The requested module '/_nuxt/composables/x.ts?t=1772618481096' does not provide an export named 'xx' (at xxx.ts)

[yk-eta]

Environment

| Node.js version | v22.14.0 |
| nuxt/cli version | 3.33.1 |
| Package manager | npm@10.9.2 |
| Nuxt version | 4.3.1 |
| Nitro version | 2.13.1 |
| Builder | vite@7.3.1 |
| Config | app, build, compatibilityDate, css, devServer, gtag, hooks, modules, routeRules, router, runtimeConfig, ssr, webpack |
| Modules | @pinia/nuxt@0.11.3, @nuxtjs/device@3.2.4, nuxt-gtag@4.1.0, nuxt-swiper@2.0.1, @nuxt/ui@4.5.1 |

Reproduction

// models/test.ts
export default class Test {
  // variable named same with composables exported function variable name
  xx
}

// composables
composables/x.ts
export const something = (xx: any) => {
  //doSomething
}

// generated test.ts?t=1772618481096
import {xx} from "/_nuxt/composables/x.ts?t=1772618481096";
export default class Test {
  // variable named same with composables exported function variable name
  xx
}

Describe the bug

after update with npm
The requested module '/_nuxt/composables/x.ts?t=1772618481096' does not provide an export named 'xx' (at xxx.ts)
error is fired on local, when I check the source file, the x.ts?t=1772618481096 inserted a new import line that try to import undefined variable from composables with the same named variable in the model file default class

[yk-eta]

look like the auto import system tried to import from utils and composables on matched variable name not exported function, why?

[Gobler]

change from arrow function to standard function - something recently went wrong with auto imports: unjs/unimport#502

const myFn = () => {} // ❌

function myFn () {} // ✅

[danielroe]

might be resolved by unjs/mlly#336.

[danielroe]

this is hotfixed in unjs/mlly#336 and will be properly fixed in unjs/mlly#339

[kbro-84]

@danielroe, will this fix be applied in the next upcoming release (one after v4.3.1)?

[danielroe]

it doesn't need to be. just update your lockfile.

[kbro-84]

@danielroe Thank you, sounds like the issue I had previously linked is not fully related then or has it's own issue as well because it still persisted after updating and fully re-installing deps.