Open MattMatt27 opened 3 weeks ago
We shall review this @MattMatt27
@MattMatt27 This needs to be done across all repositories, including LAMP-server, LAMP-js, LAMP-worker, LAMP-dashboard, and LAMP-activities (for all activities). It will be a time-consuming process, and we need to thoroughly test each functionality after making the changes. We shall look into this.
Describe the bug I just tried making a very minor change to LAMP-platform (fix the favicon path) but the gh-release build failed and I am wondering if this is a more serious concern that requires addressing. It looks like a few of the packages are now expecting a Node.js version of 18 and we are still using 16. See build error below.
To Reproduce Steps to reproduce the behavior:
Expected behavior gh-release should succeed and changes should be reflected in the documentation
Desktop (please complete the following information):
Additional context Based on my understanding it seems like the two potential solutions are upgrading our Node.js version to 18. Or adding package specific version dependencies for all failing packages so that they continue to work on Node 16.