-
Notifications
You must be signed in to change notification settings - Fork 100
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
feat: experimental vite support #387
Conversation
* move remaining bastions to `upath` * use `options.alias` rather than extending webpack build
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/nuxt-community/composition-api/72grcPvrdmjMhRnYjmigCQQnWfoJ |
* allow multiple installations of VCA in dev mode (for vite)
src/module.ts
Outdated
}) | ||
|
||
// Fake alias to prevent shadowing actual node_module | ||
const aliases = ['@nuxtjs/composition-api', '@nuxtjs/vite-composition-api'] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think in case of using a sub-path this should not happen (we use nuxt3/build
for example and is working fine)
Note: the final issue with |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work on vite plugin 👍
You can try this PR by installing
@nuxtjs/composition-api@vite
and following the steps below.To use
@nuxtjs/composition-api
withnuxt-vite
you must:@vue/composition-api
as a top level devDependency of your project rather than relying on the version provided by@nuxtjs/composition-api
.will close nuxt/vite#17