This repository has been archived by the owner on May 11, 2018. It is now read-only.
hardcode a current node version option #35
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
hzoo
force-pushed
the
current-node-version
branch
10 times, most recently
from
e32c82b
to
734619d
Compare
|
|
hzoo
force-pushed
the
current-node-version
branch
from
734619d
to
f0586f1
Compare
Closed
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
For #9
If a user wants to compile babel against the current node version (
node --version) but doesn't want to use js for the config (in package.json/.babelrc rather than say babel-loader or a separate file)node: "--version"->"node": parseFloat(process.versions.node)?Option name ideas?
cc @shubheksha