fix(vue): scope Nuxt runtime auto-import exports to composables#5009
fix(vue): scope Nuxt runtime auto-import exports to composables#5009theamodhshetty wants to merge 2 commits intowevm:mainfrom
Conversation
🦋 Changeset detectedLatest commit: 1b745ae The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
@theamodhshetty is attempting to deploy a commit to the Wevm Team on Vercel. A member of the Team first needs to authorize it. |
|
Small implementation note: I kept the deprecated aliases ( |
|
Quick follow-up update:
The remaining failing checks are both Vercel authorization gates for the Wevm team, so they should pass once team authorization is granted. |
Summary
Fixes Nuxt auto-import failures in
@wagmi/vueby narrowing the Nuxt runtime composables entrypoint to composable exports only.Problem
packages/vue/src/nuxt/runtime/composables.tsre-exported../../exports/index.js, which also includes plugin/core utility exports. In Nuxt auto-import paths, this can pull in module interop that triggers:eventemitter3 ... does not provide an export named 'default'.Changes
useAccount,useAccountEffect,useSwitchAccount) via explicit alias exports.Tests
pnpm vitest run packages/vue/src/nuxt/runtime/composables.test.ts packages/vue/src/exports/nuxt.test.tspnpm biome check packages/vue/src/nuxt/runtime/composables.ts packages/vue/src/nuxt/runtime/composables.test.tsCloses #3977.