Skip to content
This repository has been archived by the owner on Feb 27, 2023. It is now read-only.

Windows machine 'NODE_ENV' is not recognized as an internal or external command, #20

Closed
Sensiblemnd opened this issue Jul 22, 2021 · 2 comments

Comments

@Sensiblemnd
Copy link

When doing a yarn build

'NODE_ENV' is not recognized as an internal or external command,

@Sensiblemnd
Copy link
Author

Fix:
yarn add -D cross-env
in package json

"build": "cross-env NODE_ENV=production webpack --config config/webpack.prod.js",
"build-staging": "cross-env NODE_ENV=production webpack --config config/webpack.stag.js",

@stefanwuthrich
Copy link
Contributor

tks @Sensiblemnd
If you want, you can add a pull request or tell me to do

@Sensiblemnd Sensiblemnd changed the title Windows machine Windows machine 'NODE_ENV' is not recognized as an internal or external command, Jul 22, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants