Daniel Roe

Good catch. In this repo it's just ^3.0.0.

Would you try setting nitro.autoImport.exclude? https://github.com/nuxt/framework/pull/5981

I think it would be possible to create something that auto imports components at test level. Otherwise `@nuxt/components` only is usable at pages/layouts level (typically tested via e2e rather than...

**Repro**: https://codesandbox.io/s/staging-pond-9qt1g

For now, manually adding `defu` to your `package.json` is the right way to solve this.

I think this is likely the same issue that is being solved in https://github.com/antfu/unplugin-vue2-script-setup/pull/124. cc: @antfu

**Reproduction**: https://stackblitz.com/edit/github-nubkan. Note that this is likely not a bug in Nuxt Bridge.

Would you confirm whether this is still happening, and provide a reproduction if so? 🙏

I'm closing this as there is no reproduction. Feel free to comment with one and I'll reopen!

If you're encountering this on Bridge, you can try this workaround: ```js import { defineNuxtConfig } from '@nuxt/bridge' export default defineNuxtConfig({ alias: { tslib: 'tslib/tslib.es6.js' } }) ```` The issue...