Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
Many of the frontend dependencies (node) are quite old and in need of an update
Approach
As I'm not very "front-end" proficient, I used advice from the net on how to perform the update, so I'd appreciate a check
The following commands were used for the update, in the
frontend
directory:# npx npm-check-updates -u
This updated the
package.json
file.# npm update
This updated the
package-lock.json
file.Additional notes
Updating the Typescript module from
4.x
to5.x
has caused some issues with thetsconfig.config.json
andtsconfig.json
files. While I don't understand how those work, I found a note in thevue/tsconfig
repo indicating some changes needed following the upgrade of from<5.0
. Among them, usingtsconfig.dom.json
instead oftsconfig.web.json
. In addition, it is indicated there that thetsconfig.node.json
file has been removed - so I've removed the"extends": "@vue/tsconfig/tsconfig.node.json"
from thetsconfig.config.json
file. Hope that's the correct approach.I've ran some basic test, all seems fine.