paragon
paragon copied to clipboard
`npm run lint` seems to be returning SCSS linting errors (but not failing CI?)
trafficstars
On master, I ran npm i and then npm run lint and it results in 3936 linting errors (sample in screenshot). But, interestingly, none of these errors fail CI?
AC
- Verify linting errors fail CI before PR merge
- Verify whether we need to fix/ignore the SCSS linting errors returned.
Hmm, we couldn't reproduce this locally, also I don't see any warnings in CI jobs that do linting check. Are you sure you were on the latest master and didn't have any changes in .eslitrc?
Closing this since the issue is not reproduced anywhere.