Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pnpm.allowedDeprecatedVersions should autoremove entries which are not needed anymore #5951

Open
1 task
mcmxcdev opened this issue Jan 19, 2023 · 0 comments
Open
1 task

Comments

@mcmxcdev
Copy link
Contributor

Describe the user story

Similar to #5949, it becomes tedious and time-consuming to manually manage allowedDeprecatedVersions.

This is how they look for a client project of mine:

"allowedDeprecatedVersions": {
  "@floating-ui/react-dom-interactions": "0.10.3",
  "@npmcli/move-file": "1.1.2 || 2.0.1",
  "@sinonjs/commons": "1.8.4",
  "chokidar": "2.1.8",
  "fsevents": "1.2.13",
  "querystring": "0.2.0",
  "readdir-scoped-modules": "1.1.0",
  "resolve-url": "0.2.1",
  "sane": "4.1.0",
  "sourcemap-codec": "1.4.8",
  "source-map-resolve": "0.5.3 || 0.6.0",
  "source-map-url": "0.4.1",
  "stable": "0.1.8",
  "urix": "0.1.0",
  "uuid": "3.4.0"
}

I can go through the lock file and check which versions are still in there or use pnpm why, but its better to do it automated.

Describe the solution you'd like

Detect which allowedDeprecatedVersions are not marked as deprecated anymore in the lockfile.

Additionally, make the allowedDeprecatedVersions be sorted alphabetically, to avoid git diffs and have it consistent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant