v3.4.3

[danielroe]

3.4.3 is a patch release with the latest bug fixes. 🐞 It is expected that the next release will be v3.5, in approximately two weeks' time.

✅ Upgrading

As usual, our recommendation for upgrading is to run:

nuxi upgrade --force

This will refresh your lockfile as well, and ensures that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.

👉 Changelog

compare changes

🩹 Fixes

• nuxt: Don't call timeEnd unless we're debugging (#20424)
• nuxt: Use key to force server component re-rendering (#19911)
• nuxt: Add basic typings for <ClientOnly> (f1ded44e8)
• nuxt: Use event.node.req in cookie utility (#20474)
• deps: Relax upper node version constraint (#20472)
• nuxi,schema: Support devServer.https: true (#20498)
• nuxt: Throw 404 when accessing /__nuxt_error directly (#20497)
• nuxt: Use callAsync for executing hooks with context (#20510)
• nuxt: Improved typing support for app config (#20526)
• nuxt: Call app:error in SSR before rendering error page (#20511)
• nuxt: Restrict access to single renderer outside of test/rootDir (#20543)
• nuxt: Throw errors when running legacy asyncData (#20535)
• nuxt: Transform #components imports into direct component imports (#20547)
• nuxt: Return RenderResponse for redirects (#20496)

📖 Documentation

• Fix typos on docs homepage (#20456)
• Update links to vue-router docs (#20454)
• Remove RC reference and add link to vue migration build (#20485)
• Add cdn proxy section (#20408)
• Add a next steps link to first page of migration docs (#20512)
• Add custom fetch composable example (#20115)
• Adjust wrong link after repo migration (#20536)

✅ Tests

• Exclude default error pages from bundle test (ba320a558)
• Update snapshot (ac598e4f4)

🤖 CI

• Publish edge release with provenance (ec1503731)
• Run release script with node 18 (0d10e9734)
• Try releasing nuxt-edge with provenance (753c4c2a3)
• Run nuxt2 nightly release on node 14 again (48c034cf0)

---

This discussion was created from the release v3.4.3.

[jd1378]

@danielroe This new code has broken the functionality over at nuxt-svgo
the reason is that nuxt-svgo has a custom vite plugin that uses the import url query to determine what to do with the svg file
this new code now appends ?component=async at the end of a url that already has ?componentext (there's other possible queries as well) , which breaks it by combining into (?componentext?component=async)

the fault is mine I guess ? because I relied on some implementation detail rather than API, but I couldn't find an API for adding query to import urls when using addComponentsDir

[jd1378]

I have released the fix at nuxt-svgo

[CastroM081297]

@danielroe This new code has broken the functionality over at nuxt-svgo
the reason is that nuxt-svgo has a custom vite plugin that uses the import url query to determine what to do with the svg file
this new code now appends ?component=async at the end of a url that already has ?componentext (there's other possible queries as well) , which breaks it by combining into (?componentext?component=async)

the fault is mine I guess ? because I relied on some implementation detail rather than API, but I couldn't find an API for adding query to import urls when using addComponentsDir

Ok

[antfu]

Fix is here: #20591

[oleghalin]

Even with @jd1378 fix i still cannot use ?component query in import

[jd1378]

@oleghalin create an issue on nuxt-svgo repo and provide some details, we'll track it there

maybe it's something with ?component query, because I can definitely use ?skipsvgo in import without any problem
overall we probably have to wait for nuxt's fix release to see how it goes