Skip to content

Support use-node-version value in .npmrc #1130

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

Open
dr3 opened this issue Sep 11, 2024 · 3 comments · May be fixed by #1149 or #1253
Open

Support use-node-version value in .npmrc #1130

dr3 opened this issue Sep 11, 2024 · 3 comments · May be fixed by #1149 or #1253
Assignees
Labels
feature request New feature or request to improve the current logic

Comments

@dr3
Copy link

dr3 commented Sep 11, 2024

Description:
Allow node-version-file value of .npmrc and read use-node-version key

Justification:
This method of defining is quite popular, and is documented for use by pnpm
https://pnpm.io/npmrc#use-node-version

Are you willing to submit a PR?
Yep if desired

@dr3 dr3 added feature request New feature or request to improve the current logic needs triage labels Sep 11, 2024
@aparnajyothi-y
Copy link
Contributor

Hello @dr3, Thank you for creating this feature request and we will get back to you once we have some feedback on this :)

@aparnajyothi-y
Copy link
Contributor

Hello @dr3, Thank you for your suggestion and for referencing PNPM’s support for the use-node-version field in .npmrc. We appreciate the thought you’ve put into how this feature could streamline version management and enhance compatibility for PNPM users.
After internal review, we’ve decided not to move forward with this enhancement at this time. While we recognize the potential value it could bring to specific workflows, we haven’t seen enough broader demand or adoption to justify the added complexity and maintenance this feature would introduce.

We’ll continue to monitor interest in this area and are open to revisiting the idea in the future as the ecosystem evolves. We appreciate your contribution and encourage you to share any additional feedback to help guide future improvements.

@aparnajyothi-y aparnajyothi-y self-assigned this May 15, 2025
@aparnajyothi-y
Copy link
Contributor

Hello everyone, We’ve noticed some concerns reflected by the reactions to the previous message. We truly appreciate the community’s honest feedback and want to assure you that every suggestion is carefully considered.

Our decision to pause on this enhancement is based on weighing the broader impact and maintenance overhead alongside current demand. We remain open to revisiting this in the future as more users express interest or as the ecosystem evolves.

Thank you for your continued engagement and for helping us prioritize improvements that benefit the wider community.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New feature or request to improve the current logic
Projects
None yet
2 participants