You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently working on an extension for the Zed editor to provide LSP features for Stylelint (see zed-stylelint).
Since the language server is not a standalone project (see #110), I decided to fork this repo to provide a prebuilt (build + bundle) version of this package (see vscode-stylelint-prebuilt).
Questions
Is the fork acceptable as long as this project is legitimately credited? I'm asking because I do realize that this repo is designed for a VSCode extension and I'm using it for Zed so maybe that's not something you are okay with?
Have you considered publishing the built + bundled code (extension code + language server) on npm? I've seen a few vscode LSP extensions doing that and it makes it easier to port them to other code editors. For instance this would remove the need for the fork in my case 🤔
The text was updated successfully, but these errors were encountered:
Context
I'm currently working on an extension for the Zed editor to provide LSP features for Stylelint (see zed-stylelint).
Since the language server is not a standalone project (see #110), I decided to fork this repo to provide a prebuilt (build + bundle) version of this package (see vscode-stylelint-prebuilt).
Questions
npm
? I've seen a few vscode LSP extensions doing that and it makes it easier to port them to other code editors. For instance this would remove the need for the fork in my case 🤔The text was updated successfully, but these errors were encountered: