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

Check which other PRs are changing Node`s start code #70

Open
luminosuslight opened this issue Feb 12, 2018 · 0 comments
Open

Check which other PRs are changing Node`s start code #70

luminosuslight opened this issue Feb 12, 2018 · 0 comments

Comments

@luminosuslight
Copy link
Collaborator

luminosuslight commented Feb 12, 2018

We should check which other developers are currently working on the Node startup code and inform them about our proposed changes.

I found this RFC / PR by accident:
nodejs#17058

"Yeah, the key issue is that node.js startup is a Tangled mess of spaghetti code right now. From the way cli args and env vars are processed, to the order of start up events, etc. I've been looking at introducing a proper command line args parser and start up options isolation that will be tied to the Environment rather than using global state, then will be separating out the initialization of the process object. Once that is done, we should be able to refactor the bootstrap script into distinct phases."

"Status update on this side: I've started working on refactoring the native bootstrap lifecycle.... starting with how configuration and command line options are handled.... specifically, moving away from use of global variables to using a NodeOptions class associated with the Environment. From there, I will be working through a refactoring of how the process object is bootstrapped."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant