Vue-material: md-list-item vue router BUG

Created on 7 Jan 2019  路  9Comments  路  Source: vuematerial/vue-material


While Trying to use the "to=" option in vue-material I have the following error :
TypeError: "context.$options.components['router-link'] is undefined"

Steps to reproduce


Home

Which browser?

Firefox and Chrome latest version to date

What is expected?

A link

What is actually happening?

TypeError: "context.$options.components['router-link'] is undefined"

Reproduction Link


duplicated

Most helpful comment

This will be my first time I could ever help someone out.. (finally!)

This issue occurs because of the current vue-router version 3.0.2, reverting back to 3.0.1 (for now) is a quick solution to this problem.

I found multiple references to this issue in other projects. I hope it helps!

All 9 comments

I'm also getting the exact same error in md-button.

This will be my first time I could ever help someone out.. (finally!)

This issue occurs because of the current vue-router version 3.0.2, reverting back to 3.0.1 (for now) is a quick solution to this problem.

I found multiple references to this issue in other projects. I hope it helps!

I can confirm that bug is gone if vue-router is reverted to 3.0.1.

Thank you so much @RoelZ

Okay, working for me too, but the weird thing is in my package.json I had "vue-router": "^3.0.1", and the bug. I guess it's link to another bug in Vue UI where the added dependencies aren't written to package.json.

This will be my first time I could ever help someone out.. (finally!)

This issue occurs because of the current vue-router version 3.0.2, reverting back to 3.0.1 (for now) is a quick solution to this problem.

I found multiple references to this issue in other projects. I hope it helps!

Worked and I'm closing the issue.

@Nolaan Check: https://michaelsoolee.com/npm-package-tilde-caret/
having a ^3.0.1 means at least that version but minor an patch can be newer (the last two numbers)

About the issue I'm not sure if it should be closed. Is this a bug from vue-router or is it new behaviour that vuematerial should accomodate?
If I can find the time I'll try to investigate further. @RoelZ do you still have any link to the issues on the other projects. maybe it can help figure this out.

@fimdomeio you're right I'm reopening it for investigation.

Duplicate of #1977

My solution: You can use the @click event to jump the route instead of to

Was this page helpful?
0 / 5 - 0 ratings