nodejs / nodejs/package-maintenance
Upgrading Problems - Can we help?
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 423
- Forks
- 147
- PR merge metrics
- No merged PRs in 30d
Description
This is a copy of the text posted in: nodejs/user-feedback#116 which was posted Oct 26 2018:
As Node.js 10.x becomes LTS next week,now is a good time to consider upgrading.
We understand that there are stometimes issues when migrating to a newer Node.js major version.
One of the things we have heard is that this can be due to a module in the dependency chain that is not being updated.
We would like to gather some feedback and better understand how we can improve the migration experience.
Sme questions we would like to float to the community:
What challenges do you have when you upgrade to a newer Node.js major release?
Have all modules you depend on been updated?
Which specific modules do you have problems with when upgrading. And more specifically are there any modules preventing you from migrating to 10.x?
Are you a maintainer that is overwhelmed and you are not able to update your modules anymore?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the copied discussion in nodejs/user-feedback#116 and reviewing the migration questions in this issue. The issue does not name files, tests, or a specific change; it would need an agreed, concrete maintenance or migration action before completion could be measured.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100