-
Notifications
You must be signed in to change notification settings - Fork 121
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
Extract Stylelint configuration for publish to NPM #5689
Conversation
**Why**: So that we can use the same configuration across our projects (e.g. 18f/identity-style-guide).
When testing this out in |
**Why**: So that it's easier to act on an error
Not used, only using its dependency "recommended"
I gave it a shot in d4a0219. Was quite straight-forward, with the main differences being:
Let me know if you have any concerns @mitchellhenke , but I'm feeling quite good about it. |
Looks good to me! 👍🏼 |
**Why**: Because they sometimes can't coexist
Related: 18F/identity-idp#5689 **Why:** So that we can use a common standard ruleset across all repositories where Sass is used.
Related: 18F/identity-idp#5689 **Why:** So that we can use a common standard ruleset across all repositories where Sass is used.
* Use login.gov shared Stylelint configuration Related: 18F/identity-idp#5689 **Why:** So that we can use a common standard ruleset across all repositories where Sass is used. * Fix dependency resolution for stylelint-config
Why: So that we can use the same configuration across our projects (e.g. 18f/identity-style-guide).