New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ESLint v5.14.0 now requires Node.js to be compiled with crypto #11413
ESLint v5.14.0 now requires Node.js to be compiled with crypto #11413
Comments
Unfortunately, it looks like there wasn't enough interest from the team Thanks for contributing to ESLint and we appreciate your understanding. |
@nzakas Do we need to reopen this? |
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. |
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. |
Is this something we still need to look at? |
This is really just a sentence addition to the readme saying that ESLint requires crypto. |
Submitted #12475 |
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.
The text was updated successfully, but these errors were encountered: