Daniel Roe comments

Results 2592 comments of


                                            Daniel Roe

Dynamic routes on Azure Static Web Apps have stopped functioning since Nuxt 3.5.0 or later.

Here is one: https://github.com/danielroe/page-speed.dev

Dynamic routes on Azure Static Web Apps have stopped functioning since Nuxt 3.5.0 or later.

Great! Is there something we can add to the docs to help in this situation?

refactor(nuxt): use AST-aware function key injection

would you take a look at the failing webpack/rspack tests? 🙏 I think it's fine to make `source` required going forward (e.g. in types), but we should fall back to...

feat(nuxt,schema): add directives folder

@userquin what do we need to do here, now that your other two prs have made it in, enabling directives within unimport?

`tsconfig.app.json` checks types in server endpoints

this is unfortunately required for type inference for `$fetch('/some/api/route')`. I would love a solution but I don't think there is one. 🤔

SWR (and ISR) not working locally

In order for `swr` to work, you should not prerender them. Prerendering the pages entirely bypasses dynamic caching rules.

Old clients could get new _payload.json files after each deployment

this might be related to skew protection (https://github.com/nitrojs/nitro/issues/2311, https://github.com/nitrojs/nitro/issues/3756) and it might also be related to whether we ship a _Nuxt_ solution to all of these issues in general.

fix(nuxt): invalidate module cache on composable export type changes

this may also be an approach which also works for some linked issues: - https://github.com/nuxt/nuxt/pull/32044 - https://github.com/nuxt/nuxt/pull/32182 - https://github.com/nuxt/nuxt/pull/31574

wrong package exports

@benjamincanac you can already adopt them before the module builder upgrade, if you want

wrong package exports

It's more correct. If it's well set up, it means the types users can see in their projects is consistent across node10/node16 module resolutions modes + ESM/CJS. You can see...