-
Notifications
You must be signed in to change notification settings - Fork 10
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
Check for NODE_ENV !== 'development' and not NODE_ENV === 'production' #116
Comments
Hey, thanks for the detailed report. Fortunately with official No, at this stage, nothing should make it through to production. It gets a bit tricky to conditionally load packages though, so we just disable everything in the package when we're in production. The top 2 lines of if (process.env.NODE_ENV === 'production')
return; Is there any possibility at all that your |
There definitely is. It's set to |
Ah ok, got it! I guess it's probably better to check if OT: curious what kind of special things you do when it's |
Will be in the next beta :) |
Awesome. Thanks for the fix!! I'm using
I've had issues with this before though, for example Galaxy didn't respect setting |
Makes sense! Thanks! |
This also help me out with a different use case. I run my acceptance tests with |
Description of Problem
Deployment to Galaxy fails. No problems in dev mode, or if building locally / running production bundle locally.
Galaxy logs an uncaught exception with no useful information (and continually kills/loads containers) but I'm getting the following logged to Sentry which seems relevant. Should this code be going to production?
## Environment - Meteor version: 1.3.3 - ecmascript-hot version: gadicc:ecmascript-hot@2.0.0-beta.5 - Operating System: OS X 10.10.5 / Galaxy ## Supporting files
.meteor/packages
.meteor/versions
packages.json
.babelrc
(if you modified it)client/.babelrc
(if you modified it)server/.babelrc
(if you created it)The text was updated successfully, but these errors were encountered: