Consider using eslint-loader `cache` option
See original GitHub issue@kentcdodds mentioned he’s not using eslint-loader
because of perf issues.
Nobody reported them to us, so naturally we don’t know about them.
What kind of perf issues exist with eslint-loader
?
Can you tell me how to reproduce them?
Does enabling that cache
option (new in 1.5.0) help, and should we do it?
Issue Analytics
- State:
- Created 7 years ago
- Comments:22 (21 by maintainers)
Top Results From Across the Web
With eslint-webpack-plugin@2.4.1, how do you use ...
ESLint's node api has cache and cacheLocation keys in it, and setting those like const ESLintPlugin = require('eslint-webpack-plugin') ...
Read more >Node.js API - 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 >Eslint ignore
The function discards the characters in the stream until the given delimiter, inclusivebabel-loader yaml-frontmatter-loader cache-loader coffee-loader ...
Read more >VS Code ESLint extension - Visual Studio Marketplace
(see also ESLint class options#cwd). Please also keep in mind that the .eslintrc* file is resolved considering the parent directories whereas ...
Read more >vue/cli-plugin-eslint
To make lint errors show up in the browser overlay, you can use lintOnSave: 'error' . This will force eslint-loader to always emit...
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
It’s fixed on 1.0.1. whew! broke 2 project release because I wanted to contribute to eslint caching… T_T
Going to close as stale.