Use export mode "auto" by default when preserving modules #3265
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.
This PR contains:
Are tests included?
Breaking Changes?
List any relevant issue numbers:
Resolves #3258
Description
This will make sure all files are treated as entry points with regard to how their exports are rendered when preserving modules. More precisely, unless
output.exports
is used, all files will be treated as havingoutput.exports
set toauto
. This only has an effect forcjs
andamd
output:Files that mix default and named exports will now produce warnings for those formats, though. However, those warnings are aggregated and truncated by the CLI to reduce visual noise. To prevent those warnings other than changing your code, you can force all files to use
named
export mode viaoutput.exports: named
in your config. This will produce the following:That means that the default export will need to be accessed e.g. via
require(./file.js).default
. Rollup will make sure that internal exports will properly respect this.