Skip to content
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

no-insecure-random fails when ESLint is not in the same directory. #17

Closed
A-Katopodis opened this issue Nov 2, 2021 · 0 comments · Fixed by #20
Closed

no-insecure-random fails when ESLint is not in the same directory. #17

A-Katopodis opened this issue Nov 2, 2021 · 0 comments · Fixed by #20

Comments

@A-Katopodis
Copy link
Contributor

Describe the bug
The rule no-insecure-random is requiring ESLint.
const eslint = require("eslint/lib/eslint");
If ESLint is installed in a different directory from the plugin this will lead to an error.

To Reproduce
Steps to reproduce the behavior:

  1. Create a code with insecure random algorithm. E.x. crypo.pseudoRandomBytes
  2. Install ESLint in a different directory from the plugins.
  3. Add the resolve-plugin-relative-to command to load those plugins.

Expected behavior
The rule should run properly without any crashes and not requiring ESLint.

A-Katopodis added a commit that referenced this issue Nov 3, 2021
no-insecure-random fails when ESLint is not in the same directory. #17
@A-Katopodis A-Katopodis linked a pull request Nov 3, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant