Toby Chidi

same issue

Will this fix the Typescript issues? ``` Type 'Plugin' is not assignable to type 'PluginOption'. Type 'Plugin' is not assignable to type 'Plugin_2'. ```

Yes ooo. I have this same issue nuxt/framework#7196

> I have the same issue, none of my images work with nuxt-img, here is example `` it returns 404 for dev and in production. Same here

I tried Vue slicksort. But the repo has now been dormant since February. Its a neat Lib though: Vue Slicksort

I have also noticed in my codebase where ` {method: "POST"} ` and ` {method: "post"} ` return different types for data in `useFetch` with the former being a union...

Just tried our the NuxtErrorBoundary component and it didn't work 🥲. ``` ``` When I use the NuxtErrorBoundary component my m-error component does not work well at all. The contents...

Also when I encounter an error and the error boundary is shown, a page refresh would cause a blank page. 

> I think netlify seperates the built server folder and the public folder which goes to a cdn. Therefor it does not have access to the public folder and can't...

Awesome. Thanks for this. The documentation would need some more work shaaa