-
This style of comment seems to be ignored when using ignores: ['js-comments'].
/*
I'm a comment and I cause issues!
*/
I've added to the JS comments tests and I'll take a look at fixing it, but …
-
In Node 4 `process.argv[0]` is `'/usr/local/bin/node'` and not just `'node'` as in 0.12.7, and because of that, the filter function at https://github.com/evanshortiss/lintspaces-cli/blob/master/index.…
-
May be the same issue as reported in https://github.com/schorfES/grunt-lintspaces/issues/21
It seems to appear when the comments have no leading indentation.
``` javascript
/*
* This is failing....…
-
-
![screen shot 2015-06-25 at 15 42 14](https://cloud.githubusercontent.com/assets/825088/8357070/d4404062-1b50-11e5-9a90-6fd8f98cc084.png)
Probably an upstream problem
-
``` logspeak
user@machine:~$ sudo npm install -g plaidchat
npm ERR! Linux 3.16.0-4-amd64
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "-g" "plaidchat"
npm ERR! node v0.12.7
npm E…
-
[But it looks like a problem with gulp-lintspaces]
```
npm WARN package.json fetchres@1.1.0 No repository field.
npm WARN package.json ft-next-express@7.9.2 No repository field.
npm WARN package.json…
-
When using `npm>2.7.5` the installation of `lintspaces` fails.
```
npm ERR! Linux 3.19.0-16-generic
npm ERR! argv "node" "/usr/bin/npm" "install" "--no-rollback"
npm ERR! node v0.12.2
npm ERR! npm v…
-
Some dependency versions that could be upgraded:
- `lodash 3.8.0`
- `grunt-jscs 1.8.0`
- `grunt-lintspaces 0.6.2`
- `grunt-contrib-jshint 0.11.2`
-
It looks like the pinned version of editorconfig being requested by node-lintspaces has some non Mac compatible pathing. The latest version of editor config does indeed install. Let me know if you nee…