Provide users with a way to customize how changes to files are detected for caching purposes

The version of ESLint you are using.

5.12.1

The problem you want to solve.

We are currently unable to realize the benefits of eslint’s result caching within our CI environment due to a combination of limitations related to file attribute preservation with common CI tooling and the current stat -based change detection implementation within eslint.

Your take on the correct solution to problem.

Add a --cache-strategy (working title) CLI option to enable customization of the useChecksum argument to file-entry-cache#create.

(see #11487)

Are you willing to submit a pull request to implement this change?

(see #11487 😉)

[montmanu]

@nzakas Thanks for the insight. I will review that policy.

To clarify, the request here is less about using a different checksum than it is about supporting the use of a checksum at all (instead of the file’s mtime which is the default) … currently, the underlying dep supports using an md5 checksum (the useChecksum argument to fileEntryCache#create) for detecting changes, but eslint does not use that feature and does not provide an API to enable its use. So the request here is to provide that API (while leaving the current / default implementation unchanged).

[eslint-deprecated[bot]]

Unfortunately, it looks like there wasn’t enough interest from the team or community to implement this change. While we wish we’d be able to accommodate everyone’s requests, we do need to prioritize. We’ve found that issues failing to reach accepted status after 21 days tend to never be accepted, and as such, we close those issues. This doesn’t mean the idea isn’t interesting or useful, just that it’s not something the team can commit to.

Thanks for contributing to ESLint and we appreciate your understanding.