Nodejs 20 Upgrade

[Arique1104]

Update the Nodejs version to 18 to avoid Twilio deprecation.
Stephanie & Daniel

[Arique1104]

Updated code: https://github.com/MoveOnOrg/Spoke/pull/2310

[Arique1104]

If nothing breaks at version 18, please stretch to Nodejs version 20

[Arique1104]

Learning goals:

• @slyarbo2 will continue to test Node18 update on their local and then create a pull request to that StateVoicesNational/Spoke instance for approval!

[dwbond]

Setting the 20 stretch goal aside and focusing on 18

upgrade procedure:

1. change package.json engine for node and npm, and .nvmrc
2. install new node version with nvm (node version manager) nvm install v18.18.2 (and make it the default with nvm alias default v18.18.2)
3. update new packages with npm (node package manager) npm update
4. see if any issues can be automatically resolved with npm audit fix
5. force available automatic updates with npm audit fix --force
6. dependency adventures!
7. tests
8. save newly updated packages to package.json with npm update --save

package audit output https://pastebin.com/SmiraX5H

[Arique1104]

• Package upgrades that cause conflicts.
• Successfully updated 800 packages.
• Attempt to pass all the test cases on all the stuff that is supposed to be smooth sailing.
• To what extent does this work with current updates?
• How to tackle the next errors afterwards?

[dwbond]

Output from yarn install flags dependency issues https://pastebin.com/gezGMu8V

[dwbond]

full changes, upgraded to main for easier merging (Stephanie was running a pre- 13.1 version + seems to have been pushing to an inaccessible Github account) https://github.com/StateVoicesNational/Dispatch/tree/node18

[dwbond]

Test case output does not run successfully

https://pastebin.com/5FeCTnn0

[Arique1104]

BLOCKER FOR FINISHING NODE18 UPDATE: ProgressiveCoders#6

[Arique1104]

What did you learn?

• We upgrade all the packages: tun of warnings
• Load it up on the browser and it seems to be okay??
• Our whole frontend framework needs to be updated from v4 to v5. Could be a heavy lift! CSS class renaming and fun stuff like that.
• AWS they are not supporting the SD service for next year.
• Smaller packages that are not able to "forced fixed" requiring manual intervention.
• All test cases are failing currently....that's breaking also. Looking at version 18 specific test suite!

Priorities for tomorrow:

• Creating the issue tickets for what needs to be updated. Starting their issue with NODE UPDATE: name-of-update-needed
• Prioritize the No Fix Available and then group the fix available updates as one ticket.

There are a variety of different references for the Node that we are using.