A broad upgrade of NPM and Webpack scripts is needed. The GitHub Action was running npm 8 and failed to download some very old dependencies.
Workaround
As the website was not even browsable, I found a workaround.
The /public directory actually contains the static files that can no longer be computed. They were hardversioned in Git at some point in time. Rather than keeping the whole website down, I submitted a Pull Request that simply skips the building of static files
So the standard workflow of the website is:
It fetches up-to-date Crowdin data
It formats data into statistics.json file
It builds the website static files
It deploys the website
I have modified the CI to skip step 3. Currently the GitHub Action workflow does not build the static files anymore: we keep reusing the same, the ones in /public.
Long term solution
The right thing to do, but it needs more time, is to update the NPM dependencies in /front application to be able to run in the CI, which can then be piped in again inside the worklow. And resume step 3 instead of skipping it.
Until step 3 is not re-enabled, any change in the code of /front will not be active in production environment.
As of today, September 2023, this project is in Degraded Mode
Broken because of outdated code that does not build anymore
2 weeks ago, I realized this website was not working.
The GitHub Action that was supposed to deploy the website was failing. After a few easy fixes, the main problem was found: this project is running very outdated Node scripts.
A broad upgrade of NPM and Webpack scripts is needed. The GitHub Action was running npm 8 and failed to download some very old dependencies.
Workaround
As the website was not even browsable, I found a workaround.
The
/public
directory actually contains the static files that can no longer be computed. They were hardversioned in Git at some point in time. Rather than keeping the whole website down, I submitted a Pull Request that simply skips the building of static filesSo the standard workflow of the website is:
statistics.json
fileI have modified the CI to skip step 3. Currently the GitHub Action workflow does not build the static files anymore: we keep reusing the same, the ones in
/public
.Long term solution
The right thing to do, but it needs more time, is to update the NPM dependencies in
/front
application to be able to run in the CI, which can then be piped in again inside the worklow. And resume step 3 instead of skipping it.Until step 3 is not re-enabled, any change in the code of
/front
will not be active in production environment.