chore(build): Reworks babel build #163
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Add module export in project root * Remove npmignore in favor of files array in package.json * Adds minimal Gulp v4 build - clean - lint ( ESLint ./src ) - build ( Babel transpile to ./lib ) - watch ( Standard watch & rebuild ) - default ( Cleans, lints & builds )
|
The only thing I would say is babel options should come from .babelrc so they shouldn't be specified |
Removes preset from gulp task and uses .babelrc
This was referenced Aug 7, 2016
joshwiens
force-pushed
the
d3viant0ne-BabelBuild
branch
2 times, most recently
from
c342ee4
to
e5156a8
Compare
* add travis-ci matrix covering supported os and webpack versions * removes webpack 2 beta as a devDep ( we support both majors ) * fixes peerDep for webpack 1.x ( 1.4.0 doesn't exist )
joshwiens
force-pushed
the
d3viant0ne-BabelBuild
branch
from
e5156a8
to
9649e99
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
What is the current behavior? (You can also link to an open issue here)
What is the new behavior?
Does this PR introduce a breaking change?
If this PR contains a breaking change, please describe the following...
Other information:
Node v4-v6 && Webpack ^1.1.x / ^2.1.0-beta