Skip to content
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

[question][licensing] Forking this project to use as Zed extension #623

Open
florian-sanders opened this issue Nov 9, 2024 · 0 comments

Comments

@florian-sanders
Copy link

florian-sanders commented Nov 9, 2024

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

  • 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?
  • Is Publish server part as a separate stylelint-language-server #110 still on the roadmap? If you need help I could try to help (after some time to get up to speed)
  • 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 🤔
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant