Stylelint failing silently as npm script

Question

I'm setting up stylelint for a project, everything works as expected when run from the cli:

$ stylelint 'css/**/*.css' --fix

css/style.css
 20:18  ×  Expected newline after ":" with a multi-line declaration declaration-colon-newline-after
...
...

However, when run as an npm script no output appears (beyond logging the command) and the errors seem to be ignored:

$ npm run stylelint

> project lint:css path/project
> stylelint 'css/**/*.css' --fix

package.json

  "scripts": {
    ...
    "stylelint": "stylelint 'css/**/*.css' --fix"
  },

Any idea how to get the console output AND exit on errors when stylelint is run as an npm script?

It actually seems `> stylelint 'css/**/*.css' --fix` doesnt run at all via `npm` regardless of the fact it logs out to the console — Vinnie James, Aug 22 '18 at 20:00
The issue is with the globstar pattern, as `"stylelint": "stylelint 'css/file.css' --fix"` runs as expected via npm — Vinnie James, Aug 22 '18 at 20:07

Vinnie James · Answer 1 · 2018-08-23T01:54:44.043

8

The issue turned out to be the quotes around the globstar pattern. Most other scripts allow you to wrap the globstar in single quotes ', however stylelint seems to require escaped double quotes:

"stylelint": "stylelint \"src/**/*.css\" --fix"

edited Aug 23 '18 at 01:54

answered Aug 22 '18 at 20:12

Vinnie James

5,763
6
43
52

3

You're my hero, Vinnie – kontrollanten Oct 07 '18 at 19:41
1

Not all heros wear masks ;) – Vinnie James Oct 08 '18 at 00:26

score 0 · Answer 2 · answered Nov 03 '20 at 19:44

0

Seems like appending ; exit 0 also does the trick:

"stylelint": "stylelint 'css/**/*.css' --fix; exit 0"

answered Nov 03 '20 at 19:44

sn3p

726
4
13

Thanks for the suggestion (which did not help in my case though). Could you please elaborate why this would help? – Ingo Steinke Nov 09 '22 at 18:05

Stylelint failing silently as npm script

2 Answers2