Skip to content
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.

Bring back nomnom 🙏 #19875

Closed
astorije opened this issue Feb 21, 2018 · 4 comments
Closed

Bring back nomnom 🙏 #19875

astorije opened this issue Feb 21, 2018 · 4 comments
Labels

Comments

@astorije
Copy link

https://www.npmjs.com/package/nomnom has been deprecated, while hundreds of packages rely on it. I have noticed this because https://www.npmjs.com/package/jsonlint is now broken (see zaach/jsonlint#103, zaach/jsonlint#105) and since the package is not actively maintained, it is bound to be broken forever.

nomnom is downloaded between 30k times per day during weekends and 150k times per day during weekdays, so it's very likely a lot of projects are suffering from this.

FYI, I have pinged you on Twitter before opening an issue on the repo.

@kenany
Copy link
Contributor

kenany commented Feb 21, 2018

Perhaps this should be moved to https://github.com/npm/registry?

@j-brown
Copy link

j-brown commented Feb 21, 2018

I find this curious, as nomnom is #365 on the top 1000 most depended upon packages: https://gist.github.com/anvaka/8e8fa57c7ee1350e3491

Was nomnom owned/maintained by npm?

@ehsalazar
Copy link

👋 zaach/jsonlint#103 (comment)

@astorije
Copy link
Author

Thanks for taking action, @ehsalazar!

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

No branches or pull requests

4 participants