-
-
Notifications
You must be signed in to change notification settings - Fork 1k
fix(nuxt3): render nuxt custom error page #4289
Conversation
β Deploy Preview for nuxt3-docs canceled.
|
@pi0 Given we use new defu in nitropack, we may have to bump bridge defu as well, but IIRC we had some breaking issues last time. WDYT? |
Updating is fine as long as using default export instead of named one (until nuxt 2 also bumps defu. until then hosting can make issues) |
Note: we should add a breaking change indicator for bridge and require people to add the new version of |
test/fixtures/bridge/package.json
Outdated
@@ -7,6 +7,7 @@ | |||
}, | |||
"devDependencies": { | |||
"@nuxt/bridge": "*", | |||
"defu": "^6.0.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, that's right. v6 is already a direct dependency of @nuxt/bridge
, and adding this directly in user's project is likely the best way to ensure top-level defu is v6.
I'm not sure about default hosting behavior with published package. Let's try on edge and see if there is a better way to enforce bridge using latest defu. |
use new types and reveal error while generating error
π Linked issue
resolves nuxt/nuxt#13699
β Type of change
π Description
Follow up on nuxt/nuxt#13699.
π Checklist