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
Re-publish extension packages to npmjs.com
#65
Comments
I support the idea. We can not update https://github.com/neoclide/coc-stylelint without |
Thanks @guillaumewuip, publishing both the server and the client is what I’m thinking at least for starters, I will try to reach out to @shinnn again, and if no response I’ll see if we can organise something with npm to take over these packages |
Great, let me know if I can help :) |
I've reached out to npm to ask if we can adopt those packages, will let you know how that goes |
npmjs.com
npmjs.com
In #265, In the meantime, I think we should, if we've been able to get access, deprecate all three packages that currently exist on npm (listed in #65 (comment)). They won't ever receive any updates and have lost any use they might have had before. |
Hmm, I tried to deprecate the packages, doesn't seem to have worked, will look further later:
|
Looks like it's gone through now. Each has a deprecated warning on the page: |
Fantastic! This issue is effectively resolved then. We'll track the language server package in #110. |
The following 3 npm packages are published to npm, and have not been updated since this extension was moved to the @stylelint organization:
Options:
The text was updated successfully, but these errors were encountered: