ESLint v5.14.0 now requires Node.js to be compiled with crypto

[nzakas]

I came across this on Twitter. It appears that upgrading file-entry-cache means that ESLint now requires Node.js to be compiled with crypto because of how the cache is generated now. More details:

nodejs/node#26182

We should decide if this is something we are okay with going forward.

I’m guessing there aren’t a lot of folks using Node.js without crypto, so maybe not a big deal, but at a minimum it seems like we should acknowledge this requirement in our docs somewhere.

[eslint-deprecated]

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.

[platinumazure]

@nzakas Do we need to reopen this?

[nzakas]

Yes, thanks for catching this! I filed it on mobile which didn't allow me to set an assignee, and it fell off my radar.

[kaicataldo]

Related issue from a while back: #5522

How do we want to proceed with this? Should we maybe bring this up in the next TSC meeting? Given we haven't seen any other issues, it doesn't seem like it's a widespread problem. That being said, if it's something that's easily fixable it could be worth changing to make it easier for Node core's tests.

[kaicataldo]

Is this something we still need to look at?

[nzakas]

This is really just a sentence addition to the readme saying that ESLint requires crypto.

[nzakas]

Submitted #12475