This repository has been archived by the owner on Aug 4, 2020. It is now read-only.
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.
My original goal was to remove the dependency on
babel-core@5
, since there's no actual usage of the module in this plugin (nor of thehelpers.js
file, wherein the onlyrequire('babel-core')
is located). By doing this, we reduce the amount of cruft installed by npm when users update to babel 6.I went through all the dependents of
eslint-plugin-babel
, and none of them are requiringhelpers.js
. Some of the dependents themselves depend onbabel-core
, but that's not a reason to keep it as a dependency of this module.Incidentally, when running the tests after making my changes, I found weird errors related to the recent
Object.freeze()
shenanigans upstream ineslint
. Theoretically,eslint@1.10.1
should have reverted those breaking changes (first reported as breakingeslint-plugin-react
), but it's a good idea to stop modifying thecontext
object anyway, as the maintainers ofeslint
have expressed the intention of restoring that freeze ineslint@2
.