Mixing
Boilerplate Vue Project Fails on router-link and router-view
I used vue create to create a new view project with Babel, TypeScript, Router and Unit Testing. I then installed axios using npm.
Having done no other changes, I served the application by navigating to the src directory and running vue serve.
The resulting boilerplate application fails to load with the following error:
[Vue warn]: Unknown custom element: - did you register
the component correctly? For recursive components, make sure to
provide the "name" option.
found in
---> at App.vue
My own research shows that this error usually happens when you fail to call Vue.Use(). However, my router.ts file does so:
import Vue from 'vue';
import Router from 'vue-router';
import Home from './views/Home.vue';
Vue.use(Router);
export default new Router({ routes: [
{
path: '/',
name: 'home',
component: Home,
},
{
path: '/about',
name: 'about',
// route level code-splitting
// this generates a separate chunk (about.[hash].js) for this route
// which is lazy-loaded when the route is visited.
component: () => import(/* webpackChunkName: "about" */ './views/About.vue'),
}, ], });
Does anyone know what is wrong here? Given I haven't changed anything, could it be a config issue?
vue.js
asked Jan 2 at 2:21
Avi ChapmanAvi Chapman
957
add a comment |
I used vue create to create a new view project with Babel, TypeScript, Router and Unit Testing. I then installed axios using npm.
Having done no other changes, I served the application by navigating to the src directory and running vue serve.
The resulting boilerplate application fails to load with the following error:
[Vue warn]: Unknown custom element: - did you register
the component correctly? For recursive components, make sure to
provide the "name" option.
found in
---> at App.vue
My own research shows that this error usually happens when you fail to call Vue.Use(). However, my router.ts file does so:
import Vue from 'vue';
import Router from 'vue-router';
import Home from './views/Home.vue';
Vue.use(Router);
export default new Router({ routes: [
{
path: '/',
name: 'home',
component: Home,
},
{
path: '/about',
name: 'about',
// route level code-splitting
// this generates a separate chunk (about.[hash].js) for this route
// which is lazy-loaded when the route is visited.
component: () => import(/* webpackChunkName: "about" */ './views/About.vue'),
}, ], });
Does anyone know what is wrong here? Given I haven't changed anything, could it be a config issue?
vue.js
asked Jan 2 at 2:21
Avi ChapmanAvi Chapman
957
add a comment |
I used vue create to create a new view project with Babel, TypeScript, Router and Unit Testing. I then installed axios using npm.
Having done no other changes, I served the application by navigating to the src directory and running vue serve.
The resulting boilerplate application fails to load with the following error:
[Vue warn]: Unknown custom element: - did you register
the component correctly? For recursive components, make sure to
provide the "name" option.
found in
---> at App.vue
My own research shows that this error usually happens when you fail to call Vue.Use(). However, my router.ts file does so:
import Vue from 'vue';
import Router from 'vue-router';
import Home from './views/Home.vue';
Vue.use(Router);
export default new Router({ routes: [
{
path: '/',
name: 'home',
component: Home,
},
{
path: '/about',
name: 'about',
// route level code-splitting
// this generates a separate chunk (about.[hash].js) for this route
// which is lazy-loaded when the route is visited.
component: () => import(/* webpackChunkName: "about" */ './views/About.vue'),
}, ], });
Does anyone know what is wrong here? Given I haven't changed anything, could it be a config issue?
vue.js
asked Jan 2 at 2:21
Avi ChapmanAvi Chapman
957
I used vue create to create a new view project with Babel, TypeScript, Router and Unit Testing. I then installed axios using npm.
Having done no other changes, I served the application by navigating to the src directory and running vue serve.
The resulting boilerplate application fails to load with the following error:
[Vue warn]: Unknown custom element: - did you register
the component correctly? For recursive components, make sure to
provide the "name" option.
found in
---> at App.vue
My own research shows that this error usually happens when you fail to call Vue.Use(). However, my router.ts file does so:
import Vue from 'vue';
import Router from 'vue-router';
import Home from './views/Home.vue';
Vue.use(Router);
export default new Router({ routes: [
{
path: '/',
name: 'home',
component: Home,
},
{
path: '/about',
name: 'about',
// route level code-splitting
// this generates a separate chunk (about.[hash].js) for this route
// which is lazy-loaded when the route is visited.
component: () => import(/* webpackChunkName: "about" */ './views/About.vue'),
}, ], });
Does anyone know what is wrong here? Given I haven't changed anything, could it be a config issue?
vue.js
vue.js
asked Jan 2 at 2:21
Avi ChapmanAvi Chapman
957
asked Jan 2 at 2:21
Avi ChapmanAvi Chapman
957
asked Jan 2 at 2:21
Avi ChapmanAvi Chapman
957
asked Jan 2 at 2:21
Avi ChapmanAvi Chapman
957
asked Jan 2 at 2:21
Avi ChapmanAvi Chapman
957
957
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
I got it!
The issue was that I was running the server the wrong way. I was using:
vue serve src/App.vue
when I should have used:
npm run serve
After that change, it started to work.
answered Jan 2 at 7:47
Avi ChapmanAvi Chapman
957
Actually I did noticed that but thought you might have had a custom npm run command in your vue.config.js, updated my answer.
– Edgar Quintero
Jan 2 at 17:22
add a comment |
You don't need to navigate to the src folder, just navigate to the root directory of your application, then run npm run serve.
answered Jan 2 at 2:25
Edgar QuinteroEdgar Quintero
6251815
I tried that originally, but I got the following error: Failed to locate entry file in H:DataApacheDocRootSoftAccountssoft-accounts. Valid entry file should be one of: main.js, index.js, App.vue or app.vue.
– Avi Chapman
Jan 2 at 4:18
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54000527%2fboilerplate-vue-project-fails-on-router-link-and-router-view%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
I got it!
The issue was that I was running the server the wrong way. I was using:
vue serve src/App.vue
when I should have used:
npm run serve
After that change, it started to work.
answered Jan 2 at 7:47
Avi ChapmanAvi Chapman
957
Actually I did noticed that but thought you might have had a custom npm run command in your vue.config.js, updated my answer.
– Edgar Quintero
Jan 2 at 17:22
add a comment |
I got it!
The issue was that I was running the server the wrong way. I was using:
vue serve src/App.vue
when I should have used:
npm run serve
After that change, it started to work.
answered Jan 2 at 7:47
Avi ChapmanAvi Chapman
957
Actually I did noticed that but thought you might have had a custom npm run command in your vue.config.js, updated my answer.
– Edgar Quintero
Jan 2 at 17:22
add a comment |
I got it!
The issue was that I was running the server the wrong way. I was using:
vue serve src/App.vue
when I should have used:
npm run serve
After that change, it started to work.
answered Jan 2 at 7:47
Avi ChapmanAvi Chapman
957
I got it!
The issue was that I was running the server the wrong way. I was using:
vue serve src/App.vue
when I should have used:
npm run serve
After that change, it started to work.
answered Jan 2 at 7:47
Avi ChapmanAvi Chapman
957
answered Jan 2 at 7:47
Avi ChapmanAvi Chapman
957
answered Jan 2 at 7:47
Avi ChapmanAvi Chapman
957
answered Jan 2 at 7:47
Avi ChapmanAvi Chapman
957
957
Actually I did noticed that but thought you might have had a custom npm run command in your vue.config.js, updated my answer.
– Edgar Quintero
Jan 2 at 17:22
add a comment |
Actually I did noticed that but thought you might have had a custom npm run command in your vue.config.js, updated my answer.
– Edgar Quintero
Jan 2 at 17:22
Actually I did noticed that but thought you might have had a custom npm run command in your vue.config.js, updated my answer.
– Edgar Quintero
Jan 2 at 17:22
Actually I did noticed that but thought you might have had a custom npm run command in your vue.config.js, updated my answer.
– Edgar Quintero
Jan 2 at 17:22
add a comment |
You don't need to navigate to the src folder, just navigate to the root directory of your application, then run npm run serve.
answered Jan 2 at 2:25
Edgar QuinteroEdgar Quintero
6251815
I tried that originally, but I got the following error: Failed to locate entry file in H:DataApacheDocRootSoftAccountssoft-accounts. Valid entry file should be one of: main.js, index.js, App.vue or app.vue.
– Avi Chapman
Jan 2 at 4:18
add a comment |
You don't need to navigate to the src folder, just navigate to the root directory of your application, then run npm run serve.
answered Jan 2 at 2:25
Edgar QuinteroEdgar Quintero
6251815
I tried that originally, but I got the following error: Failed to locate entry file in H:DataApacheDocRootSoftAccountssoft-accounts. Valid entry file should be one of: main.js, index.js, App.vue or app.vue.
– Avi Chapman
Jan 2 at 4:18
add a comment |
You don't need to navigate to the src folder, just navigate to the root directory of your application, then run npm run serve.
answered Jan 2 at 2:25
Edgar QuinteroEdgar Quintero
6251815
You don't need to navigate to the src folder, just navigate to the root directory of your application, then run npm run serve.
answered Jan 2 at 2:25
Edgar QuinteroEdgar Quintero
6251815
edited Jan 2 at 17:21
answered Jan 2 at 2:25
Edgar QuinteroEdgar Quintero
6251815
answered Jan 2 at 2:25
Edgar QuinteroEdgar Quintero
6251815
answered Jan 2 at 2:25
Edgar QuinteroEdgar Quintero
6251815
6251815
I tried that originally, but I got the following error: Failed to locate entry file in H:DataApacheDocRootSoftAccountssoft-accounts. Valid entry file should be one of: main.js, index.js, App.vue or app.vue.
– Avi Chapman
Jan 2 at 4:18
add a comment |
I tried that originally, but I got the following error: Failed to locate entry file in H:DataApacheDocRootSoftAccountssoft-accounts. Valid entry file should be one of: main.js, index.js, App.vue or app.vue.
– Avi Chapman
Jan 2 at 4:18
I tried that originally, but I got the following error: Failed to locate entry file in H:DataApacheDocRootSoftAccountssoft-accounts. Valid entry file should be one of: main.js, index.js, App.vue or app.vue.
– Avi Chapman
Jan 2 at 4:18
I tried that originally, but I got the following error: Failed to locate entry file in H:DataApacheDocRootSoftAccountssoft-accounts. Valid entry file should be one of: main.js, index.js, App.vue or app.vue.
– Avi Chapman
Jan 2 at 4:18
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54000527%2fboilerplate-vue-project-fails-on-router-link-and-router-view%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
