bug: regression on nuxt@3.13.2 breaking the entire module

[tobychidi]

The requested module '/nuxt/@fs/C:/Users/tobychidi/Documents/GitHub/kaycee/Rotabliss/node_modules/.pnpm/@vue-leaflet+vue-leaflet@0.10.1@types+leaflet@1.9.12_leaflet@1.9.4_typescript@5.6.2/node_modules/@vue-leaflet/vue-leaflet/dist/vue-leaflet.cjs.js?v=6cbe18fd' does not provide an export named 'LTileLayer'

[Gugustinette]

Ooh that's weird, can you provide a reproduction ?

[urbgimtam]

Suffering the same after updating to nuxt@3.13.2.

Reproduction

[urbgimtam]

Forcing nuxt@3.13.1 does not trigger error. Only 3.13.2

[cesxhin]

same problem, after updating to nuxt@3.13.2

[Gugustinette]

After further investigations, I think this is more or less due to this fix from nuxt@3.13.2.

But I'm really not sure what should be changed on the module side, this is how components from vue-leaflet are imported :

for (const component of components) {
  addComponent({
    name: component,
    export: component,
    filePath: '@vue-leaflet/vue-leaflet',
    chunkName: `nuxt-leaflet/${component}`,
    mode: 'all',
  })
}

@danielroe any suggestion on this ?

You can develop on the module playground directly here : https://stackblitz.com/~/github.com/nuxt-modules/leaflet and try to navigate to /map/map path, which displays the following error :

[danielroe]

yes, this is a nuxt bug.

[Gugustinette]

Re-opening until the fix is released, for now stick with nuxt@3.13.1

[ipanamski]

Is the fix going to be included in the next release or the current one 3.13.2?

[Gugustinette]

@ipanamski You'll have to wait for a new release, I'll update this issue when it is available 👍

[urbgimtam]

It may be interesting to remind that it can be mitigated by wrapping <NuxtErrorBoundary> around your component which holds <LMap>, and even pass alternative content with <template #error={error}></template>.

Never used NuxtErrorBoundary much, but its really interesting as it can save the page from breaking in these kind of scenarios. Lovely stuff!