Daniel Roe
Daniel Roe
@Smef I don't think that is related to this issue, exactly. Would you create a new issue with a reproduction and I'll look at it? :pray:
I suspect the `route.fullPath` might have a trailing slash in your deployed environment which is causing this mismatch. Try instead using `route.params.slug`.
Well, the trailing slash is not an issue unless you are using the url as a key. You can make it any unique key; it doesn't have to be url-like...
@richhiggins For what you need, [this](https://github.com/nuxt/framework/issues/4919#issuecomment-1124349857) is the solution, for now at least.
The never ending test run on Windows is an issue we are also seeing on bridge: https://github.com/nuxt/bridge/pull/489
This seems like it might be a vite error. Would you test with https://stackblitz.com/github/nuxt-contrib/vue3-ssr-starter/tree/main?
Thanks for checking.
I can't reproduce; would you try again with `npx nuxi@latest` in case you have an outdated version of nuxi in your npm cache?
@J4MSH1D Are you using an http proxy on your system?
The key thing is that you should not destructure `params` from the returned route object that Nuxt (or vue-router) provides, as it is a reactive object and destructuring anything from...