feat: Update and cleanup pnpm dependencies #399
Merged
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
…feature/update-node-deps
mkleszcz
previously approved these changes
Sep 22, 2023
mkleszcz
approved these changes
Sep 22, 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.
Please check if the PR fulfills these requirements
What kind of change does this PR introduce?
feature
What is the current behavior?
Lot's of outdated pnpm dependencies
What is the new behavior?
Updated most of pnpm packages to latest versions, changed code accordingly.
I also moved a lot of dependencies to the root package.json to avoid conflicts and ease of future updates. It's just too difficult to manage that many duplications of packages. It's also easier to avoid having multiple versions of the same library in code bundles.
I also added some CLI commands to webapp that I found helpful when working on this PR.
Does this PR introduce a breaking change?
no