feat(react): add generateExportsField option to @nrwl/web:rollup
executor so it is an opt-in feature
#10742
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The new
exports
field is a way to specify entry points for packages. Node and TypeScript both support this field, however it is causing issues with other tooling, so for now it is opt-in via thegenerateExportsField
option.Also adds skipTypeField option in case that is causing issues for users.
Current Behavior
Building with
@nrwl/web:rollup
generates package.json withexports
field for the main entry point. This is causing some issues with other tooling/bundlers.Expected Behavior
Users must set
generateExportsField: true
in order to generate this field. By default it is off.Related Issue(s)
Fixes #10741