chore: update angular and node, resolve package conflicts and vulnerability #72
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…l styles, updated angular to v14 the styles were moved to the assets folder for better consistency
EwoutV
force-pushed
the
version-bumps-2
branch
2 times, most recently
from
18a81b6 to
f6f1383
Compare
|
closes #43 |
smessie
reviewed
Feb 23, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The project now works fine with Node v18. All packages were updated (Angular v14) and vulnerabilities were resolved.
Since the Dockerfile has always used npm, the yarn lockfile has been removed (and should not be used anymore).