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.

Sign up for GitHub

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

Jump to bottom

Support current Node LTS #1408

Open
ghost opened this issue Oct 31, 2019 · 5 comments
Open

Support current Node LTS #1408

ghost opened this issue Oct 31, 2019 · 5 comments
Labels
feature good first issue Hactoberfest help wanted

Comments

@ghost
Copy link

ghost commented Oct 31, 2019

Latest LTS Version: 12.13.0 (includes npm 6.12.0)
@sobolevn
Copy link
Member

Awesome! @jhabdas are you willing to help?

@ghost
Copy link
Author

ghost commented Oct 31, 2019

Perhaps. I can see the manifest specifies the engines. Why use NVM?

@sobolevn
Copy link
Member

I use it for historic reasons. What are the alternatives?

@ghost
Copy link
Author

ghost commented Oct 31, 2019

Let me take a look. I might have some good Hacktoberfest ideas.

@ghost
Copy link
Author

ghost commented Nov 1, 2019

Idea is to drop NVM and run stack in arch container for determinism. IMHO NVM makes switching engines easier but causes side effects like this which could lead to unexpected consequences and variance between machines and platforms.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature good first issue Hactoberfest help wanted
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sobolevn