npm-keyword

Get a list of npm packages with keywords

by sindresorhus

Star on GitHub Forknpm

JavaScript

52 stars 8 forks 9 contributorsQuiet · 2y agoSince 2015 v8.0.0MIT

Meet the team

See all 9 on GitHub →

sindresorhus44 contributions

kevva3 contributions

mischah3 contributions

BendingBender2 contributions

eddiemonge1 contribution

Richienb1 contribution

ntwb1 contribution

tommy-mitchell1 contribution

Languages

View on GitHub →

JavaScript87.5%

TypeScript12.5%

Commit activity

Last 12 weeks · 0 commits

Full graph →

Community health

4 of 6 standards met

Community profile →

✓README✓License✓Contributing✓Code of Conduct○Issue Template○PR Template

Recent fixes

View closed PRs →

Target Node.js 18, use `ky`, switch to named exportsMergedPR

Uses over , and uses named exports:

tommy-mitchell · 2y ago

Move to GitHub ActionsMergedPR

Richienb · 5y ago

support private npm registry with authMergedPR

I've found that npm-keyword doesn't work if your .npmrc has a private npm registry configured that requires authentication. It always gets 401 responses. I've tested the following with a .npmrc with a private registry and without. Without a private registry and _auth, the getAuth function returns undefined and it behaves as it always has. All 11 tests pass. With a .npmrc, I ran npm test and all but the two count tests succeeded. I think this is more a problem with our private registry's API. Without the change, nothing passes. Example of .npmrc I hope you consider this pull request. Thanks!

kgoodridge · 6y ago

Structured data for AI agents

Repository: sindresorhus/npm-keyword. Description: Get a list of npm packages with keywords Stars: 52, Forks: 8. Primary language: JavaScript. Languages: JavaScript (87.5%), TypeScript (12.5%). License: MIT. Latest release: v8.0.0 (2y ago). Open PRs: 0, open issues: 0. Last activity: 2y ago. Community health: 85%. Top contributors: sindresorhus, kevva, mischah, BendingBender, eddiemonge, Richienb, ntwb, tommy-mitchell.