| thcipriani | |
| mobrovac | |
| mmodell |
| Release-Engineering-Team |
Define NODE_ENV based on the configuration and define NODE_PATH when
either npm.install or npm.env are true. The latter behavior is
necessary for final stages of multi-stage builds where npm modules are
not installed but the application requires node-related environment
variables to run.
Rename npm module/config to node
Renamed npm yaml entry to node and NpmConfig to NodeConfig.
Since we're dealing with general node builds and configuration, this
seems to make more sense.
Run go test ./... or arc unit. Run blubber against at least the
blubber.example.yaml.
| Automatic diff as part of commit; lint not applicable. |
| Automatic diff as part of commit; unit tests not applicable. |
For testing and development, NODE_ENV should probably be set to development, but I don't see it being set, i.e. if we are not in a production setting, it's safe to assume we are in development mode :)
Blubber will just set up a NODE_ENV environment variable for whatever you've set the node.env yaml config to, so it's up to you to set it according to your needs at the root level of the config or for a specific variant.