Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Most of our repositories are currently using Node v8 or v12. As node v8’s support ended on 31st December 2019 and node v12’s support is scheduled to end on 30th April 2022, we’re going to start upgrading our repositories to node v16.

...

(we’ll consider adding a modernizer to automate this phase as well but as of now it’s going to be a manual step taken by the owning team).

If applicable, please update the status in this sheet as well Node 16 upgrade status tracking

Steps to deploy an MFE on Node 16:

...

Helpful local testing notes for testing out enterprise repos against node 16

In case someone decides to try this, here are the tailored node ‘tryout’ instructions. I can move this to a doc if that works better. Consulted with @astankiewicz before sending this outTo test enterprise MFEs against frontend-enterprise changes locally

  • Install nvm locally (you can use other node manages too this is just what I use)

  • Sync this branch of frontend-enterprise with Adam’s fixes: https://github.com/openedx/frontend-enterprise/pull/250

  • Start completely clean, remove node_modules/, package-lock file (it will all need to be regenerated)

  • update .nvmrc file to v16 if not already

  • nvm use (nvm will ask to install node16 if not already on your system)

  • Verify node is now 16 and npm is v8

...