@nuxtjs/ionic Module Affecting HTTP Status Codes

🐛 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:

1. Be explicitly designed for client-side-only (SPA) applications to avoid breaking SSR behavior.
2. Provide clear documentation or a configuration option to disable server-side interference.

🛠️ To reproduce

.

🌈 Expected behaviour

Steps to Reproduce:

1. Install @nuxtjs/ionic in a Nuxt 3 SSR project.
2. Attempt to return a 404 response or any other status code from a Nuxt route.
3. 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

No files or tests are named. Start by reproducing the issue in a Nuxt 3 SSR project with @nuxtjs/ionic and inspect how the module affects HTTP status handling. Done means 404 and other non-200 responses are preserved, with regression coverage added if the project provides a suitable test location.