fix: expect 0 to be defined

[clarkdo]

Try to fix #2505, delegate params['pathMatch'] to params['0'] for pathToRegexp package matching.

[rchl]

This fix feels hacky but I think for all practical purposes, it should be fine.

Maybe I would create a copy of params instead of mutating it to eliminate need to remove property and make it a bit cleaner.

Also, I would add tests to test the bug and the fix - here is my modified create-matcher.spec.js with relevant tests added - https://gist.github.com/rchl/2418f5c40e66f9f27a34f89f83960b9a

Please prioritize this @posva as it's a breaking bug in specific setup (with nuxt-i18n) and in development ENV, it breaks nuxt-link/router-link (in production just cases warning in the client).

[posva]

I will come to it when I can :/
But it's supposed to just be a warning that shouldn't be displayed. Why would it break. And yes, a tes is required

[rchl]

Sorry, this is just a warning. I've confused this bug with nuxt-modules/i18n#73

[posva]

I'll merge this and add the test and comments locally, thanks!

[posva]

hmm, doesn't seem to be fixed yet. I need to debug further. It's now on a branch fix/2505 in case you want to take a look. I won't be able to until tomorrow