Skip to content
This repository has been archived by the owner on Apr 6, 2023. It is now read-only.

fix(nuxt3): render nuxt custom error page #4289

Merged
merged 14 commits into from
Apr 12, 2022
Merged

Conversation

danielroe
Copy link
Member

@danielroe danielroe commented Apr 12, 2022

πŸ”— Linked issue

resolves nuxt/nuxt#13699

❓ Type of change

  • πŸ“– Documentation (updates to the documentation or readme)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • πŸ‘Œ Enhancement (improving an existing functionality like performance)
  • ✨ New feature (a non-breaking change that adds functionality)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

πŸ“š Description

Follow up on nuxt/nuxt#13699.

πŸ“ Checklist

  • I have linked an issue or discussion.
  • I have updated the documentation accordingly.

@danielroe danielroe added bug Something isn't working nitro nuxt3 ❗ p4-important Priority 4: bugs that violate documented behavior, or significantly impact perf labels Apr 12, 2022
@danielroe danielroe requested a review from pi0 April 12, 2022 11:41
@danielroe danielroe self-assigned this Apr 12, 2022
@netlify
Copy link

netlify bot commented Apr 12, 2022

βœ… Deploy Preview for nuxt3-docs canceled.

Name Link
πŸ”¨ Latest commit 4372e59
πŸ” Latest deploy log https://app.netlify.com/sites/nuxt3-docs/deploys/6255ddb3b7d36f00084dbc45

@danielroe
Copy link
Member Author

danielroe commented Apr 12, 2022

@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?

@pi0
Copy link
Member

pi0 commented Apr 12, 2022

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)

@danielroe
Copy link
Member Author

danielroe commented Apr 12, 2022

Note: we should add a breaking change indicator for bridge and require people to add the new version of defu to their package.json (as we now require this in nitropack 0.2.4) - or we need to revert this in nitropack.

@@ -7,6 +7,7 @@
},
"devDependencies": {
"@nuxt/bridge": "*",
"defu": "^6.0.0",
Copy link
Member Author

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.

@pi0
Copy link
Member

pi0 commented Apr 12, 2022

Note: we should add a breaking change indicator for bridge and require people to add the new version of defu to their package.json (as we now require this in nitropack 0.2.4) - or we need to revert this in nitropack.

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.

packages/bridge/src/app.ts Outdated Show resolved Hide resolved
@pi0 pi0 merged commit e43ba6e into main Apr 12, 2022
@pi0 pi0 deleted the fix/override-nitro-error-page branch April 12, 2022 20:37
@danielroe danielroe added the 3.x label Jan 19, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
3.x bug Something isn't working nitro nuxt3 ❗ p4-important Priority 4: bugs that violate documented behavior, or significantly impact perf
Projects
None yet
Development

Successfully merging this pull request may close these issues.

error page can't custom render, error page rendered by nitropack
2 participants