What is the problem this feature will solve?
The NODE_OPTIONS environment variable allows configuration of the node process at runtime. This is inappropriate for Single Executable Applications. But the configurability provided is also something strictly desirable foe Single Executable Applications at "build" time.
What is the feature you are proposing to solve the problem?
- Store the
NODE_OPTIONS environment variable into the injected blob at build-time
- Use that value to override the environment
NODE_OPTIONS value at runtime
What alternatives have you considered?
I looked at enabling individual overrides via sea-config.json as well as possibly storing the actual environment settings and reconstructing these.
However that seems to be either less configurable as well as introducing additional complexity. By going this route, we'd expose the full configurability of NODE_OPTIONS while at the same time not introducing any strictly new mechanisms.
What is the problem this feature will solve?
The
NODE_OPTIONSenvironment variable allows configuration of the node process at runtime. This is inappropriate for Single Executable Applications. But the configurability provided is also something strictly desirable foe Single Executable Applications at "build" time.What is the feature you are proposing to solve the problem?
NODE_OPTIONSenvironment variable into the injected blob at build-timeNODE_OPTIONSvalue at runtimeWhat alternatives have you considered?
I looked at enabling individual overrides via sea-config.json as well as possibly storing the actual environment settings and reconstructing these.
However that seems to be either less configurable as well as introducing additional complexity. By going this route, we'd expose the full configurability of
NODE_OPTIONSwhile at the same time not introducing any strictly new mechanisms.