Suggestion: consistent package names on NPM
See original GitHub issueOne of the off-putting things about Koa vs other solutions is that it isn’t clear which NPM packages are maintained by the Koa authors and which are community efforts. I would like to stick to official Koa packages to get some degree of assurance.
It would be great if these packages had a common naming scheme on NPM.
My suggestion would be to follow the @koa/router
package:
- Koa main package
koa
- Router
@koa/router
- Body Parser
@koa/bodyparser
- Static
@koa/static
- etc…
This convention is already used by Babel.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:25
- Comments:9 (8 by maintainers)
Top Results From Across the Web
name-suggestion-index - npm
Start using name-suggestion-index in your project by running `npm i ... for suggesting consistent spelling and tagging in OpenStreetMap.
Read more >name-suggestion-index - npm Package Health Analysis - Snyk
The npm package name-suggestion-index was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as...
Read more >Tips and Tricks for NPM Package Management - Stout Systems
Node Package Manager (NPM) is a great tool that brings order to the world of ... to keep NPM dependencies up to date...
Read more >Custom Dependency Lists and Directories #10395 - GitHub
I like this idea as well: alternative syntax suggestion for consistency: npm install package-name --save-frontend.
Read more >Hunting typosquatters on npm - Scott Logic Blog
46% of npm package names have another name within a Levenshtein distance of 2 or less (64% for a distance of 3 or...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Out of curisosity, why having the main package outside of the
@koa
namespace?Why not having everything within the namespace?
This is what other projects, for example Material UI, and Babel, etc. do.
I can try to look at this once I’m done with other major projects.