Skip to content

[Case Study] stylelint #369

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

Closed
7rulnik opened this issue Aug 20, 2019 · 4 comments
Closed

[Case Study] stylelint #369

7rulnik opened this issue Aug 20, 2019 · 4 comments
Assignees
Labels
case study Package compatibility report

Comments

@7rulnik
Copy link
Contributor

7rulnik commented Aug 20, 2019

What package is covered by this investigations?
stylelint

Describe the goal of the investigation
We should support stylelint because this is the most popular linting tool for CSS.

Investigation report
Seems that integration with yarn should be the same (#8) as with ESLint? But there is at least one problem: most popular vscode integration doesn't support configurable binary and maintainer closed issues for this project

@7rulnik 7rulnik added the case study Package compatibility report label Aug 20, 2019
@arcanis
Copy link
Member

arcanis commented Aug 20, 2019

Have you tried running it and see where it fails?

Regarding the VSCode integration, some projects disable issues because they expect people who care to submit PRs rather than issues, maybe that's the case here and @shinnn would be open to a contribution?

@ota-meshi
Copy link

Hello! Now the stylelint VSCode extension is maintained by the official team.
https://github.com/stylelint/vscode-stylelint

I would be grateful if you could comment on the work required to support Yarn2.
stylelint/vscode-stylelint#44

@7rulnik
Copy link
Contributor Author

7rulnik commented Apr 2, 2020

@arcanis seems that everything works (at least with my configuration). So our problem is editor integration.

@7rulnik
Copy link
Contributor Author

7rulnik commented May 11, 2020

Closed in #1011

@7rulnik 7rulnik closed this as completed May 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
case study Package compatibility report
Projects
None yet
Development

No branches or pull requests

3 participants