env & babel-node cmds not recognized on Windows #73
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.
A couple of commands in the
package.json
scripts do not work out of the box on Windows.env
Installed cross-env to solve the common
env
command not being recognized on Windows.babel-node
The command works when using Yarn, but
npm run dev
produces the error:'babel-node' is not recognized as an internal or external command
. For some reason, on Windows, NPM does not pick upbabel-node
fromnode_modules/.bin
. It is solved by specifying the path directly.