chore(deps): Mark peer dependencies and update frontend packages #11385
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.
This pull request updates the
src/frontend/package-lock.jsonfile to improve dependency management and compatibility. The main change is the addition of the"peer": trueproperty to a large number of dependencies, which helps npm and other package managers correctly handle peer dependencies. Additionally, a few packages are updated to newer versions.Dependency Management Improvements
"peer": trueto many dependencies throughoutpackage-lock.json, ensuring that peer dependencies are explicitly marked and handled correctly during installation. This change affects packages such as@babel/core,@chakra-ui/styled-system,@codemirror/language,@types/react,acorn,chokidar,react,react-dom,rollup,tailwindcss,vite, and many others. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20] [21] [22] [23] [24] [25] [26] [27] [28] [29] [30] [31] [32] [33]Version Updates
devaluepackage from version5.6.1to5.6.2and updated its dependency reference insvelte. [1] [2]honopackage from version4.11.3to4.11.4.sveltepackage from version5.46.1to5.47.1.These changes will help ensure that your project’s dependencies are managed more reliably, reducing the risk of version conflicts and improving compatibility with other packages.