The configs themselves are cached in lib/config.js. See https://github.com/eslint/eslint/blob/master/lib/config.js#L246
On Tue, Sep 13, 2016 at 1:04 PM, adamc via ESLint <[email protected]> wrote: > Currently working on #3611 Glob based configuration > <https://github.com/eslint/eslint/issues/3611>, and specifically making > cacheing work. I noticed config files are cached in > config.localConfigFinder / FileFinder, but not the config contents. This > makes a little sense since merged directory configs are cached, but it's > also a weird since incremental cacheing is not utilized (i.e., traverse up > config hierarchy to nearest cache and merge from there; e.g., a/b is > cached, a/b/c is not, but config hierarchy is merged from scratch instead > of from a/b's cache). > > Is there a reason not to do this? I see none. The seemingly negligible > memory overhead of cacheing config files (since we're already cacheing > merged directory configs), seems more than worth the performance gains to > be had by not having to reload from fs and recompute (extends, plugins, > etc...) config files. > > -- > You received this message because you are subscribed to the Google Groups > "ESLint" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- ______________________________ Nicholas C. Zakas @slicknet Author, Principles of Object-Oriented JavaScript <http://amzn.to/29Pmfrm> Author, Understanding ECMAScript 6 <http://amzn.to/29K1mIy> -- You received this message because you are subscribed to the Google Groups "ESLint" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
