-
Notifications
You must be signed in to change notification settings - Fork 497
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
Stylelint #1648
Labels
language
A request to add a language extension
Comments
1 task
florian-sanders
added a commit
to florian-sanders/extensions
that referenced
this issue
Nov 29, 2024
florian-sanders
added a commit
to florian-sanders/extensions
that referenced
this issue
Nov 29, 2024
florian-sanders
added a commit
to florian-sanders/extensions
that referenced
this issue
Nov 30, 2024
florian-sanders
added a commit
to florian-sanders/extensions
that referenced
this issue
Dec 2, 2024
florian-sanders
added a commit
to florian-sanders/extensions
that referenced
this issue
Feb 28, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Check for existing issues
Language
CSS, SCSS, css-in-js
Tree Sitter parser link
No response
Language server link
https://github.com/stylelint/vscode-stylelint
Misc notes
Context
I am currently working on a zed-stylelint extension.
The extension seems to work properly but I still consider it Work In Progress for several reasons:
css-in-js
mostly),npm
and only publishes the source code on the repo. Since it's a TypeScript project it needs to be built + bundled and I couldn't find how to run npm commands that are async from thezed_extension_api
🤔npm
so I don't have to maintain a fork (see stylelint/vscode-stylelint #623.It seems the Sublime text Stylelint extension also has the same strategy of bundling the VSCode extension code: https://github.com/sublimelsp/LSP-stylelint/tree/master/language-server
Questions
Other Zed users asking for Stylelint LSP
Couldn't find much but Stylelint was mentionned in zed-industrices/zed #5612
The text was updated successfully, but these errors were encountered: