This repository has been archived by the owner on May 16, 2023. It is now read-only.
Is it intended that default watch sets NODE_ENV to production?
#17
Assignees
Labels
Comments
ivawzh
changed the title
watch to run with NODE_ENV production?watch sets NODE_ENV to production?
|
This is a bug. I'll fix it next Monday unless you got a PR for it, sorry! |
|
This seems to be fixed in 0.7.0, but I didn't actually try to fix anything related to this. I've noticed this on one of my projects but it seems to be fairly random. I'm trying to pin-point more specifically what causes this and I definitely need your help with this one! |
Cretezy
added
help wanted
|
Hey @Cretezy, I'm still seeing this behaviour in |
|
I've been experiencing this too sometimes, and I'm unsure what is the root of it. If you can give me a sample that I can reproduce it would help greatly! :) |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As title said, currently v0.6.0 by default run
yarn watchwithNODE_ENV=production start.My assumption is most people will only use
watchfor development. Is there any reason it should not bedevelopmentby default?The text was updated successfully, but these errors were encountered: