Open deyaaeldeen opened 1 year ago
For api-extractor, I kind of have it here https://github.com/Azure/azure-sdk-for-js/pull/27646
We should be able to have format commands too. Most of the commands are using the same config/ignore config.
I wonder if we should in general lean into dev-tool providing virtual handling for all/most npm scripts so that all packages have the same entry points but we can override/customize the behavior in dev-tool instead of in the individual package?
The current setup of our libraries involves various npm scripts, such as "clean", "build", "format", among others, utilizing third-party development dependencies like rollup, typescript, api-extractor, prettier, rimraf, etc. This approach in our mono-repository presents several challenges:
To address these issues, I suggest adopt dev-tool vendored commands (the dtx command) for incorporating development dependencies. This approach will standardize the use of these dependencies across all our libraries. For instance, generating an API view for a library would be executed with the following command:
This command would reference the version of api-extractor that dev-tool relies on. By adopting this method, our libraries will not directly depend on individual development dependencies, simplifying management and upgrades, and ensuring a consistent development experience across all libraries.