Setting Environment Variables for preset-node

[trusktr]

I'd like for an app that I run with neutrino-preset-node to use real environment variables (not transpiled in).

How can we do this?

[eliperelman]

Node.js still has access to process.env and environment variables won't be transpiled in unless you use a Webpack plugin or the env middleware to force it to. For example, if you had the following code:

console.log(process.env.TEST);

and ran the build with:

TEST="hello world" neutrino build

Your built file won't contain the string "hello world". It will still contain the call to process.env.TEST and it will be pulled at runtime (e.g. when the Node.js process starts).

Hope that answers your question. 👍

[trusktr]

It makes sense, but as mentioned in the other issue, the env vars are undefined when neutrino runs the script.

…

On Sep 15, 2017 7:58 AM, "Eli Perelman" ***@***.***> wrote: Closed #319 <#319>. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#319 (comment)>, or mute the thread </~https://github.com/notifications/unsubscribe-auth/AASKzrll6GkiKGVFHvL-UPPUTcliK_suks5sipCUgaJpZM4PYbi5> .

[trusktr]

I ended up making a webpack plugin to start/restart the server using child_process.exec on compiler after-emit event.

[timkelty]

@trusktr @eliperelman I believe the confusion here may be related this bug: #839

[edmorley]

@trusktr does the issue you were seeing sound like #839?