Utilizing a component, from GitHub, in my Vue project. (I'm a complete beginner)
up vote
2
down vote
favorite
I am a 43 year-old student in a Web Development track and a first-time poster to Stack Overflow. I feel that my age may be relevant as I've surely picked up bad-habit along the way in how I understand other languages that I've been familiar with such as HTML, CSS, BASIC, very little JavaScript and PHP.
This semester, I began learning Vue. Our first "assignment" for the Vue phase was to follow along with, and complete, the instruction provided by a YouTube video from Traversy Media. This video was great to follow, evident that I was able to complete its objective with little difficulty. However, I don't feel that I quite understand the relevance of each file within a Vue project, such as index.js, index.html, *.vue.
I've found a few videos which create a component and then utilize that component. However, I feel completely lost when downloading a component, specifically: 'Vue-Accordion' from github to use as my navigation in conjunction with vue-router. The vue-accordion instructions simply state to add specific code, but doesn't say to which file I should add this code.
I've hacked at it by guessing/assuming a file that I figured relevant to the task, such as app.vue, index.js, and index.html... to no avail. Certainly, I think that a better understanding of a Vue Project's file-structure/hierarchy could give me a better feel in knowing exactly what files are relevant to any task-at-hand that I may have.
I appreciate your taking the time to read this post as well as your effort(s) in understanding my current dilemma. Thank you, in advance, for any and all input!
Very respectfully,
Dave
github vue.js components hierarchy file-structure
add a comment |
up vote
2
down vote
favorite
I am a 43 year-old student in a Web Development track and a first-time poster to Stack Overflow. I feel that my age may be relevant as I've surely picked up bad-habit along the way in how I understand other languages that I've been familiar with such as HTML, CSS, BASIC, very little JavaScript and PHP.
This semester, I began learning Vue. Our first "assignment" for the Vue phase was to follow along with, and complete, the instruction provided by a YouTube video from Traversy Media. This video was great to follow, evident that I was able to complete its objective with little difficulty. However, I don't feel that I quite understand the relevance of each file within a Vue project, such as index.js, index.html, *.vue.
I've found a few videos which create a component and then utilize that component. However, I feel completely lost when downloading a component, specifically: 'Vue-Accordion' from github to use as my navigation in conjunction with vue-router. The vue-accordion instructions simply state to add specific code, but doesn't say to which file I should add this code.
I've hacked at it by guessing/assuming a file that I figured relevant to the task, such as app.vue, index.js, and index.html... to no avail. Certainly, I think that a better understanding of a Vue Project's file-structure/hierarchy could give me a better feel in knowing exactly what files are relevant to any task-at-hand that I may have.
I appreciate your taking the time to read this post as well as your effort(s) in understanding my current dilemma. Thank you, in advance, for any and all input!
Very respectfully,
Dave
github vue.js components hierarchy file-structure
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I am a 43 year-old student in a Web Development track and a first-time poster to Stack Overflow. I feel that my age may be relevant as I've surely picked up bad-habit along the way in how I understand other languages that I've been familiar with such as HTML, CSS, BASIC, very little JavaScript and PHP.
This semester, I began learning Vue. Our first "assignment" for the Vue phase was to follow along with, and complete, the instruction provided by a YouTube video from Traversy Media. This video was great to follow, evident that I was able to complete its objective with little difficulty. However, I don't feel that I quite understand the relevance of each file within a Vue project, such as index.js, index.html, *.vue.
I've found a few videos which create a component and then utilize that component. However, I feel completely lost when downloading a component, specifically: 'Vue-Accordion' from github to use as my navigation in conjunction with vue-router. The vue-accordion instructions simply state to add specific code, but doesn't say to which file I should add this code.
I've hacked at it by guessing/assuming a file that I figured relevant to the task, such as app.vue, index.js, and index.html... to no avail. Certainly, I think that a better understanding of a Vue Project's file-structure/hierarchy could give me a better feel in knowing exactly what files are relevant to any task-at-hand that I may have.
I appreciate your taking the time to read this post as well as your effort(s) in understanding my current dilemma. Thank you, in advance, for any and all input!
Very respectfully,
Dave
github vue.js components hierarchy file-structure
I am a 43 year-old student in a Web Development track and a first-time poster to Stack Overflow. I feel that my age may be relevant as I've surely picked up bad-habit along the way in how I understand other languages that I've been familiar with such as HTML, CSS, BASIC, very little JavaScript and PHP.
This semester, I began learning Vue. Our first "assignment" for the Vue phase was to follow along with, and complete, the instruction provided by a YouTube video from Traversy Media. This video was great to follow, evident that I was able to complete its objective with little difficulty. However, I don't feel that I quite understand the relevance of each file within a Vue project, such as index.js, index.html, *.vue.
I've found a few videos which create a component and then utilize that component. However, I feel completely lost when downloading a component, specifically: 'Vue-Accordion' from github to use as my navigation in conjunction with vue-router. The vue-accordion instructions simply state to add specific code, but doesn't say to which file I should add this code.
I've hacked at it by guessing/assuming a file that I figured relevant to the task, such as app.vue, index.js, and index.html... to no avail. Certainly, I think that a better understanding of a Vue Project's file-structure/hierarchy could give me a better feel in knowing exactly what files are relevant to any task-at-hand that I may have.
I appreciate your taking the time to read this post as well as your effort(s) in understanding my current dilemma. Thank you, in advance, for any and all input!
Very respectfully,
Dave
github vue.js components hierarchy file-structure
github vue.js components hierarchy file-structure
asked Nov 14 at 1:48
David C.
132
132
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
2
down vote
accepted
Alright so schools in session (sorry if I explain too basic stuff at times, just trying to be thorough).
Here's the basic structure for a Vue project using vue init webpack-simple my-project
:
- src/
- assets/
- logo.png
- App.vue
- main.js
- assets/
- .babelrc
- .gitignore
- index.html
- package.json
- README.md
- webpack.config.js
The src
folder contains all the source files of your project.
The src/assets
folder contains all your assets, primarily images.
App.vue
is the first "view" of your app.
main.js
is the main script of your project where you configure and run Vue. This is where you load anything that should exist in the global scope of your app.
.babelrc
configures how the babel tool should syntax check your code.
.gitignore
tells Git to ignore certain files from committing.
index.html
is the page that's sent to the clients browser. This is where we load the main.js file and put any and all meta data you need (unless you use e.g. vue-meta to handle it there instead). Note that <div id="app">
html tag, this is where all your Vue files get mounted to.
package.json
is our npm configuration file. When you run e.g. npm install --save component-from-npm-name it's saved here so you can just run npm install later to get all the dependencies of your project.
README.md
is a documentation file in the Markdown language format. It's displayed as the frontpage of your project on e.g. Github or Gitlab.
webpack.config.js
is a Node.js file that is responsible for running Webpack on your project. Vue can be used without Webpack but I don't recommend it. You can run node webpack.config.js
directly to build your project. This file is your build script, you configured this to handle the build process of your project.
So, armed with this information, lets get to your question.
How do you load a component in Vue.js?
- Run
npm install --save vue-accordion
(note that while the source code is hosted on Github, the package is downloaded from here: https://www.npmjs.com/package/vue-accordion) - In your
index.js
file, which is responsible for loading things to your Vue app in the global context, you do as the Github page tells you and firstimport {vueAccordion} from 'vue-accordion'
, then runVue.component('vue-accordion', vueAccordion)
to register it in the global context.
That's all there is to it. index.js
is your entry point for your Vue app, while webpack.config.js
is your build script.
There is however an alternative solution to loading components. In the previous variant we loaded it in index.js
to load it in the global context, i.e. you can use the component now anywhere in your app, but what if you only want to load it on an as-is-needed basis (you'd wanna do this for performance reasons)?
Well, in your App.vue
file you have a <script>
tag where you can configure things in just that Vue component (all .vue files are Vue components, even if you call them routes, pages, views or whatever to indicated their purpose). In order to load a component not in the global context, but the component context, you'd do the following in App.vue
:
<script>
import Accordion from 'vue-accordion';
export default {
components: {
'vue-accordion': Accordion
}
</script>
Tips...
- This is just one setup for a Vue project. A Vue project can be as simple as just loading Vue as a script to your static index.html file, then you can have a much more annoying setup with regular javascript files, but that's dumb and inefficient. So, a proper project has a Node.js file to run Webpack. Depending on how you configure Webpack your project can act quite differently from any other Webpack project.
- Read up more on how Webpack works so you can have a project structure that makes sense for you.
- Take a look at Nuxt, it's essentially a collection of other projects (primarily Vue and Webpack) that simplifies the making of a powerful Vue project. You can sit and set up your own Vue project and all the tools yourself and get the same result, but Nuxt makes it simpler for you to do.
A very thorough and simple to understand answer for a beginner like the question starter.
– Ru Chern Chong
Nov 14 at 2:26
Your response is precisely what I needed to understand so that I know exactly what I'm hacking at, and why! That you so much for taking the time to provide such an elaborate answer!
– David C.
Nov 14 at 16:11
You're welcome :)
– Simon Hyll
Nov 15 at 1:57
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
Alright so schools in session (sorry if I explain too basic stuff at times, just trying to be thorough).
Here's the basic structure for a Vue project using vue init webpack-simple my-project
:
- src/
- assets/
- logo.png
- App.vue
- main.js
- assets/
- .babelrc
- .gitignore
- index.html
- package.json
- README.md
- webpack.config.js
The src
folder contains all the source files of your project.
The src/assets
folder contains all your assets, primarily images.
App.vue
is the first "view" of your app.
main.js
is the main script of your project where you configure and run Vue. This is where you load anything that should exist in the global scope of your app.
.babelrc
configures how the babel tool should syntax check your code.
.gitignore
tells Git to ignore certain files from committing.
index.html
is the page that's sent to the clients browser. This is where we load the main.js file and put any and all meta data you need (unless you use e.g. vue-meta to handle it there instead). Note that <div id="app">
html tag, this is where all your Vue files get mounted to.
package.json
is our npm configuration file. When you run e.g. npm install --save component-from-npm-name it's saved here so you can just run npm install later to get all the dependencies of your project.
README.md
is a documentation file in the Markdown language format. It's displayed as the frontpage of your project on e.g. Github or Gitlab.
webpack.config.js
is a Node.js file that is responsible for running Webpack on your project. Vue can be used without Webpack but I don't recommend it. You can run node webpack.config.js
directly to build your project. This file is your build script, you configured this to handle the build process of your project.
So, armed with this information, lets get to your question.
How do you load a component in Vue.js?
- Run
npm install --save vue-accordion
(note that while the source code is hosted on Github, the package is downloaded from here: https://www.npmjs.com/package/vue-accordion) - In your
index.js
file, which is responsible for loading things to your Vue app in the global context, you do as the Github page tells you and firstimport {vueAccordion} from 'vue-accordion'
, then runVue.component('vue-accordion', vueAccordion)
to register it in the global context.
That's all there is to it. index.js
is your entry point for your Vue app, while webpack.config.js
is your build script.
There is however an alternative solution to loading components. In the previous variant we loaded it in index.js
to load it in the global context, i.e. you can use the component now anywhere in your app, but what if you only want to load it on an as-is-needed basis (you'd wanna do this for performance reasons)?
Well, in your App.vue
file you have a <script>
tag where you can configure things in just that Vue component (all .vue files are Vue components, even if you call them routes, pages, views or whatever to indicated their purpose). In order to load a component not in the global context, but the component context, you'd do the following in App.vue
:
<script>
import Accordion from 'vue-accordion';
export default {
components: {
'vue-accordion': Accordion
}
</script>
Tips...
- This is just one setup for a Vue project. A Vue project can be as simple as just loading Vue as a script to your static index.html file, then you can have a much more annoying setup with regular javascript files, but that's dumb and inefficient. So, a proper project has a Node.js file to run Webpack. Depending on how you configure Webpack your project can act quite differently from any other Webpack project.
- Read up more on how Webpack works so you can have a project structure that makes sense for you.
- Take a look at Nuxt, it's essentially a collection of other projects (primarily Vue and Webpack) that simplifies the making of a powerful Vue project. You can sit and set up your own Vue project and all the tools yourself and get the same result, but Nuxt makes it simpler for you to do.
A very thorough and simple to understand answer for a beginner like the question starter.
– Ru Chern Chong
Nov 14 at 2:26
Your response is precisely what I needed to understand so that I know exactly what I'm hacking at, and why! That you so much for taking the time to provide such an elaborate answer!
– David C.
Nov 14 at 16:11
You're welcome :)
– Simon Hyll
Nov 15 at 1:57
add a comment |
up vote
2
down vote
accepted
Alright so schools in session (sorry if I explain too basic stuff at times, just trying to be thorough).
Here's the basic structure for a Vue project using vue init webpack-simple my-project
:
- src/
- assets/
- logo.png
- App.vue
- main.js
- assets/
- .babelrc
- .gitignore
- index.html
- package.json
- README.md
- webpack.config.js
The src
folder contains all the source files of your project.
The src/assets
folder contains all your assets, primarily images.
App.vue
is the first "view" of your app.
main.js
is the main script of your project where you configure and run Vue. This is where you load anything that should exist in the global scope of your app.
.babelrc
configures how the babel tool should syntax check your code.
.gitignore
tells Git to ignore certain files from committing.
index.html
is the page that's sent to the clients browser. This is where we load the main.js file and put any and all meta data you need (unless you use e.g. vue-meta to handle it there instead). Note that <div id="app">
html tag, this is where all your Vue files get mounted to.
package.json
is our npm configuration file. When you run e.g. npm install --save component-from-npm-name it's saved here so you can just run npm install later to get all the dependencies of your project.
README.md
is a documentation file in the Markdown language format. It's displayed as the frontpage of your project on e.g. Github or Gitlab.
webpack.config.js
is a Node.js file that is responsible for running Webpack on your project. Vue can be used without Webpack but I don't recommend it. You can run node webpack.config.js
directly to build your project. This file is your build script, you configured this to handle the build process of your project.
So, armed with this information, lets get to your question.
How do you load a component in Vue.js?
- Run
npm install --save vue-accordion
(note that while the source code is hosted on Github, the package is downloaded from here: https://www.npmjs.com/package/vue-accordion) - In your
index.js
file, which is responsible for loading things to your Vue app in the global context, you do as the Github page tells you and firstimport {vueAccordion} from 'vue-accordion'
, then runVue.component('vue-accordion', vueAccordion)
to register it in the global context.
That's all there is to it. index.js
is your entry point for your Vue app, while webpack.config.js
is your build script.
There is however an alternative solution to loading components. In the previous variant we loaded it in index.js
to load it in the global context, i.e. you can use the component now anywhere in your app, but what if you only want to load it on an as-is-needed basis (you'd wanna do this for performance reasons)?
Well, in your App.vue
file you have a <script>
tag where you can configure things in just that Vue component (all .vue files are Vue components, even if you call them routes, pages, views or whatever to indicated their purpose). In order to load a component not in the global context, but the component context, you'd do the following in App.vue
:
<script>
import Accordion from 'vue-accordion';
export default {
components: {
'vue-accordion': Accordion
}
</script>
Tips...
- This is just one setup for a Vue project. A Vue project can be as simple as just loading Vue as a script to your static index.html file, then you can have a much more annoying setup with regular javascript files, but that's dumb and inefficient. So, a proper project has a Node.js file to run Webpack. Depending on how you configure Webpack your project can act quite differently from any other Webpack project.
- Read up more on how Webpack works so you can have a project structure that makes sense for you.
- Take a look at Nuxt, it's essentially a collection of other projects (primarily Vue and Webpack) that simplifies the making of a powerful Vue project. You can sit and set up your own Vue project and all the tools yourself and get the same result, but Nuxt makes it simpler for you to do.
A very thorough and simple to understand answer for a beginner like the question starter.
– Ru Chern Chong
Nov 14 at 2:26
Your response is precisely what I needed to understand so that I know exactly what I'm hacking at, and why! That you so much for taking the time to provide such an elaborate answer!
– David C.
Nov 14 at 16:11
You're welcome :)
– Simon Hyll
Nov 15 at 1:57
add a comment |
up vote
2
down vote
accepted
up vote
2
down vote
accepted
Alright so schools in session (sorry if I explain too basic stuff at times, just trying to be thorough).
Here's the basic structure for a Vue project using vue init webpack-simple my-project
:
- src/
- assets/
- logo.png
- App.vue
- main.js
- assets/
- .babelrc
- .gitignore
- index.html
- package.json
- README.md
- webpack.config.js
The src
folder contains all the source files of your project.
The src/assets
folder contains all your assets, primarily images.
App.vue
is the first "view" of your app.
main.js
is the main script of your project where you configure and run Vue. This is where you load anything that should exist in the global scope of your app.
.babelrc
configures how the babel tool should syntax check your code.
.gitignore
tells Git to ignore certain files from committing.
index.html
is the page that's sent to the clients browser. This is where we load the main.js file and put any and all meta data you need (unless you use e.g. vue-meta to handle it there instead). Note that <div id="app">
html tag, this is where all your Vue files get mounted to.
package.json
is our npm configuration file. When you run e.g. npm install --save component-from-npm-name it's saved here so you can just run npm install later to get all the dependencies of your project.
README.md
is a documentation file in the Markdown language format. It's displayed as the frontpage of your project on e.g. Github or Gitlab.
webpack.config.js
is a Node.js file that is responsible for running Webpack on your project. Vue can be used without Webpack but I don't recommend it. You can run node webpack.config.js
directly to build your project. This file is your build script, you configured this to handle the build process of your project.
So, armed with this information, lets get to your question.
How do you load a component in Vue.js?
- Run
npm install --save vue-accordion
(note that while the source code is hosted on Github, the package is downloaded from here: https://www.npmjs.com/package/vue-accordion) - In your
index.js
file, which is responsible for loading things to your Vue app in the global context, you do as the Github page tells you and firstimport {vueAccordion} from 'vue-accordion'
, then runVue.component('vue-accordion', vueAccordion)
to register it in the global context.
That's all there is to it. index.js
is your entry point for your Vue app, while webpack.config.js
is your build script.
There is however an alternative solution to loading components. In the previous variant we loaded it in index.js
to load it in the global context, i.e. you can use the component now anywhere in your app, but what if you only want to load it on an as-is-needed basis (you'd wanna do this for performance reasons)?
Well, in your App.vue
file you have a <script>
tag where you can configure things in just that Vue component (all .vue files are Vue components, even if you call them routes, pages, views or whatever to indicated their purpose). In order to load a component not in the global context, but the component context, you'd do the following in App.vue
:
<script>
import Accordion from 'vue-accordion';
export default {
components: {
'vue-accordion': Accordion
}
</script>
Tips...
- This is just one setup for a Vue project. A Vue project can be as simple as just loading Vue as a script to your static index.html file, then you can have a much more annoying setup with regular javascript files, but that's dumb and inefficient. So, a proper project has a Node.js file to run Webpack. Depending on how you configure Webpack your project can act quite differently from any other Webpack project.
- Read up more on how Webpack works so you can have a project structure that makes sense for you.
- Take a look at Nuxt, it's essentially a collection of other projects (primarily Vue and Webpack) that simplifies the making of a powerful Vue project. You can sit and set up your own Vue project and all the tools yourself and get the same result, but Nuxt makes it simpler for you to do.
Alright so schools in session (sorry if I explain too basic stuff at times, just trying to be thorough).
Here's the basic structure for a Vue project using vue init webpack-simple my-project
:
- src/
- assets/
- logo.png
- App.vue
- main.js
- assets/
- .babelrc
- .gitignore
- index.html
- package.json
- README.md
- webpack.config.js
The src
folder contains all the source files of your project.
The src/assets
folder contains all your assets, primarily images.
App.vue
is the first "view" of your app.
main.js
is the main script of your project where you configure and run Vue. This is where you load anything that should exist in the global scope of your app.
.babelrc
configures how the babel tool should syntax check your code.
.gitignore
tells Git to ignore certain files from committing.
index.html
is the page that's sent to the clients browser. This is where we load the main.js file and put any and all meta data you need (unless you use e.g. vue-meta to handle it there instead). Note that <div id="app">
html tag, this is where all your Vue files get mounted to.
package.json
is our npm configuration file. When you run e.g. npm install --save component-from-npm-name it's saved here so you can just run npm install later to get all the dependencies of your project.
README.md
is a documentation file in the Markdown language format. It's displayed as the frontpage of your project on e.g. Github or Gitlab.
webpack.config.js
is a Node.js file that is responsible for running Webpack on your project. Vue can be used without Webpack but I don't recommend it. You can run node webpack.config.js
directly to build your project. This file is your build script, you configured this to handle the build process of your project.
So, armed with this information, lets get to your question.
How do you load a component in Vue.js?
- Run
npm install --save vue-accordion
(note that while the source code is hosted on Github, the package is downloaded from here: https://www.npmjs.com/package/vue-accordion) - In your
index.js
file, which is responsible for loading things to your Vue app in the global context, you do as the Github page tells you and firstimport {vueAccordion} from 'vue-accordion'
, then runVue.component('vue-accordion', vueAccordion)
to register it in the global context.
That's all there is to it. index.js
is your entry point for your Vue app, while webpack.config.js
is your build script.
There is however an alternative solution to loading components. In the previous variant we loaded it in index.js
to load it in the global context, i.e. you can use the component now anywhere in your app, but what if you only want to load it on an as-is-needed basis (you'd wanna do this for performance reasons)?
Well, in your App.vue
file you have a <script>
tag where you can configure things in just that Vue component (all .vue files are Vue components, even if you call them routes, pages, views or whatever to indicated their purpose). In order to load a component not in the global context, but the component context, you'd do the following in App.vue
:
<script>
import Accordion from 'vue-accordion';
export default {
components: {
'vue-accordion': Accordion
}
</script>
Tips...
- This is just one setup for a Vue project. A Vue project can be as simple as just loading Vue as a script to your static index.html file, then you can have a much more annoying setup with regular javascript files, but that's dumb and inefficient. So, a proper project has a Node.js file to run Webpack. Depending on how you configure Webpack your project can act quite differently from any other Webpack project.
- Read up more on how Webpack works so you can have a project structure that makes sense for you.
- Take a look at Nuxt, it's essentially a collection of other projects (primarily Vue and Webpack) that simplifies the making of a powerful Vue project. You can sit and set up your own Vue project and all the tools yourself and get the same result, but Nuxt makes it simpler for you to do.
edited Nov 14 at 2:28
answered Nov 14 at 2:16
Simon Hyll
9481922
9481922
A very thorough and simple to understand answer for a beginner like the question starter.
– Ru Chern Chong
Nov 14 at 2:26
Your response is precisely what I needed to understand so that I know exactly what I'm hacking at, and why! That you so much for taking the time to provide such an elaborate answer!
– David C.
Nov 14 at 16:11
You're welcome :)
– Simon Hyll
Nov 15 at 1:57
add a comment |
A very thorough and simple to understand answer for a beginner like the question starter.
– Ru Chern Chong
Nov 14 at 2:26
Your response is precisely what I needed to understand so that I know exactly what I'm hacking at, and why! That you so much for taking the time to provide such an elaborate answer!
– David C.
Nov 14 at 16:11
You're welcome :)
– Simon Hyll
Nov 15 at 1:57
A very thorough and simple to understand answer for a beginner like the question starter.
– Ru Chern Chong
Nov 14 at 2:26
A very thorough and simple to understand answer for a beginner like the question starter.
– Ru Chern Chong
Nov 14 at 2:26
Your response is precisely what I needed to understand so that I know exactly what I'm hacking at, and why! That you so much for taking the time to provide such an elaborate answer!
– David C.
Nov 14 at 16:11
Your response is precisely what I needed to understand so that I know exactly what I'm hacking at, and why! That you so much for taking the time to provide such an elaborate answer!
– David C.
Nov 14 at 16:11
You're welcome :)
– Simon Hyll
Nov 15 at 1:57
You're welcome :)
– Simon Hyll
Nov 15 at 1:57
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f53292041%2futilizing-a-component-from-github-in-my-vue-project-im-a-complete-beginner%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