Nothing in the node.js runtime. Perhaps in one or more of the packages you use. That and other environment variables is just one way to configure behaviour.

By the way you would not normally deploy node modules or store them in your versioning system. They should be installed/updated at deployment time on the target. You should also be able to dictate the node version to use with nvm

On 7 Feb 2018, at 18:20, Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote:

So there's nothing inherent in the runtime controlled by that?

-----Original Message-----
From: Jack Woehr [mailto:jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx]
Sent: Wednesday, February 07, 2018 11:56 AM
To: IBMi Open Source Roundtable <opensource@xxxxxxxxxxxx>
Subject: Re: [IBMiOSS] Deploy Node?

NODE_ENV is a convention so you can execute conditional code based on its setting, typically differentiating between production and development.

Samples may check its setting.


--
This is the IBMi Open Source Roundtable (OpenSource) mailing list
To post a message email: OpenSource@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/opensource
or email: OpenSource-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/opensource.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.