chore(deps): move duplicated dependencies to the pnpm catalog #257
No reviewers
Labels
No labels
dependencies
major
security-pin
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
trails-cool/trails!257
Loading…
Reference in a new issue
No description provided.
Delete branch "i18next-catalog"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
i18nextwas on the Renovate dashboard (#12) twice: once in the "production (non-major)" group and once in "development". #251 declared it in the apps'dependencies, and the rootpackage.jsonstill had it indevDependencies. Renovate groups by dependency type, so one update became two PRs.Six more packages had the same problem:
react-i18next,i18next-browser-languagedetector,leaflet,react-leaflet,fit-file-parserandlinkedom. All seven are now pnpm catalog entries, and every manifest that uses them references them withcatalog:. Renovate then updates one version in one place, in the production group.The root
devDependenciesfor these packages are removed. Each user declares its own:packages/i18n:i18nextandreact-i18nextas devDependencies. They are peers there, and its tests and typecheck need them.packages/fit:fit-file-parser(devDependency, for tests).packages/gpx:linkedom.The resolved versions do not change: i18next 26.4.3, react-i18next 17.0.16, i18next-browser-languagedetector 8.2.1, leaflet 1.9.4, react-leaflet 5.0.0, fit-file-parser 6.2.2, linkedom 0.18.13.
Test plan
pnpm install --frozen-lockfilepnpm typecheck,pnpm lint,pnpm testscripts/check-dockerfiles.shcheck-server-externals.mjs)🤖 Generated with Claude Code
https://claude.ai/code/session_01LQv5c9rFGq2hSPpjLiFmQ8