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

Don't try to access files that should be ignored. #680

Closed
purpleKarrot opened this issue Nov 10, 2016 · 1 comment

Comments

@purpleKarrot
Copy link

commented Nov 10, 2016

I have some files that cannot be accessed by the current user. Even though I have listed them in both ".gitignore" and "standard.ignore", I get the following output:

> standard --verbose | snazzy

standard: Unexpected linter output:

Error: EACCES: permission denied, scandir '...'
@feross

This comment has been minimized.

Copy link
Member

commented Jan 13, 2017

This happens with raw eslint, so it's not something that standard is doing. See:

$ ls -lha t.js
-rw-------  1 root  wheel    19B Jan 12 21:57 t.js
$ ./node_modules/.bin/eslint -c eslintrc.json .
EACCES: permission denied, open '/Users/feross/code/standard-stuff/standard/t.js'
Error: EACCES: permission denied, open '/Users/feross/code/standard-stuff/standard/t.js'
    at Error (native)
    at Object.fs.openSync (fs.js:640:18)
    at Object.fs.readFileSync (fs.js:508:33)
    at processFile (/Users/feross/code/standard-stuff/standard/node_modules/eslint/lib/cli-engine.js:302:21)
    at executeOnFile (/Users/feross/code/standard-stuff/standard/node_modules/eslint/lib/cli-engine.js:672:25)
    at fileList.forEach.fileInfo (/Users/feross/code/standard-stuff/standard/node_modules/eslint/lib/cli-engine.js:710:13)
    at Array.forEach (native)
    at CLIEngine.executeOnFiles (/Users/feross/code/standard-stuff/standard/node_modules/eslint/lib/cli-engine.js:709:18)
    at Object.execute (/Users/feross/code/standard-stuff/standard/node_modules/eslint/lib/cli.js:171:107)
    at Object.<anonymous> (/Users/feross/code/standard-stuff/standard/node_modules/eslint/bin/eslint.js:74:28)

I suggest fixing the permission issue with the file, or if you feel strongly, open an issue on the ESLint bug tracker here: https://github.com/eslint/eslint/issues

@feross feross closed this Jan 13, 2017

@lock lock bot locked as resolved and limited conversation to collaborators May 10, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
2 participants
You can’t perform that action at this time.