The new Vue.js 3.0 plugin architecture is nice, but it seems to to be missing a router plugin. If I choose not to install routing when I first create the project (vue create my-project), I'd expect that I could change my mind later and add routing with something like vue add #vue/router, but that plugin doesn't appear to exist. Is there a way to add routing from the CLI after the fact?
After some experimenting with vue-cli3, i found that you can use vue add to setup components you missed.
Use vue add router That set up the routing and created some sample components Home and About.
This also work for other modules like adding vuetify with vue add vuetify. You can read more about vue add from the plugins and presets guide
Have a look at the issue page here: https://github.com/vuejs/vue-cli/issues/1202, the conclusion is you can't use cli to add router if you didn't choose router initially.
With three reasons:
Late-adding router when you've already modified the entry file is extremely fragile.
If you haven't modified the file much, you can just re-generate the project instead.
If we only add the dependency and skip the file-modifying part, then it's easier to just npm install vue-router or yarn add vue-router.
Related
npm is great to download some js libraries, but including the into a vue app is really hard. i have no idea if there is an "official" way, but searching online i see so many different approaches.
sometimes it is imported in the app.js file, sometimes in the .vue files inside the tags. i have also seen that there are vue plugins that handle differently. how should i know if i have a vue plugin or not? i don't even know what the other option would be. like a vue module instead of a vue plugin?
is there a way that the vue app just includes/imports the stuff from node_modules so i can use it? so that after doing some npm install it is all available?
Npm just downloads the library into the node_modules folder and let's you access it where you need it.
If it's a vue component you need to import it in a vue file, because that's where you need it.
If it's a vue plugin you have to import it in the main js file because that's where it gets initalized in the whole app.
Looks like you are new to vue, I suggest you to take a look at this simple guide where you can learn some basic stuff.
I want put my Vue project in the Electron, so I find the method in the Internet. According to the given method on the Intenet, I make a demo to test it.
At frist, I create Vue project using vue create myProject, then I use vue add electron-builder to add Electron, then I choose the Electron version, then it prepare to install the additional dependencies. But the error is thereļ¼
Someone could help me? Thanks!
electron-vue: An Electron & Vue.js quick start boilerplate with vue-cli scaffolding.
maybe you can try it.
I've Electron Project, but I can't use vuejs inside it...so how to use vuejs inside it? or I should install vue cli and install electron?
The easiest way that I have seen currently is to create your Vue site first, with vue-cli 3, and then a vue-cli-plugin- but not electron-vue, which is stale. Use vue-cli-plugin-electron-builder. Starting with this, you can then add all the Vue you want.
I am new to nuxt. I want to know whether is it possible to use Buefy on nuxt just by using CDN
as I directly imported beufy CDN in script in head function of nuxt.config
But it gave error while using navbar of beufy that the component is not registered correctly.
Nuxt supports buefy by default, when installing using npx create-nuxt-app you'll be asked if you want to use a component framework (buefy is an option here).
If you want to use it in an installed project you can npm install buefy --save and then add "nuxt-buefy" in the modules array of your nuxt.config
I'm trying to register a vue component (https://www.npmjs.com/package/vue-numeric) in a sails app. there is provision to create a new component using parasails.registerComponent but not sure how to include an existing one. I'm using Sails version 1.1 and the included version of Vue.
You can find a detailed answer here.
However, I guess you might want to install a component that has dependent components in turn, and this is not trivial.
The issue is open on GitHub and these are the best answers I got so far:
Register each component
or, include the component as an already compiled bundle