npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I’ll try
to do my best with it!
In target settings under the web section there is a node setting there I have not updated my version just yet but I would assume this is how to upgrade not tried this though
The node version on your host computer has nothing to do with the node version that runs inside the Docker container - follow Sorry_Duh’s suggestion to change the version in your project settings, which in turn will update your docker-compose file to use the new version
Hey John, Were there any unintended side effects upgrading Node in the target settings? Would appreciate any experience you could share. Thanks for going out there ahead of us !
Interesting, I just upgraded to Node 16 and the site seems to have lost the database connection. This is multi tenant site and we get a 404 Page not found error on all the tenants. Although Navigating directly to the primary URL works successfully. Any troubleshooting suggestions would be welcomed. Thanks