-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
default to production when no NODE_ENV #3614
Conversation
QA Wolf here! As you write new code it's important that your test coverage is keeping up. |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
if (!process.env.NODE_ENV) | ||
console.warn( | ||
'*FOX SCREAM* process.env.NODE_ENV is not explicitly set!, defaulting to production' | ||
) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah yes we need this because the built package won't work I actually told jess about it a few days ago, nice catch!
I'm a little on the fence exposing this error to users but at the same time I can imagine anyone missing this argument and wondering what's going on. So I think it's good as-is.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah mostly likely their app launcher is going to eat all these logs anyways
failures were unrelated |
Resolves #3576
Looks like something @lf94 added so I'll put him on review in case there's something I'm missing here.