[Feature] Allow ignoring paths via package.json
See original GitHub issueI propose adding a second top level key to package.json
named eslintIgnore
that contains an array of paths to be ignored (or not).
Issue Analytics
- State:
- Created 6 years ago
- Comments:14 (7 by maintainers)
Top Results From Across the Web
package.json - npm Docs
This feature is helpful for local offline development and creating tests that require npm installing where you don't want to hit an external...
Read more >'package.json' is not under 'rootDir' - Stack Overflow
When using // @ts-ignore on top of the import call and setting "rootDir": "./src" it works. In this case enabling resolveJsonModule will ...
Read more >Configuring package.json · Jest
Use the <rootDir> string token to include the path to your project's root directory to prevent it from accidentally ignoring all of your...
Read more >Modules: Packages | Node.js v19.3.0 Documentation
Imported CommonJS modules have their URLs converted to absolute paths and are then loaded via the CommonJS module loader. package.json and file extensions#....
Read more >How To Use Node.js Modules with npm and package.json
Let's run through this example. In your locator application, you will use the axios library, which will help you make HTTP requests. Install...
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
As discussed in today’s TSC meeting, this issue is now accepted.
@HarrisonMc555 Ah, I see what you’re saying. There’s definitely assumed knowledge regarding how to upgrade a package using npm, but that isn’t specific to ESLint.
Maybe in the future we could include an install command and a link to npm’s docs? That being said, I think it’ll be difficult to always anticipate when that’s useful and when it’s extra noise - I think at some point it’s reasonable to assume knowledge about (or the ability to discover) how the package manager works.