move babel requirements into dependencies #71
Closed
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.
we use
webpack
andbabel-loader
and explicitly exclude/node_modules/
from babel-loader:we now get this error:
that line is using the es6 spread operator which requires specific babel plugins / configuration.
we do use a babel config that supports this so i change my
babel-loader
to run for this module only (per this)then we got this error:
because those requirements are listed in devDependencies they don't get installed when npm does its build.
this pr moves those into proper deps so that they work.
beyond that the es6 build probably deserves at least a minor version bump (if not major) - going from 1.2.1 -> 1.2.3 broke our app and required digging to solve. react-helmet recently went through something similar..