Optional
options: AutoExportOptionsReadonly
orderThe higher the number the later the feature will be invoked within each step.
The only real use of this is to make sure the sorting of the packageJson file happens last.
Called once at the start of Autolib, giving a change for each plugin to examine the package.
The returned examination result is merged together with the other plugins result, sharing them the next step. TODO: Re-evaluate if this is even useful or you should just keep your result in the plugin. This could return void
This plugin compiles the exports object for a packageJson file
For the distributed packageJson it should always contain paths that are targeting the dist folder from the dist folder.
For development packageJson the types always target the source for immediate feedback by the LSP by local consumers of the package. The actual code that's being imported by node has two options, by default they target the outDir and expect libraries to be built before actually running them in a local setting. There's an alternative mode however that will target the source files.
Generates exports entries automatically