Good strategy for upgrading Nodejs from version 16 to the latest LTS 22? #14033
              
                Unanswered
              
          
                  
                    
                      nkamp
                    
                  
                
                  asked this question in
                Help/Questions
              
            Replies: 1 comment 1 reply
-
| 
         有一个npm可以忽略这种版本冲突的约束判断。  | 
  
Beta Was this translation helpful? Give feedback.
                  
                    1 reply
                  
                
            
  
    Sign up for free
    to join this conversation on GitHub.
    Already have an account?
    Sign in to comment
  
        
    
Uh oh!
There was an error while loading. Please reload this page.
-
I am in the process of upgrading Nodejs (+NPM) from Nodejs version 16 to 22.
I also want to upgrade all Vue web dependencies.
I first did the ‘dependencies’ part and am now working on ‘devDependencies’ in package.json.
6 Repeat steps 4 & 5
This way, I can continue, but it takes a lot of time. Because in the root project there is a dependency for example "eslint": "9.38.0."
Then there is a devDependency with an 'transistive' dependency that uses eslint. This conflicts with the version eslint 9.38.0. Then I have to find which version of the dependency works with eslint 9.38.0.
Another example:
I also have a dependency that works with luxon 1.12.1, but luxon dependency is also defined in the root project. However, I cannot upgrade the dependency in the root project to version 3.5.4 because that conflicts with the dependency that the 'transistive' dependency luxon 1.12.1 uses.
In short, what is a good strategy in this case?
Beta Was this translation helpful? Give feedback.
All reactions