Closed mdshamoon closed 3 weeks ago
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 59.25%. Comparing base (
177bf8b
) to head (03d6f16
).
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
@mdshamoon should we release this on staging for a 1-2 days before merging?
@Ishankoradia makes sense. Lets do this today.
@mdshamoon done (on staging).
Upraded node to 18.20.3
and corresponding npm to 10.7.0
.
Had to delete and re-create the pm2 process for webapp since it was still reading the old nodejs version. Only restarting the process didn't work
@mdshamoon merging this. Updated next on beta also.
@Ishankoradia @mdshamoon when you upgrade things please record the commands you used in the ticket
on production i ran nvm install 18.20.3
which upgraded npm to 10.7.0
pm2 was using the 18.16
so i added interpreter: "/home/ddp/.nvm/versions/node/v18.20.3/bin/node"
to the top of the ecosystem.config.js
file
before that i ran yarn global add pm2@latest
and pm2 update
which had no effect that i could see
when versions change please also update platform-infra
: https://github.com/DalgoT4D/platform_infra/issues/38
@Ishankoradia @mdshamoon when you upgrade things please record the commands you used in the ticket
on production i ran
nvm install 18.20.3
which upgraded npm to10.7.0
pm2 was using the
18.16
so i addedinterpreter: "/home/ddp/.nvm/versions/node/v18.20.3/bin/node"
to the top of theecosystem.config.js
filebefore that i ran
yarn global add pm2@latest
andpm2 update
which had no effect that i could seewhen versions change please also update
platform-infra
: DalgoT4D/platform_infra#38
@fatchat i mentioned in the above comment that I had to delete the pm2 process and create a new one to start the webapp from new node version. pm2 doesn't understand the new version somehow.
Summary
Next js v14 update