Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reading additional Node command line options from the .env file. #2839

Closed
wants to merge 1 commit into from

Conversation

dfbaskin
Copy link
Contributor

Have not set up any additional tests for this yet, but wanted to confirm that this was a reasonable approach to specifying additional command line options on the spawned instance of Node.

As an example, you could give Node additional memory on a build by specifying the following in your .env file:

NODE_COMMAND_LINE_BUILD=--max-old-space-size=8192

Original issue is #2820

@Timer
Copy link
Contributor

Timer commented Aug 2, 2017

I'm not sure if this is exactly what I had in mind.
Is it possible to see what flags were passed to the node process?

If we use fork() instead of spawn() do we get the behavior we'd like; should we do that instead?

@dfbaskin
Copy link
Contributor Author

dfbaskin commented Aug 8, 2017

Superseded by #2913.

@dfbaskin dfbaskin closed this Aug 8, 2017
@lock lock bot locked and limited conversation to collaborators Jan 21, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants