`npx eslint-nibble` fails, because it uses `require`
See original GitHub issueInstead of using bare require
, eslint-nibble should use require(resolve(path, { cwd: process.cwd() }))
and https://npmjs.com/resolve, so it doesn’t have to be installed locally.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:4
- Comments:12 (10 by maintainers)
Top Results From Across the Web
eslint-nibble - npm
Start using eslint-nibble in your project by running `npm i eslint-nibble`. There are 9 other projects in the npm registry using eslint-nibble.
Read more >How to fix just one rule using eslint - Stack Overflow
To fix the issues caused by just one rule, you need to combine --fix --rule with --no-eslintrc . Otherwise your rule will just...
Read more >Command Line Interface - ESLint - Pluggable JavaScript Linter
A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.
Read more >@mizdra/eslint-interactive NPM | npm.io
However, eslint-interactive is installed locally, so you need to add npx . ... the format to be used for the `Display problem messa...
Read more >eslint-nibble - Bountysource
No issues · package.lock.json size $ 0 · `npx eslint-nibble` fails, because it uses `require` $ 0 · Esprint integration $ 0 ·...
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 Free
Top 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
I just tried running
npx eslint-nibble .
in one of my projects, and it worked just fine. Maybe npx has made improvements. I’m going to close this out, but speak up if you still experience problems.It shouldn’t need those flags to work tho.