NODE_ENV is always "production" when running "netlify-lambda serve..."

[rub1e]

I've followed the excellent @sw-yx static/dynamic tutorial and I'm trying to build on it to include local env vars in development

I've set up a .env.development file and I'm trying to use NODE_ENV to set the correct .env filepath in development.

But when I run the start scripts (gatsby develop and netlify-lambda serve src/lambda), I get two different NODE_ENVs 😕

• In gatsby-config.js it logs "development"
• In src/lambda/hello.js it logs "production" 🤕

Apologies if this is obvious / expected behaviour, but I've run out of ideas 😖

[swyxio]

hmm. what version are you on? we addressed this here #119 may just need an update

[rub1e]

I'm on 1.4.13

I did see #123 from #119 but that fix is for build, whereas the issue I'm having is with serve

I've tried going through https://github.com/netlify/netlify-lambda/blob/master/lib/serve.js but I can't figure out why this would be. Happy to do a PR if you can point me in the right direction!

[swyxio]

i'm not sure either. dont have time to go through this in detail right now. if you have the time, this one should be a matter of placing a few strategic console.log's inside your netlify-lambda instance to figure out where your NODE_ENV is getting introduced.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.