Change Request: Eslintcache relative

[brenelz]

ESLint version

v8.26.0

What problem do you want to solve?

I am currently trying to use the .eslintcache file in our jenkins ci.

Is there anyway the cache can use relative file paths? In our instance each branch is in a seperate dir but I want to reuse the cache.

What do you think is the correct solution?

In order to move the .eslintcache around it would be great if the cache filePaths were relative

Participation

• I am willing to submit a pull request for this change.

Additional comments

No response

[mdjermanovic]

Hi @brenelz, thanks for the issue!

I think this is generally doable. We'd need to discuss details, like whether this needs a new option and what should be the base path (directory to which the file paths would be relative; would it be the current working directory, or location of the cache file, or something else). This is a non-trivial change in the core, so I think it should go through the RFC process, but let's hear more opinions from the team first.

[brenelz]

If its a non-trivial change its probably not worth it. Seems like no one has really asked for it besides me. We were just trying to use the cache in our ci which I think we are unable to do currently.

[brenelz]

Another option very specific to my use case would be if we could not include the path in hashOfConfig if that makes sense

[nzakas]

Yeah, we’d need an RFC for this as it has the potential to break current cache file usage.

[CSchulz]

Who can initiate this rfc request? We are also struggling with caching.

Why not using a hybrid scenario for the paths? Cutting the absolute path to a relative path and always store the relative path for the future.
As long as nobody moves the workspace around there is no breaking change for the cache itself.

[nzakas]

Anyone can initiate an RFC. Some people check in their cache file, so any change to the cache format is a breaking change. We can't know for sure where people are storing cache files or how else they might be used.

[CSchulz]

I can't believe anyone is using absolute paths if people want to check in their cache files.
Otherwise to prevent some breaking changes, can we add a third strategy for the cache using relative paths?

[nzakas]

@CSchulz you can feel free to propose whatever you want. As already stated, we would just need an RFC to consider it.