I am trying to implement an in-browser IDE and want to extract the ts info in browser. Since ts compiler
can already run in browser, and the core algorithm of api-extractor don't depend on Node.js, it is hopful to support in-browser usage.
The main obstacle is :
resolve files, load files (currently using 'path', 'resolve' and '@rushstack/node-core-library'). We need to make api-extractor depend on a in-memory filesystem.
Related issue:
https://github.com/microsoft/rushstack/issues/988: this resolved issue already enable us to parse .api.json emmited by api-extractor, in browser. But I also want to run api-extractor inside browser.
https://github.com/microsoft/rushstack/issues/1010: discuss about making api-extractor run tsc as a prepare step, emitting '.d.ts' in memory, for api-extractor to consume. Since tsc can already run in browser and emit files into memery, I think if we can make api-extractor resolve/load files from memory(depend on a in-memory filesystem), both these issues would be resolved.
Is this a feature or a bug?
I am trying to implement an in-browser IDE and want to extract the ts info in browser. Since ts compiler can already run in browser, and the core algorithm of api-extractor don't depend on Node.js, it is hopful to support in-browser usage.
The main obstacle is :
Related issue: https://github.com/microsoft/rushstack/issues/988: this resolved issue already enable us to parse
.api.json
emmited by api-extractor, in browser. But I also want to run api-extractor inside browser. https://github.com/microsoft/rushstack/issues/1010: discuss about making api-extractor run tsc as a prepare step, emitting '.d.ts' in memory, for api-extractor to consume. Since tsc can already run in browser and emit files into memery, I think if we can make api-extractor resolve/load files from memory(depend on a in-memory filesystem), both these issues would be resolved.