Daniel Roe

The issue here is that you should not import `useRoute` from `vue-router` but from `#imports`. We have a custom implementation of `useRoute` that handles some suspense related issues (https://github.com/nuxt/framework/pull/6275). The...

You can workaround this issue for now by ensuring you have only one version of `node-fetch-native` in your package lockfile. (The issue is a regression in nitro's traced externals which...

Here's a minimal reproduction: https://stackblitz.com/edit/github-1nqt6s.

Yes; you can run `npm i node-fetch-native`.

The issue is multiple versions installed rather than a specific version number; check your lockfile to see what they are and _why_. You may also be able to resolve with...

Reopening until we resolve in nitropack - you can follow https://github.com/unjs/nitro/pull/529.

related: https://github.com/nuxt/framework/issues/3015. Also see https://github.com/nuxt-community/router-module (which will need to be migrated to support nuxt 3).

We now have the ability to customise _all_ the options to `createRouter` via https://github.com/nuxt/framework/pull/3485 and https://github.com/nuxt/framework/pull/7129. Allowing an entirely separate router to be provided is not a good idea, I...

We are testing for dev here: https://github.com/nuxt/framework/blob/5605f1ce18d152122d966ac37c35c4c434b16184/packages/nuxt/src/core/nuxt.ts#L95 I think HMR for dev, but no scripts for built site seems a better default, but happy to be convinced otherwise.

To describe the issue, styles for the first page are being inlined. This includes global styles. They are in the right order, so global styles precede the page-specific CSS. But...