Closed tobychidi closed 1 week ago
Ooh that's weird, can you provide a reproduction ?
Suffering the same after updating to nuxt@3.13.2.
Forcing nuxt@3.13.1 does not trigger error. Only 3.13.2
same problem, after updating to nuxt@3.13.2
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 :
yes, this is a nuxt bug.
Re-opening until the fix is released, for now stick with nuxt@3.13.1
Is the fix going to be included in the next release or the current one 3.13.2?
@ipanamski You'll have to wait for a new release, I'll update this issue when it is available π
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!
Looks like this will be fixed on v3.14.0
: https://github.com/nuxt/nuxt/pull/29077
As far as I tested, this seems resolved with Nuxt Leaflet 1.2.4.
@tobychidi can you confirm ?
Not op but I can confirm, works with 3.14 on my end ππΌ
The issue has been resolved. Thank you @Gugustinette
Cool ! Thanks a lot everyone π
The requested module '/_nuxt/@fs/C:/Users/tobychidi/Documents/GitHub/kaycee/Rotabliss/nodemodules/.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'