Mick Lawitzke
Mick Lawitzke
Amazing thanks!! May you release to npm? :)
@danielroe How can I have a custom fetch but with all the behavior as before? [The docs](https://nuxt.com/docs/guide/recipes/custom-usefetch) didnt say anything about the downsides of missing functionality when using custom fetch....
Can we have a simple way to recreate the Nuxt behavior? Personally I "just" want to set the base url for `$fetch`, `useFetch` and `useLazyFetch` but it ends up being...
@Aareksio Your code is working, thanks. But I do have TypeScript errors:
Duplicate of #3378, please close
I just came back here 9 months later, having the exact same issue. Now I have way more number and date formats and languages so the duplicate code is enormous....
I always try to avoid using route names because they are hard to find and sometimes I just cant find the right one at all
I use custom route paths per language, e.g. `/products` becomes `/produkte` in German. Now I want to link to `/products/123` and the dev tools show me as the name `products-id___de`...
I think I got it: ``` localePath({ name: 'products-id', params: { id: props.id } }) ```
Sounds amazing, I will check soon!!