Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[Feature request] Cache results
See original GitHub issueWhen running e.g. eslint and stylelint normally, I always add the --cache option which allows me to run linting significantly faster once the cache has been created.
For example, running eslint with the --cache option in one of our projects takes ~50 seconds to run initially. But running it again, after the first run, takes only around ~2 seconds, which is a lot quicker.
Is this something that could be possible to “hook into” from @betterer/eslint and @betterer/stylelint? Or, if not, would it maybe be possible to create something similar for Betterer in general?
Issue Analytics
- State:
- Created 2 years ago
- Comments:11 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Closing this, pretty happy how it’s working! I have some work in progress for full parallelisation too which should improve things further.
Hey @Svish, I just did some more perf fixes (and I have some ideas for the TS performance too), would you mind updating and seeing if you have improvements?