Unexpected "With `useBuiltins` option, required direct setting of `corejs` option" with default configuration #2819

tmbrwn · 2019-03-19T22:42:42Z

🐛 bug report

Calling parcel build <entry point> with all default configuration results in a warning from @babel/preset-env.

🎛 Configuration (.babelrc, package.json, cli command)

.babelrc:
none
package.json:

{
  "name": "test",
  "version": "1.0.0",
  "license": "MIT",
  "devDependencies": {
    "parcel-bundler": "^1.12.2"
  }
}

CLI command: yarn run parcel build src/index.html

🤔 Expected Behavior

The build should complete with no errors or warnings

😯 Current Behavior

The build completes, but it emits the following warning:
With `useBuiltIns` option, required direct setting of `corejs` option

💁 Possible Solution

This warning appears to come from @babel/preset-env. It seems like it might be possible to avoid by specifying corejs appropriately in transforms/babel.js

🔦 Context

I'm trying to bootstrap a project which requires no extra configuration than what Parcel comes with out of the box. It would be helpful for this warning to be resolved without having to add extra non-functional Babel configuration (several attempts at configuring correctly have failed).

💻 Code Sample

The following files with the addition of the above configuration should be enough to reproduce the issue.

src/index.html:

<!DOCTYPE html>
<html>
  <body>
    <div id="root">test</div>
    <script src="./index.js"></script>
  </body>
</html>

src/index.js:

document.getElementById('root').append('more test')

🌍 Your Environment

Software	Version(s)
Parcel	1.12.2
Node	11.9.0
npm/Yarn	1.13.0
Operating System	macOS 10.14.3

The text was updated successfully, but these errors were encountered:

SGrondin · 2019-03-19T22:54:04Z

Seems to be due to babel/babel#7646 (comment)

My build is broken as well, thanks to Babel 7.4.0. I don't think it's a Parcel issue but I'd really like to hear what the solution is.

tmbrwn · 2019-03-19T23:05:59Z

"useBuiltIns now requires direct setting of corejs version option, without it will be used 2 by default and shown deprecation warning."
merged 3 hours ago at the time of writing.

Didn't realize the change was so recent. Looks like Babel is making a soft API change in 7.4.0. I doubt they'll turn back on that, so unfortunately I think it has become a Parcel issue.

loopmode · 2019-03-20T08:50:39Z

See this stackoverflow question for some solutions/approaches.

Cerlancism · 2019-03-20T09:16:40Z

See this stackoverflow question for some solutions/approaches.

I tried to lock Babel core to ~7.3 but the message still shows up

kill8268 · 2019-03-20T09:21:10Z

我的 Babel 版本是 7.0.0 也是这个问题。。。。。。

Cerlancism · 2019-03-20T09:35:08Z

Seems to be due to babel/babel#7646 (comment)

My build is broken as well, thanks to Babel 7.4.0. I don't think it's a Parcel issue but I'd really like to hear what the solution is.

I am not sure the severity of this issue, is your built really "broken" as not able run stably? Is this supposed to just a deprecation warning which should be harmless for now? I have a production project and its build is affected by this but it seems to work fine, I hope things actually are fine.

Maximilianos · 2019-03-20T09:43:59Z

For some reason my parcel build src/index.html is failing with:

With `useBuiltIns` option, required direct setting of `corejs` option


With `useBuiltIns` option, required direct setting of `corejs` option

×  XXXX\src\polyfills.js: Cannot resolve dependency 'core-js/modules/es6.array.copy-within'
    at Resolver.resolve (XXXX\node_modules\parcel-bundler\src\Resolver.js:71:17)

Despite installing core-js@3 as dependency of the project and using ["@babel/preset-env", {"useBuiltIns":"entry","corejs":"core-js@3"}] as suggested.

Rolled back to @babel/core@7.3 for now.

liuzeyafzy · 2019-03-20T13:49:52Z

See the same issue by using "cnpm install" today, however, using "npm install" is ok for me.
今天使用"cnpm install"遇到了同样的问题，但是改用“npm install” 问题就没有了。

SGrondin · 2019-03-20T14:06:18Z

I am not sure the severity of this issue, is your built really "broken" as not able run stably?

My build is broken. parcel build fails with an error, and parcel index.html fails with the same error.

It seems to be due to babel/babel#9616

I fixed it by adding "@babel/parser": "<7.4.0", to my dependencies. That forces parcel-bundler to resolve to @babel/parser 7.3. And with that the problem is fixed. I'll revisit this in a month or two once the Babel people fix the problem.

npm ls @babel/parser
├─┬ @babel/core@7.3.4
│ ├── @babel/parser@7.3.4  deduped
│ ├─┬ @babel/template@7.4.0
│ │ └── @babel/parser@7.4.0
│ └─┬ @babel/traverse@7.4.0
│   └── @babel/parser@7.4.0
├── @babel/parser@7.3.4
└─┬ parcel-bundler@1.11.0
  └── @babel/parser@7.3.4  deduped

Other links discussing this problem:
https://stackoverflow.com/questions/55251983/what-does-this-error-mean-with-usebuiltins-option-required-direct-setting-of
#2820
vuejs/vue-cli#3678
apollographql/react-apollo#2886

nicolo-ribaudo · 2019-03-20T14:12:49Z

In Babel that is just a log message, not an error. If your build is broken, it's because of something else.

cdll · 2019-03-20T15:55:26Z

same issue here even on babel@6😠

LP1994 · 2019-03-20T16:16:56Z

For the solution of plug-in error reporting upgraded to version 7.4.0, personally testing the following configuration can be successful!
1、
npm i -g core-js
2、
'@babel/preset-env',
{
useBuiltIns: 'usage',
corejs: {
version: 3,
proposals: true
}
}
PS:
'@babel/plugin-transform-runtime'can't have the corejs configuration option, although the source code in its version 7.4.0 has this option, but setting it will make an error!!! Use the'@babel/preset-env'plug-in's corejs configuration options!!!

LP1994 · 2019-03-20T16:24:09Z

https://github.com/zloirock/core-js/blob/master/docs/2019-03-19-core-js-3-babel-and-a-look-into-the-future.md

nicolo-ribaudo · 2019-03-20T17:46:41Z

'@babel/plugin-transform-runtime'can't have the corejs configuration option, although the source code in its version 7.4.0 has this option, but setting it will make an error!!!

Can you show an example which explains the problem? It should work.

@Maximilianos Doesn't Babel 7.4.0 work if you do not upgrade to core-js@3?

devongovett · 2019-03-20T18:56:02Z

@nicolo-ribaudo perhaps because babel-preset-env explicitly depends on core-js 3 itself?

https://github.com/babel/babel/blob/master/packages/babel-preset-env/package.json#L58

nicolo-ribaudo · 2019-03-20T19:02:45Z

It shouldn't be a problem: the node_modules folder should end up being similar to this:

- @babel/preset-env@7.4.0
  - core-js@3.0.0
- core-js@2

And the user code will end up loading core-js@2.

Anyway, maybe it's possible to make core-js a devDependency of core-js-compat instead of a dependency. cc @zloirock

robGetsTheJobDone · 2019-03-20T19:18:16Z

So I tried both

locking "@babel/parser": "<7.4.0
Solution mentioned above
Neither are working.
I assume others are having the same result can anyone confirm?

nicolo-ribaudo · 2019-03-20T19:22:38Z

Did you try to npm install --save core-js@2?

robGetsTheJobDone · 2019-03-20T19:27:43Z

@nicolo-ribaudo yes this is my babelrc file
{ "presets": [ ["@babel/preset-env", { "useBuiltIns": "entry", "corejs": "core-js@2" }] ] }
Still no luck :(

devongovett · 2019-03-20T19:29:04Z

Unfortunately, that won't work since Parcel overrides the preset-env config with its own. And we have no way of knowing what corejs version to use. This isn't something users should need to worry about anyway. I think the warning needs to be removed. Just use core-js 2 unless it is specified.

devongovett · 2019-03-20T19:29:39Z

(btw this overriding behavior is bad and it's going away in parcel 2, but it's what we have right now)

robGetsTheJobDone · 2019-03-20T19:30:40Z

Its not just a warning in my case even when i remove the babelrc file with core-js@2 installed i break on building :(
` /Users/rob/Documents/GitHub/h1/node_modules/history/esm/history.js:904:9: Export 'createBrowserHistory' is not defined (904:9)
902 | }
903 |

904 | export { createBrowserHistory, createHashHistory, createMemoryHistory, createLocation, locationsAreEqual, parsePath, createPath };`

devongovett · 2019-03-20T19:31:34Z

I believe that is probably a separate issue with babel 7.4, unrelated to the warning.

robGetsTheJobDone · 2019-03-20T19:33:20Z

So I tried to force @babel/parser": "<7.4.0 without any luck. Any ideas of a workaround that actually works ?

devongovett · 2019-03-20T19:36:04Z

Probably babel/babel#9589

robGetsTheJobDone · 2019-03-20T19:43:03Z

@devongovett Thanks for your help! I am not experienced with the inner workings of babel or parcel I played around with web-pack today and had no issues building my app. I prefer parcel and love how easy it is to set up. Do you think it would be a wise choice to switch back over to webpack until this issue is resolved ?

devongovett · 2019-03-20T19:43:44Z

This isn't an issue with parcel, it's a bug in babel. You'd have the same issues with webpack.

devongovett · 2019-03-20T20:08:57Z

yep, same issue.

nicolo-ribaudo · 2019-03-20T20:12:00Z

I'm not sure about the core-js thing. It's a warning, but people tend to freak out about warnings, and perhaps other bugs in babel 7.4 are getting conflated with this warning.

Ok, let me explain the current situation:
@babel/preset-env generates imports to core-js. Let's assume that it only generates imports to core-js@2, that it doesn't know about core-js@3. We can make this assumption because core-js@2 is the default behavior.

The fact that it generates those imports means that users need to have "core-js": "^2.0.0" in their package.json's dependencies.
Since almost every node project which uses npm already has core-js as a dependency of a dependency (it has three times the downlaods of react or of webpack), and npm hoist packages to the top when possible, so node_modules/core-js always existed even if it wasn't defined as a dependency: even if it was documented, people didn't notice that they where depending on a package which they hadn't specified.

Yesterday core-js@3 was released. If any package in your dependency tree (for example, as you noted in #2819 (comment), Babel), your app will have both core-js@2 and core-js@3 in your dependencies three and npm can choose which to hoist.
If it decides to hoist core-js@3, all the imports pointing to core-js@2 will be broken. It is a major version of the package, so it isn't unexpected that it breaks something.
For this reason, users must have core-js@2 in their dependencies: if they are relying on a package, it needs to be explicit or major updates will be done when any of the dependencies updates its subdependency.

Even if the necessity to npm install --save core-js has been documented since Babel 6, users didn't do it. We needed to do something to make them aware about it, so we asked them not to rely on the default behavior but to be explicit about it: corejs: 2 is a way of saying "I know I'm using core-js@2". I know, the warning message doesn't explain it and we will soon update it (babel/babel#9716).

An example of a project which relied on core-js without it being installed is angular-cli: angular/angular-cli#13954 (comment)

Relying on npm hoisting won't work anymore, and we need to make people aware of the presence of core-js in their project.

I don't know if parcel does analyse node_modules, but if it does the only way to proper fix this issue is to set the corejs option you pass to preset env based on what will be bundled: corejs: require("core-js/package.json").version.

Thanks for reporting the other issue, I'm looking at it.

nicolo-ribaudo · 2019-03-20T20:15:51Z

Also, 53c09b3 will only work until some other dependency will depend on core-js@3. As you can see in #2819 (comment), it's not a problem specific of v7.4.

LP1994 · 2019-03-21T07:06:29Z

'@babel/plugin-transform-runtime'can't have the corejs configuration option, although the source code in its version 7.4.0 has this option, but setting it will make an error!!!

Can you show an example which explains the problem? It should work.

@Maximilianos Doesn't Babel 7.4.0 work if you do not upgrade to core-js@3?

I only installed version 3.0.0 of "core-js".(npm i -g core-js)
No "core-js@2"!!!

My version of "core-js" in "package.json":
"core-js": "^3.0.0" ,
"core-js-compat": "^3.0.0" ,
"core-js-pure": "^3.0.0"

and, My Babel configuration has the following information:
'@babel/preset-env',
{
targets: {
browsers: [
'>= 10%',
'cover 95%',
'since 2017-01-01',
'iOS >= 10',
'Safari >= 10',
'Edge >= 16',
'Opera >= 47',
'Android >= 56',
'Chrome >= 56',
'ChromeAndroid >= 56',
'Firefox ESR',
'Firefox >= 54',
'FirefoxAndroid >= 54',
'last 2 Baidu major versions',
'last 2 OperaMini major versions',
'last 2 QQAndroid major versions',
'last 2 UCAndroid major versions',
'last 2 OperaMobile major versions',
'last 2 Samsung major versions',
'last 2 BlackBerry major versions',
'last 2 major versions',
'last 2 versions',
'not ie <= 11',
'not ie_mob <= 11',
'not dead'
],
safari: 'tp',
esmodules: false
},
modules: false,
spec: false,
loose: true,
shippedProposals: true,
useBuiltIns: 'usage'
}
'@babel/plugin-transform-runtime',
{
helpers: true,
regenerator: true,
useESModules: true
}

When the @babel/preset-env and @babel/plugin-transform-runtime options are set the "corejs" option, the value is:
corejs: {
version: 3,
proposals: true
}
Report wrong!!!
The error message is as follows:

1.txt

If only the "corejs" option of "@babel/plugin-transform-runtime" is set, and the value is:
corejs: {
version: 3,
proposals: true
}
And there is no "corejs" option for "@babel/preset-env"!!!
However, the value of the "useBuiltIns" option of "@babel/preset-env" is "usage".
It will go wrong.!!!
The error message is as follows:

只启用transform.txt

But if me just set the "corejs" option of "@babel/preset-env", the value is:
corejs: {
version: 3,
proposals: true
}
No "corejs" option is set for "@babel/plugin-transform-runtime"!
Then my project will compile successfully!!!

nicolo-ribaudo · 2019-03-21T08:13:11Z

If you want to use core-js with Babel/runtime you need to install @babel/runtime-corejs2 or @babel/runtime-corejs3.

Anyway (at everyone) this issue is turning in a Babel-related support not related to Parcel. Please ask these questions in the Babel repo.

LP1994 · 2019-03-21T09:36:03Z

If you want to use core-js with Babel/runtime you need to install @babel/runtime-corejs2 or @babel/runtime-corejs3.

Anyway (at everyone) this issue is turning in a Babel-related support not related to Parcel. Please ask these questions in the Babel repo.

Exactly!!!
I went to my "node_modules" folder and found that there was only "@babel/runtime-core js2" and no "@babel/runtime-core js3"!!!
I'll try it now!!!
Thank you for your answer!!!
I am a person who likes to use the latest babel. As a result, many problems have been encountered before due to the changes in the new version, but solutions have been found on "GitHub" and "Stack Overflow" and "Babel official website".

please check these resources below on the reasoning behind this problematic babel bug: - https://stackoverflow.com/questions/55251983/what-does-this-error-mean-with-usebuiltins-option-required-direct-setting-of - parcel-bundler/parcel#2819 - parcel-bundler/parcel@53c09b3

ewqazxc · 2019-03-25T02:02:54Z

使用npm start报错

但parcel index.html又正常。。。

… version (Lyrkan) This PR was merged into the master branch. Discussion ---------- Set useBuiltIns to false by default and allow to set core-js version While working on #544 I noticed that the latest version of `@babel/preset-env` displayed a warning (which luckily made [one of the tests](https://travis-ci.org/symfony/webpack-encore/jobs/509655320) fail): ``` WARNING: We noticed you're using the `useBuiltIns` option without declaring a core-js version. Currently, we assume version 2.x when no version is passed. Since this default version will likely change in future versions of Babel, we recommend explicitly setting the core-js version you are using via the `corejs` option. You should also be sure that the version you pass to the `corejs` option matches the version specified in your `package.json`'s `dependencies` section. If it doesn't, you need to run one of the following commands: npm install --save core-js@2 npm install --save core-js@3 yarn add core-js@2 yarn add core-js@3 ``` This is related to the `core-js` 3 update that happened recently (see babel/babel#7646). As explained in parcel-bundler/parcel#2819 (comment) the issue is that users are normally supposed to add `core-js` in their root `package.json` when setting `useBuiltIns` (which is currently already set by Encore to `entry` by default). This is a problem for us since it means that: * we are requiring users to add `core-js` to their project by default (or manually setting `useBuiltIns` to `false`) * if they do they'll still have a warning because the new `corejs` option of `@babel/preset-env` won't be set (we can't do that because we won't know which version they choose to install). For now I suggest that we set `useBuiltIns` to `false` by default and add a new option to `Encore.configureBabel()` that allows to set the `corejs` option. Commits ------- 85896ef Set useBuiltIns to false by default and allow to set corejs version

ewqazxc · 2019-04-24T01:55:52Z

I just use these. you can also try update parcel,it maybe deal this bug ![image](https://user-images.githubusercontent.com/30255395/56632942-bd5eb300-668e-11e9-90ee-4be3145fe240.png)

mischnic · 2019-05-09T19:46:23Z

@devongovett With the next release switching back to the latest Babel, is the corejs situation resolved now?

Several warnings are emitted during build due to parcel-bundler/parcel#2819 so pin parcel to a version without the issues.

tmbrwn · 2019-05-16T17:05:34Z

Confirmed that this issue is solved with 1.12.3 of parcel

tmbrwn · 2019-05-16T17:10:06Z

Sorry, just realized that 1.12.3 only rolled back the version of babel. I think I should keep this open until there is a definitive solution.

AK47-dadada · 2019-05-27T09:09:55Z

For the solution of plug-in error reporting upgraded to version 7.4.0, personally testing the following configuration can be successful!
1、
npm i -g core-js
2、
'@babel/preset-env',
{
useBuiltIns: 'usage',
corejs: {
version: 3,
proposals: true
}
}
PS:
'@babel/plugin-transform-runtime'can't have the corejs configuration option, although the source code in its version 7.4.0 has this option, but setting it will make an error!!! Use the'@babel/preset-env'plug-in's corejs configuration options!!!

babel.config.js吗

github-actions · 2020-01-18T01:02:56Z

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs.

airtonix · 2020-06-28T01:29:26Z

Upgrading made this go away:

    "parcel": "^1.12.4",

{
    "presets": [
        ["@babel/preset-env", {
            "useBuiltIns": "usage",
            "corejs": "3"
        }]
    ],
    "plugins": [
        ["@babel/plugin-proposal-class-properties", {}]
    ]
}

mischnic added 🐛 Bug Babel labels Mar 19, 2019

0xGabi mentioned this issue Mar 20, 2019

Unexpected "With useBuiltins option, required direct setting of corejs" aragon/aragon-apps#724

Closed

nicolo-ribaudo mentioned this issue Mar 21, 2019

core-js upgrade to 3 seems like a breaking change (broke StorybookJS) babel/babel#9731

Closed

zloirock mentioned this issue Mar 21, 2019

core-js@3.0.0/modules/es6.array.copy-within not found zloirock/core-js#506

Closed

zloirock mentioned this issue Mar 21, 2019

Unnecessary polyfills in code babel/babel#9737

Closed

Lyrkan mentioned this issue Mar 21, 2019

Set useBuiltIns to false by default and allow to set core-js version symfony/webpack-encore#545

Merged

oakromulo mentioned this issue Mar 22, 2019

Update package.json (@babel/core@7.4.0 issue) vuejs/vue-cli#3692

Closed

nicolo-ribaudo mentioned this issue Mar 22, 2019

ModuleNotFoundError: Module not found: Error: Can't resolve 'core-js/library/fn/object/define-property' babel/babel#9734

Closed

mischnic mentioned this issue May 7, 2019

Fix CI #2990

Merged

3 tasks

coocos added a commit to coocos/toy-tracer that referenced this issue May 12, 2019

Pin parcel to 1.12.3

0799424

Several warnings are emitted during build due to parcel-bundler/parcel#2819 so pin parcel to a version without the issues.

tmbrwn closed this as completed May 16, 2019

tmbrwn reopened this May 16, 2019

github-actions bot added the Stale Inactive issues label Jan 18, 2020

AndreyChernykh mentioned this issue Jan 27, 2020

pdfjs-dist doesn't have core-js in dependencies mozilla/pdf.js#11539

Closed

github-actions bot closed this as completed Feb 3, 2020

github-actions bot removed the Stale Inactive issues label Jun 28, 2020

Unexpected "With useBuiltins option, required direct setting of corejs option" with default configuration #2819

Unexpected "With useBuiltins option, required direct setting of corejs option" with default configuration #2819

Comments

tmbrwn commented Mar 19, 2019 • edited

🐛 bug report

🎛 Configuration (.babelrc, package.json, cli command)

🤔 Expected Behavior

😯 Current Behavior

💁 Possible Solution

🔦 Context

💻 Code Sample

🌍 Your Environment

SGrondin commented Mar 19, 2019

tmbrwn commented Mar 19, 2019

loopmode commented Mar 20, 2019

Cerlancism commented Mar 20, 2019

kill8268 commented Mar 20, 2019

Cerlancism commented Mar 20, 2019 • edited

Maximilianos commented Mar 20, 2019

liuzeyafzy commented Mar 20, 2019

SGrondin commented Mar 20, 2019 • edited

nicolo-ribaudo commented Mar 20, 2019 • edited

cdll commented Mar 20, 2019 • edited

LP1994 commented Mar 20, 2019

LP1994 commented Mar 20, 2019

nicolo-ribaudo commented Mar 20, 2019 • edited

devongovett commented Mar 20, 2019

nicolo-ribaudo commented Mar 20, 2019 • edited

robGetsTheJobDone commented Mar 20, 2019

nicolo-ribaudo commented Mar 20, 2019 • edited

robGetsTheJobDone commented Mar 20, 2019 • edited

devongovett commented Mar 20, 2019

devongovett commented Mar 20, 2019

robGetsTheJobDone commented Mar 20, 2019 • edited

devongovett commented Mar 20, 2019

robGetsTheJobDone commented Mar 20, 2019

devongovett commented Mar 20, 2019

robGetsTheJobDone commented Mar 20, 2019

devongovett commented Mar 20, 2019 • edited

devongovett commented Mar 20, 2019

nicolo-ribaudo commented Mar 20, 2019 • edited

nicolo-ribaudo commented Mar 20, 2019 • edited

LP1994 commented Mar 21, 2019

nicolo-ribaudo commented Mar 21, 2019

LP1994 commented Mar 21, 2019

ewqazxc commented Mar 25, 2019

ewqazxc commented Apr 24, 2019 via email • edited

mischnic commented May 9, 2019

tmbrwn commented May 16, 2019

tmbrwn commented May 16, 2019

AK47-dadada commented May 27, 2019

github-actions bot commented Jan 18, 2020

airtonix commented Jun 28, 2020

Unexpected "With `useBuiltins` option, required direct setting of `corejs` option" with default configuration #2819

Unexpected "With `useBuiltins` option, required direct setting of `corejs` option" with default configuration #2819

tmbrwn commented Mar 19, 2019 •

edited

Cerlancism commented Mar 20, 2019 •

edited

SGrondin commented Mar 20, 2019 •

edited

nicolo-ribaudo commented Mar 20, 2019 •

edited

cdll commented Mar 20, 2019 •

edited

nicolo-ribaudo commented Mar 20, 2019 •

edited

nicolo-ribaudo commented Mar 20, 2019 •

edited

nicolo-ribaudo commented Mar 20, 2019 •

edited

robGetsTheJobDone commented Mar 20, 2019 •

edited

robGetsTheJobDone commented Mar 20, 2019 •

edited

devongovett commented Mar 20, 2019 •

edited

nicolo-ribaudo commented Mar 20, 2019 •

edited

nicolo-ribaudo commented Mar 20, 2019 •

edited

ewqazxc commented Apr 24, 2019 via email •

edited