Outdated dependencies

[damianstasik]

New Issue Checklist

• I am not disclosing a vulnerability.
• I am not just asking a question.
• I have searched through existing issues.
• I can reproduce the issue with the latest versions of Parse Server and Parse Dashboard.

Issue Description

Currently, most of the dependencies from package.json are outdated, some of them have a vulnerability reported by npm audit. I created this ticket to keep track of the progress, as I think the best way to get everything updated is to update everything one by one which helps with testing and debugging what went wrong.

Steps to reproduce

Run any command that checks for dependency updates.

Actual Outcome

• @babel/runtime
• bcryptjs
• commander
• graphiql
• graphql
• history
• immutable
• package-json
• react
• react-ace
• react-dnd
• react-dnd-html5-backend
• react-dom
• react-helmet
• react-popper-tooltip
• react-redux
• regenerator-runtime
• semver
• @actions/core
• @babel/core
• @babel/plugin-proposal-decorators
• @babel/plugin-transform-regenerator
• @babel/plugin-transform-runtime
• @babel/preset-env
• @babel/preset-react
• @semantic-release/changelog
• @semantic-release/commit-analyzer
• @semantic-release/git
• @semantic-release/github
• @semantic-release/npm
• @semantic-release/release-notes-generator
• all-node-versions
• babel-loader
• core-js
• cross-env
• css-loader
• eslint
• eslint-plugin-jest
• eslint-plugin-react
• http-server
• jest
• marked
• node-sass
• path-to-regexp
• puppeteer
• react-test-renderer
• sass-loader
• semantic-release
• style-loader
• webpack
• webpack-cli
• yaml

Expected Outcome

There should not be any outdated dependency, or at least all dependencies included in npm audit should be fixed.

Environment

Node v14.17.3

Dashboard

• Parse Dashboard version: 3.3.0-alpha.14
• Browser (Safari, Chrome, Firefox, Edge, etc.): n/a
• Browser version: n/a

Server

• Parse Server version: n/a
• Operating system: n/a
• Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): n/a

Database

• System (MongoDB or Postgres): n/a
• Database version: n/a
• Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc): n/a

Logs

[parse-github-assistant]

Thanks for opening this issue!

• 🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.

[mtrezza]

@visualfanatic That's quite an effort - hats off! Maybe you could reduce your work if you combine dependency upgrades that are not major version upgrades into 1 common PR. We trust that the package maintainers follow semver, so we usually do not test anything manually if the CI passes and it's not a major version upgrade.

[mtrezza]

Upgrading semantic-release 17.4.6 → 18.0.0 requires Node 16 in the CI as well. A PR for that should include the related dependencies @semantic....

[parseplatformorg]

🎉 This change has been released in version 5.1.0-beta.2

[parseplatformorg]

🎉 This change has been released in version 5.1.0-alpha.11

[parseplatformorg]

🎉 This change has been released in version 5.1.0