Replies: 3 comments
-
Currently VanUI only supports NPM. I can consider supporting other forms. But there are caveats:
For those reasons, I feel that in the context of VanUI, NPM is a much better solution compared to other alternatives. That said, I will keep your request in mind while deciding whether to publish VanUI in other forms in the future. |
Beta Was this translation helpful? Give feedback.
-
Since it's not hard to support using VanUI via a Let me know how it works for your use cases :-) |
Beta Was this translation helpful? Give feedback.
-
Awesome! Thanks for your quick reply and update. Will test it out in the
next few days and let you know!
…On Thu, Sep 28, 2023 at 11:11 Tao Xin ***@***.***> wrote:
Since it's not hard to support using VanUI via a <script> tag, I just
added the support. You can refer to
https://github.com/vanjs-org/van/tree/main/components#via-a-script-tag
for details.
Let me know how it works for your use cases :-)
—
Reply to this email directly, view it on GitHub
<#129 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGBQBFL6D75WEX5CR666BQDX4WVVRANCNFSM6AAAAAA5KLWZ7A>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
I'm just getting started with VanJS, and so far I love the minimal reactive API, what drew me to VanJS is that it can be used without a build step or any additional dependencies. I think it would be great if the VanUI components could be used like that. I tried downloading this file and including it via html <script> tag but it produced the following error:
SyntaxError: Unexpected identifier 'van'. import call expects one or two arguments.
Is there any possibility of creating a release of VanUI that could be included via script tag? I'm pretty knowledgable on JS but not sure what would be involved in compiling this down to vanilla js.
Beta Was this translation helpful? Give feedback.
All reactions