Error: EISDIR: illegal operation on a directory

[Lngramos]

Running sass-lint . fails on my system, throwing the following error:

fs.js:603
  var r = binding.read(fd, buffer, offset, length, position);
                  ^

Error: EISDIR: illegal operation on a directory, read
    at Error (native)
    at Object.fs.readSync (fs.js:603:19)
    at Object.fs.readFileSync (fs.js:438:24)
    at /Users/myuser/projects/my-project/node_modules/sass-lint/index.js:180:18
    at Array.forEach (native)
    at Function.sassLint.lintFiles (/Users/myuser/projects/my-project/node_modules/sass-lint/index.js:178:9)
    at detectPattern (/Users/myuser/projects/my-project/node_modules/sass-lint/bin/sass-lint.js:16:18)
    at /Users/myuser/projects/my-project/node_modules/sass-lint/bin/sass-lint.js:91:5
    at Array.forEach (native)
    at Object.<anonymous> (/Users/myuser/projects/my-project/node_modules/sass-lint/bin/sass-lint.js:90:16)

I'm running Node v4.2.4 and the latest version of sass-lint (v1.5.1) on OS X 10.11 and fails with and without default config files.

[DanPurdy]

How're you running sass-lint? From the CLI? If so which command did you use?

[Lngramos]

Yeah, from the CLI, simply by running sass-lint . as mentioned above.

I've also attempted running it via an npm script using the same command.

[nene]

I ran into the same thing.

Coming from scss-lint I assumed that sass-lint would scan a directory for .sass & .scss files. But apparently it doesn't - it just blindly attempts to read the directory as a file.

Workaround: sass-lint 'path/to/**/*.scss'

[DanPurdy]

Maybe we weren't so specific but it does mention the globbing and including of a file extension in the docs for the CLI and config file include section.

This probably should change though. Thanks 👍

[mischkl]

It would be nice if running sass-lint from the command line would auto-detect a sass-lint.yml file in the same directory. Also it might be nice to at least get feedback about the number of warnings, even when not in verbose mode. Otherwise it looks like nothing happened. :)

[DanPurdy]

I found the cause of this, if running sass-lint without any options the default glob would match folders labelled like the following 'o.scss' which happens the appear in the sass-graph package which is a dependency of node-sass. If you dont pass options to sass-lint the chances are it attempted to lint your node modules and came across this.

The fix should be with you for 1.8.0