-
-
Notifications
You must be signed in to change notification settings - Fork 27k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Add allowESModules option to babel-preset-react-app #5487
Conversation
This pull request has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs. |
Bump? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it'd be better to use the already-existing variable name. What do you think?
@@ -29,6 +29,7 @@ module.exports = function(api, opts, env) { | |||
var isEnvProduction = env === 'production'; | |||
var isEnvTest = env === 'test'; | |||
|
|||
var allowESModules = validateBoolOption('allowESModules', opts.allowESModules, true); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's make this default to isEnvDevelopment || isEnvProduction
and use the existing name.
var allowESModules = validateBoolOption('allowESModules', opts.allowESModules, true); | |
var useESModules = validateBoolOption('useESModules', opts.useESModules, isEnvDevelopment || isEnvProduction); |
@@ -140,7 +141,7 @@ module.exports = function(api, opts, env) { | |||
// https://babeljs.io/docs/en/babel-plugin-transform-runtime#useesmodules | |||
// We should turn this on once the lowest version of Node LTS | |||
// supports ES Modules. | |||
useESModules: isEnvDevelopment || isEnvProduction, | |||
useESModules: allowESModules ? isEnvDevelopment || isEnvProduction : false, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Consequently, this becomes simpler (or use the shorthand syntax):
useESModules: allowESModules ? isEnvDevelopment || isEnvProduction : false, | |
useESModules: useESModules, |
Seams reasonable, updated to match requested changes. |
Co-Authored-By: Pajn <rasmus@eneman.eu>
I misunderstood and thought you ment only the varaible name, but that's an easy fix |
I think this behavior is best -- if undefined, it uses old (reasonable) logic. If the user defines it, uses that value. Does this seem good to you? |
Absolutely, It's even cleaner code. 👍 |
* upstream/master: (210 commits) Support setupTests.ts (facebook#5698) Remove unnecessary whitespace in template HTML Run prettier on HTML files (facebook#5839) Some Grammar fixes (facebook#5858) Fix link to page about running tests (facebook#5883) fix: make typescriptformatter support 0.5 of fork checker (facebook#5879) Always test with the latest stable Node version on Travis (facebook#5546) Fix propertyDecorator test Upgrade babel deps Fix annotated var test Fix TypeScript decorator support (facebook#5783) fix: add `sideEffects: false` to react-error-overlay (facebook#5451) Add allowESModules option to babel-preset-react-app (facebook#5487) Make named-asset-import plugin work with export-as syntax (facebook#5573) React native repository updated in README.md (facebook#5849) extra polyfills must be included manually (facebook#5814) Rename 'getting started' link to 'docs' (facebook#5806) docs: Simplify installing Storybook with npx (facebook#5788) Don't polyfill fetch for Node -- additional files (facebook#5789) docs: Change Storybook install documentation (facebook#5779) ...
Please see the discussion in #5452