-
Notifications
You must be signed in to change notification settings - Fork 58
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
Deprecate unused+archived @npmcli
packages
#849
Comments
|
In handy script form to run with
|
Thanks @lukekarrys I'll run that ... not on a weekend. |
Gonna make a back-burner issue for |
Now that we have all our packages on the
@npmcli
team, it was easier to do something I've wanted to do before: map our packages to their GitHub repos and use in the CLI. Using this data as a signal I was able to identify a number of packages I think we should deprecate. All of the deprecations are to match repos that are already archived, although some of the repos were archived as part of my findings here.There is one outlier
npm-merge-driver
that I'm not sure what to do with. It's usage has been brought up before by other teams at GitHub. The repo is archived, but I'm not sure if it should be officially deprecated on the registry.Here are the packages I think we should deprecate and the message we should use to deprecate them:
Below is the full data I used to find the above packages to deprecate.
I went through it all manually since there are no perfect signals here. Eg: some deprecated packages map to active repos and some unused packages are tools that aren't used by the CLI but we don't want to deprecate/archive.
Full Data
The text was updated successfully, but these errors were encountered: