Open salcock opened 18 hours ago
Node 16 is no longer supported, so we will not be getting any security updates or be able to use new packages.
First, we need to make sure that the existing code will run on a newer version of Node and make any necessary fixes to support this.
This will most likely require replacing some dead dependencies and dealing with upstream API changes for the dependencies that we continue to use.
Then, Shane can update the deployment containers to use a newer Node and test that everything still works as expected.
It's going to be a bit of a painful job, but we should try to do it sooner or later...
Node 16 is no longer supported, so we will not be getting any security updates or be able to use new packages.
First, we need to make sure that the existing code will run on a newer version of Node and make any necessary fixes to support this.
This will most likely require replacing some dead dependencies and dealing with upstream API changes for the dependencies that we continue to use.
Then, Shane can update the deployment containers to use a newer Node and test that everything still works as expected.
It's going to be a bit of a painful job, but we should try to do it sooner or later...