Like the Did you mean? in git for npm
const meant = require('meant')
const result = meant('foa', ['foo', 'bar', 'baz'])
// => [ 'foo' ]
Download node at nodejs.org and install it, if you haven't already.
npm install meant --save
npm install
npm test
> meant@1.0.0 test /Users/watilde/Development/meant
> standard && tap test.js
TAP version 13
# Subtest: test.js
# Subtest: test vs ['tast', 'tbst', 'tcst', 'foo']
ok 1 - list has tast
ok 2 - list has tbst
ok 3 - list has tcst
ok 4 - list doesn't have foo
1..4
ok 1 - test vs ['tast', 'tbst', 'tcst', 'foo'] # time=11.816ms
1..1
# time=44.006ms
ok 1 - test.js # time=249.154ms
1..1
# time=267.371ms
None
npm version with automatic CHANGELOG generationMIT
Generated by package-json-to-readme
FAQs
Like the `Did you mean?` in git for npm
We found that meant demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
An advanced npm supply chain attack is leveraging Ethereum smart contracts for decentralized, persistent malware control, evading traditional defenses.
Security News
Research
Attackers are impersonating Sindre Sorhus on npm with a fake 'chalk-node' package containing a malicious backdoor to compromise developers' projects.
Security News
The npm package for the LottieFiles Player web component was hit with a supply chain attack after a software engineer's npmjs credentials were compromised.