Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update website to use a modern / currently supported stack #110

Closed
augusto-herrmann opened this issue Apr 22, 2021 · 0 comments · Fixed by #111
Closed

Update website to use a modern / currently supported stack #110

augusto-herrmann opened this issue Apr 22, 2021 · 0 comments · Fixed by #111
Labels
Website The frontend of publicbodies.org website

Comments

@augusto-herrmann
Copy link
Collaborator

The website uses very early node.js and express framework. Most libraries used are either deprecated, have been substituted for new versions (e.g. jade -> pug) or are no longer supported. npm reports that the package versions used have many vulnerabilities, some of which are classified as "high" and "critical".

As per the log when trying to run it on node.js 12:

npm WARN deprecated [email protected]: Updated API and improved functionality.
npm WARN deprecated [email protected]: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated [email protected]: this library is no longer supported

> [email protected] install /home/node/portal/node_modules/leveldown
> node-gyp-build

npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN [email protected] license should be a valid SPDX license expression

added 159 packages from 149 contributors and audited 160 packages in 11.598s

13 packages are looking for funding
  run `npm fund` for details

found 29 vulnerabilities (10 low, 11 moderate, 7 high, 1 critical)
  run `npm audit fix` to fix them, or `npm audit` for details

We need to port the website to current javascript and node.js. Alternatively, it could also could be reimplemented on another language and framework that is currently supported.

@augusto-herrmann augusto-herrmann added the Website The frontend of publicbodies.org website label Apr 22, 2021
This was referenced Apr 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Website The frontend of publicbodies.org website
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant