-
Notifications
You must be signed in to change notification settings - Fork 243
cross-env not working with webpack command? #13
Comments
Huh, that's very odd. Do you have a repo where I can see this in action? |
I'll slap one together later tonight. |
Hey, just put together the example repo below specifically for this issue, so hopefully that'll help localize the problem: https://github.com/mikechabot/cross-env-example And I tried to document as much as I could in the README, but let me know if you hit any issues, or if I'm simply doing something incorrect, or if you have any questions. Of the scripts documented, you'll probably be interested in the following three:
|
Oh, and no rush. |
Sorry it took so long, but here's the solution: mikechabot/cross-env-example#1 |
Great, thanks very much for taking a look; I knew it'd be something on my end!. Thanks again, and great lib! |
I feel I may be implementing this incorrectly. The first command properly sets my NODE_ENV variable, however the second does not. What am I missing? Server.js provided below.
As we can see, I'm now running in production mode, however if I add in the
webpack
command, which is noted in the example command on https://www.npmjs.com/package/cross-env, it doesn't work. (Note:NODE_ENV not found, defaulting to development
)However, if I just use the following, everything works as expected:
Server.js
The text was updated successfully, but these errors were encountered: