Add new cli-service command instead of modifying existing. about vue-cli-plugin-browser-extension HOT 3 CLOSED

Definitely not out of the question, but I think your issue stems from your project setup. If you've got a set of shared components, you might want to go with a monorepo setup (Lerna or yarn workspaces do this well), where you have a package with all your shared components that is a dependency of your extension and web projects.

.
|- packages/
|   |- extension/
|       |- run `vue create .` and `vue add browser-extension`
|   |- project/
|       |- your existing web project
|   |- shared/
|       |- src/
|           |- components/
|               |- shared components
|- package.json

from vue-cli-plugin-browser-extension.

Hmm, what I was thinking of doing was, to manage all the builds under same Vue CLI setup. So my current setup looks like this.

What I can understand from your structure is that I'll need to install separate Vue CLI for extension and project right?

from vue-cli-plugin-browser-extension.

You're correct: I would recommend separate vue-cli projects per build style. On top of that, I would recommend a common components project that would be the source of anything you would want to be reusable across projects.

Closing due to the recommendation that a monorepo setup is the preferred project setup at this time for component reuse across different build types: web app, electron app, browser extension, and mobile app.
I'll be happy to revisit this in the future as technology continues to evolve, but at this time, supporting more than just browser extensions is outside the scope of this project.

from vue-cli-plugin-browser-extension.