Update README: useBuiltins: true
is changed to "entry"
#6527
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.
babel-preset-env@next founds "useBuiltins": true is illegal. README is updated accordingly.
I've checked
@babel/preset-env@next
and found that"useBuiltins": true
is illegal. Considering that:"useBuiltins": true
doesn't work in@next
version"useBuiltins": true
is not documented"useBuiltins": "entry"
works in@latest
versionI suggest changing
"useBuiltins": true
to"useBuiltins": "entry"
Also I suggest that README is future-oriented because it specifies
@babel/preset-env
npm
package that is currently absent innpm
.Special thanks to @existentialism for explaining the
"useBuiltins": true
option.