NODE_ENV is always `production`

[Neddz]

Hello! I am having some trouble with the following:

I have been trying to overwrite the NODE_ENV variable with no success.

If I do:
NODE_ENV=development netlify-lambda build <folder>
all the functions inside <folder> will have the process.env.NODE_ENV set to production. I believe this might be because webpack is always run in production mode.

Please let me know if I am doing anything wrong.

Thank you!

[swyxio]

hi,

yes, the line is here

netlify-lambda/lib/build.js

Line 72 in d0cb744

mode: 'production',

pr welcome if you wanna fix

[azdanov]

As a workaround you could define a webpack.functions.js with:

const webpack = require('webpack')

module.exports = {
  plugins: [
    new webpack.EnvironmentPlugin({ NODE_ENV: 'development' }),
  ],
}

And run netlify-lambda --config webpack.functions.js build src/lambda. This way it's possible to load any env variables from CI or Netlify.

[swyxio]

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