Remove unused dependencies and use static versions#2021
Conversation
There was a problem hiding this comment.
Pull request overview
This PR tightens dependency management by pinning several packages to exact versions and removing unused Angular/Karma-related tooling from the Nx workspace.
Changes:
- Pin previously ranged dependencies (e.g.,
^x.y.z) to exact versions inpackage.jsonand syncpackage-lock.json. - Remove unused Karma/Jasmine-related dependencies and delete the
karma.conf.jsfile. - Simplify
nx.jsonby removing Karma/Angular-specific cache inputs and generator defaults.
Reviewed changes
Copilot reviewed 3 out of 4 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| package.json | Pins several dependencies to exact versions and removes Karma/Jasmine-related dev deps. |
| package-lock.json | Regenerated/updated lockfile to reflect the new pinned versions and removed packages. |
| nx.json | Removes references to karma.conf.js and Angular-specific Nx target/generator configuration. |
| karma.conf.js | Deletes the Karma configuration file (no longer used). |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "@nx/js": "20.5.0", | ||
| "@nx/node": "19.8.8", | ||
| "@nx/react": "20.5.0", | ||
| "@nx/storybook": "^20.0.8", | ||
| "@nx/storybook": "20.8.4", | ||
| "@nx/vite": "19.8.8", |
There was a problem hiding this comment.
@nx/storybook is pinned to 20.8.4 while several other @nx/* packages (and the top-level nx install) are at 19.8.8 / 20.5.0. In the lockfile this results in multiple Nx copies being installed (e.g., @nx/storybook brings its own @nx/devkit/nx 20.8.4), which can lead to subtle plugin/runtime incompatibilities and larger installs. Consider aligning all @nx/* (and nx) packages to a single Nx release line/version to keep the toolchain consistent.
|



Fixes OPS-3796.
Additional Notes