Stefan Krüger

I'll get to it soon :)

Hi @roberttco, the error you are receiving has no imminent connection to the harmony extension. If you update npm the problem quite possibly goes away. Under the link is an...

The breaking change was noted in the release notes, unfortunately it couldn't be avoided in the new design. On sending the command twice: there was a bug previous to version...

Is there any update on this? I'm getting a very similar error in my tests, and the workaround above does not seem feasible to be included in a simple test.

It worked before we changed to future, but as your repro shows, it doesn't seem to be the root cause. We noticed NuxtLink is not working as expected, as activeClass...

We found out why it worked before, it had nothing to do with versions. We had an additional `page1.vue` in pages, which rendered the `index.vue` as `NuxtPage`, something like this:...

Is there any update on this? It's still in triage, I think this should be confirmed as a bug?

This issue is now lingering for a very long time, with many issue since 2023 related to this. Is there a reason this can't be fixed? Seems like a straightforward...

Confirming the issue. I think it's caused by [this line ](https://github.com/nuxt/ui/commit/6e27304d8ca459a04667bac404084264a8cf58fd#diff-b7fa789489c8c59a3f5b6fe1ae3dc8b57ba36a45fb99f9db8f4b598aa377a5cdR204) from the reactivity update. https://github.com/nuxt/ui/commit/6e27304d8ca459a04667bac404084264a8cf58fd#diff-b7fa789489c8c59a3f5b6fe1ae3dc8b57ba36a45fb99f9db8f4b598aa377a5cdR204

The reason for the 404 error often is a mismatch of driver version, not necessarily due the URL. Please see #170. If the issue occurs on RHEL distros, I've created...