Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"exports" conditions semantics #665

Merged
merged 1 commit into from Mar 18, 2021
Merged

"exports" conditions semantics #665

merged 1 commit into from Mar 18, 2021

Conversation

guybedford
Copy link
Contributor

This updates ncc to follow the "node" condition and not the "module" condition in the exports field with tests.

This will ensure that the built semantics exactly mirror the Node.js semantics.

Support for the "imports" field similarly is pending webpack/webpack#12928.

@guybedford guybedford force-pushed the exports-nomodule branch 2 times, most recently from 8bb367e to ce63108 Compare March 18, 2021 16:19
@styfle styfle added the automerge Automatically merge PR once checks pass label Mar 18, 2021
@@ -52,8 +52,24 @@ function ncc (
transpileOnly = false,
license = '',
target,
production = true,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does node automatically consider 'production' exports?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems like this should be conditions: string[] instead

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automerge Automatically merge PR once checks pass
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants