Skip to content
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

Fix how NODE_ENV is being handled #123

Merged
merged 1 commit into from
Feb 14, 2019
Merged

Fix how NODE_ENV is being handled #123

merged 1 commit into from
Feb 14, 2019

Conversation

Neddz
Copy link
Contributor

@Neddz Neddz commented Feb 13, 2019

This solves #119

If a standard NODE_ENV value is specified (production or development), let it pass through and set the mode accordingly. If a non-standard NODE_ENV is specified, let is pass through and set the Webpack mode to none.

If an specific NODE_ENV value is specified, let it pass through and set the mode accordingly. If a non-standard NODE_ENV is specified, let is pass through and set the webpack mode to none.
@swyxio
Copy link
Contributor

swyxio commented Feb 14, 2019

hmm, i like the turning off of optimization for dev. cheers!

@swyxio swyxio merged commit 0121b5f into netlify:master Feb 14, 2019
@jessepinho
Copy link

Could we please get a new release of this library so that this PR is included? Thanks!

@swyxio
Copy link
Contributor

swyxio commented Mar 15, 2019

sure jesse. been a while

@swyxio
Copy link
Contributor

swyxio commented Mar 15, 2019

https://github.com/netlify/netlify-lambda/releases/tag/v1.4.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants