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
Roadmap #158
Comments
@egoist I'm already a supporter, but would it be possible to pay a one-time donation to request an article that discusses publishing vue components on NPM. With eg. the title:
I'm having a hard time finding resources that discuss the things above, and would be interested in getting your vision on the issue. |
The official guide demonstrates how to annotate props: https://v3.vuejs.org/guide/typescript-support.html#annotating-props It seems Vetur won't show type hints when you use components written in
Yes for me, many users don't use TypeScript at all. Doing this will also save some compile time for the user. |
@egoist did your opinion change on publishing components to NPM with Also, do you use (I'm looking for guidance on the best way to publish standalone Vue components.) |
Are you using Volar? It seems Volar won't pick up
|
@egoist thanks for your advice. Yeah, I switched to Volar from Vetur. if I go for:
will people still be able to use it in non-TS projects? |
yes |
@egoist thanks for the clarification! I might prepare a separate import path for the |
using the rollup plugin? or use Vite |
@egoist cheers! i'm going to test it and see how it goes. i'll report back here : ) |
@egoist final question on this:
do you know if this is a known issue we can track in the Volar repo? I searched in the Volar repo but couldn't find anything on it. |
nope, maybe you can open a feature request
Luca Ban ***@***.***> 于 2021年12月17日周五 上午12:42写道:
… @egoist <https://github.com/egoist> final question on this:
It seems Volar won't pick up some-package/index.d.ts if you import
some-package/index.vue
do you know if this is a known issue we can track in the Volar repo? I
searched in the Volar repo but couldn't find anything on it.
—
Reply to this email directly, view it on GitHub
<#158 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACDAWSC5NH4MCRSZXUIW5RLURIJHHANCNFSM4PTCMGZA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@egoist After struggling with rollup for more than half a day, I ended up getting help from a friend to set up Vite.
|
brilliant, i think you can just use the vite vue plugin instead of the rollup plugin |
@egoist thanks!! I've replaced it and it works just as well! I also updated the post above. |
I'm in a never-ending quest to finding the best way to prepare a standalone vue component for publishing on NPM.
vue-compile
is great for Vue 2 components.Is there a roadmap with features you plan to create for Vue 3?
Especially when it comes to typing & auto completion in Vue 3. I wonder how components should be typed in the first place for optimal support in VSCode with eg. Vetur. And I'd love to know if this is on the roadmap for
vue-compile
or not : )The text was updated successfully, but these errors were encountered: