Daniel Roe comments

Results 2595 comments of


                                            Daniel Roe

Potential Memory Leak

I refreshed your lockfile + updated to Node v22 and could not reproduce. ![CleanShot 2024-08-28 at 14 37 29@2x](https://github.com/user-attachments/assets/fd5e34ca-e7bd-4441-ba38-e52aa6c7df42) Between each snapshot I ran: ```bash ab -n 1000 -c 50...

Potential Memory Leak

delighted to hear it! 🔥

fix(nuxt): change the name of the RouteProvider componet when keepalive

Try running: ```bash pnpm playwright-core install chromium ```

fix(nuxt): change the name of the RouteProvider componet when keepalive

I'd have a better idea of how to fix if you could provide a reproduction of the issue.

fix(nuxt): change the name of the RouteProvider componet when keepalive

this was implemented in https://github.com/nuxt/nuxt/pull/30807 and will be included in Nuxt v3.16

Composables with explicit import are not keyed

I think you just need to provide `source`: https://stackblitz.com/edit/nuxt-starter-tdftk6. So, two possible improvements: 1. mark `source` required. 2. handle resolving aliases, so `~/composables/test` works as well.

Factory function to create `useFetch` and `useAsyncData` with defaults

@adrienZ That would be great!

Factory function to create `useFetch` and `useAsyncData` with defaults

You can use `$fetch.create` to create a custom preconfigured fetch instance for your needs.

Factory function to create `useFetch` and `useAsyncData` with defaults

useAsyncData is a composable (= declarative), and if you are using it imperatively and expect it to throw then that's an indication you should probably be using using something else,...

Factory function to create `useFetch` and `useAsyncData` with defaults

@cernymatej you'd be welcome to pick - checked with @pi0 to ensure he didn't have a WIP! ❤️