You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The @nuxtjs/ionic module is preventing my Nuxt server from correctly sending HTTP status codes, effectively making server-side rendering (SSR) useless. This impacts critical functionality such as proper 404 error pages and other HTTP responses, which are essential for a Nuxt-based application.
Expected Behavior:
The module should either:
Be explicitly designed for client-side-only (SPA) applications to avoid breaking SSR behavior.
Provide clear documentation or a configuration option to disable server-side interference.
🛠️ To reproduce
.
🌈 Expected behaviour
Steps to Reproduce:
Install @nuxtjs/ionic in a Nuxt 3 SSR project.
Attempt to return a 404 response or any other status code from a Nuxt route.
Observe that the expected status codes do not work correctly.
This effectively negates the benefits of using Nuxt over Vue 3 for SSR applications. I would appreciate it if the module were restricted to client-side use only or had a proper fix to ensure SSR compatibility.
Thanks for your time!
ℹ️ Additional context
No response
The text was updated successfully, but these errors were encountered:
🐛 The bug
The
@nuxtjs/ionic
module is preventing my Nuxt server from correctly sending HTTP status codes, effectively making server-side rendering (SSR) useless. This impacts critical functionality such as proper 404 error pages and other HTTP responses, which are essential for a Nuxt-based application.Expected Behavior:
The module should either:
🛠️ To reproduce
.
🌈 Expected behaviour
Steps to Reproduce:
This effectively negates the benefits of using Nuxt over Vue 3 for SSR applications. I would appreciate it if the module were restricted to client-side use only or had a proper fix to ensure SSR compatibility.
Thanks for your time!
ℹ️ Additional context
No response
The text was updated successfully, but these errors were encountered: