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

refactor: Renaming packages from @volar/vue-* to @vue/* #3134

Merged
merged 5 commits into from May 6, 2023

Conversation

johnsoncodehk
Copy link
Member

@johnsoncodehk johnsoncodehk commented May 6, 2023

close #2437

Changes:

  • @volar/vue-language-server -> @vue/language-server
  • @volar/vue-language-service -> @vue/language-service
  • @volar/vue-language-plugin-pug -> @vue/language-plugin-pug
  • @volar/vue-language-core -> @vue/language-core
  • @volar/vue-typescript -> @vue/typescript

@johnsoncodehk johnsoncodehk changed the title refactor: Renaming packages refactor: Renaming packages from @volar/vue-* to @vue/* May 6, 2023
@johnsoncodehk johnsoncodehk merged commit 214d935 into master May 6, 2023
6 checks passed
@johnsoncodehk johnsoncodehk deleted the pkgs-rename branch May 6, 2023 07:34
@yaegassy
Copy link
Collaborator

yaegassy commented May 7, 2023

Hi @johnsoncodehk, It seems that the renamed package has not been published to npm yet. (e.g. @vue/language-server)

Will it be published to npm at version 2.0?

@johnsoncodehk
Copy link
Member Author

I can't publish packages for @vue/* at the moment, probably due to permissions, I'm checking it out with Evan.

btw 1.7.x pre-release may update some breaking changes randomly, if coc-volar will update it, I suggest you release it with "next" tag instead of "latest" tag before 2.0.

@johnsoncodehk
Copy link
Member Author

Just released these.

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

Successfully merging this pull request may close these issues.

Rename packages in 2.0 -> 1.8
2 participants