Vuepress: Unknown custom element: <v-xxxxxxx>

[zhixinpeng]

• [x] I confirm that this is an issue rather than a question.

Bug report

Steps to reproduce

.vuepress/theme/Layout.vue

<template>
  <div>
    <router-link to="/a">to a</router-link>
    <router-link to="/b">to b</router-link>
    <Content></Content>
  </div>
</template>

./a.md

# a

./b.md

# a

What is expected?

correct render

What is actually happening?

The first page I went to can render correctly, when I click link,The following error occurred

Other relevant information

• vuepress version: 1.2.0
• node version: 12.7.0

[vvni]

这个问题我也遇到了，看到之前修复过这个问题，但是为什么v1.2.0还有这个问题呢？

[Mister-Hope]

I met this too, it seems that commit 2a5980 had solved this issue. Maybe we can figure out.

[ozguruysal]

I've been having this issue and here are the steps to reproduce it in Chrome.

Tested with

VuePress 1.2.0
Vue.js devtools 5.3.3

Reproduction Steps

1. Run the project in dev mode.
2. Open it in browser in a fresh tab.
3. Open Chrome dev tools but only go to Console tab.
4. Navigate between routes /route-a and route- b. Everything works well, no errors.
5. Open Vue tab in Chrome dev tools to activate Vue.js devtools then go back to Console tab.
6. Now navigate to /route-c (i.e. any route you haven't yet visited) and you get the error.

Hope this helps anyone out there familiar with the codebase to identify the problem.

[Mister-Hope]

I've been having this issue and here are the steps to reproduce it in Chrome.

Tested with

VuePress 1.2.0
Vue.js devtools 5.3.3

Reproduction Steps

1. Run the project in dev mode.
2. Open it in browser in a fresh tab.
3. Open Chrome dev tools but only go to Console tab.
4. Navigate between routes /route-a and route- b. Everything works well, no errors.
5. Open Vue tab in Chrome dev tools to activate Vue.js devtools then go back to Console tab.
6. Now navigate to /route-c (i.e. any route you haven't yet visited) and you get the error.

Hope this helps anyone out there familiar with the codebase to identify the problem.

I am able to reproduce it, not surprice to find the official are keeping silence as they allways did.

[acmoles]

I have also have this problem.

I don't experience the problem without following the Chrome repro steps, so, perhaps the issue relates to Vue devtools? Or the interaction between Vuepress and devtools?

[meteorlxy]

@acmoles vue-devtools has some problems with dynamic components https://github.com/vuejs/vue-devtools/issues/943 . Not sure if it's fixed

[meteorlxy]

I cannot reproduce this issue without opening vue-devtools.

So this is an issue that comes from vue-devtools: https://github.com/vuejs/vue-devtools/issues/944

[meteorlxy]

Closing this as this has been filed in https://github.com/vuejs/vue-devtools/issues/944.

Anyone else who encounter this problem, please check if it's related to your vue-devtools first.

[fsworld009]

Get the same issue when trying to inheritance the default theme. This workaround works for me https://github.com/vuejs/vuepress/issues/1173#issuecomment-470534176