Extract babel config into a .babelrc file #5
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.
Note: This part is already inluded in a much larger
Various improvements
PR. However that PR seems to be stale. It might be easier to merge this very simple fix as a separate PR.Summary: If anyone tries to pipe current version of
unescape-js
through babel with custom config they will be unable to do so since the local babel config placed inside the package.json will take precedence over any other config.This is not ideal as not everyone excludes node_modules when running babel.
The fix is very simple: extract babel config into a
.babelrc
file and exclude this file when publishing to npm.