[api-extractor] add basic support for import * as module from './local-module'

[mckn]

I have basically taken the PR created by @adventure-yunfei here and cleaned up the code a bit. Tested it on the Grafana project which is a really big project and then opened this PR.

Thanks and great work by @adventure-yunfei!

Please let me know what you want to be adressed to get it merged. I think there are several people that wants to help out to get this PR merged.

Fixes: #1029

[msftclas]

All CLA requirements met.

[mckn]

I can run the tests and see that there are two failing tests but not sure how to get some more details about the failure.

Saw that it was a build failure and got more details by running the regular gulp script in the api-extractor.

[stevengum]

Just had two style/practice comments.

I ran into this issue today and am looking forward to these changes, thanks @mckn!

[stevengum]

@octogonz sorry for the out-of-the-blue PR review, just excited to use api-extractor on my team's projects 😄

@mckn, do you have tests that can be added to the PR?

[mckn]

@octogonz sorry for the out-of-the-blue PR review, just excited to use api-extractor on my team's projects 😄

@mckn, do you have tests that can be added to the PR?

@stevengum awesome feedback! Thanks for doing the review. Have made the updates and pushed the changes.

I have not added any tests but please give me some directions on how I can write some tests and I am happy to add that as well.

[stevengum]

@mckn sorry for the delay, I'm not a regular contributor to this project so I don't know how to write/run tests.

I've pulled the grafana branch and was going to run the tests locally, it looks like they've already passed as part of the setup of the repo.

I don't have insight into their CI pipelines either, could the rushstack CI Build be stuck in pending due to the merge conflict?

[mckn]

@stevengum I have added one some simple tests to verify the import * as .. scenario. Not sure if it is the merge conflict that is causing errors. But I will sync with upstream asap so we can get this mergeable.

[mckn]

@octogonz would be awesome if you could have a look at this PR 🙏

[rbuckton]

I tried this on one of my projects and the links in the TOC for namespaces are broken (as in, clicking on them does nothing).

This is when using the YamlDocumenter API via new YamlDocumenter(apiModel, /*newDocfxNamespaces*/ true);.

[rbuckton]

Disregard that comment. After a clean build of my documentation it seems to be working fine.

[rbuckton]

I will add that this does fix the underlying issue for me. I've been using a local patch to work around this for my documentation builds and that patch is no longer necessary.

[santam85]

Happy to see there's a PR already in this advanced stage for this. This is a must to support api-extractor for Angular projects as well, as there's limited control on the typings output from the CLI

[lifeiscontent]

@octogonz any updates here?

[octogonz]

@octogonz any updates here?

To be clear, what's blocking this PR wasn't the code review, but rather some nontrivial work required to complete the implementation. (Some of which is identified by TODO in the author's comments.) I'm looking at it again this weekend to see if I can push it along.

[octogonz]

Today I got the .api.md file straightened out. The last step will be the .api.json file.

[octogonz]

🚀 This is finally ready to go!

I tested it by building a large production monorepo with lots of projects that use API Extractor.

[octogonz]

Released with API Extractor 7.17.0