Assuming you need completely separate builds, with some shared scripts guided by your entries, you can add separate build commands. In your package.json “scripts” section: “scripts”: { “build:admin”: “vue-cli-service build –dest dist/admin src/admin/index.js, “build:public”: “vue-cli-service build –dest dist/public src/public/index.js } For admin builds, you may run: npm run build:admin and for public builds: npm run … Read more
As already pointed out, it’s more of a “service workers” issue than a “vue cli” one. First of all, to make sure we’re on the same page, here’s what the boilerplate content of registerServiceWorker.js should look like (vue cli 3, official pwa plugin): import { register } from ‘register-service-worker’ if (process.env.NODE_ENV === ‘production’) { register(`${process.env.BASE_URL}service-worker.js`, … Read more
Based on the docs: npm run test — -u I verified this works.
A few tips for people who land here: Make sure your .env files are in the project root folder (and not in say src/) Variable names should start with VUE_APP_ if to be statically embedded into the client bundle Restart the dev server or build your project for changes to take effect If you are … Read more
npm run build creates a dist directory with a production build of your app. In order to serve index.html in a browser you need an HTTP server. For example serve: npm install -g serve serve -s dist The default port is 5000, but can be adjusted using the -l or –listen flags: serve -s build … Read more
My problem was WDS Console displayed: [HMR] Waiting for update signal from WDS… [WDS] Disconnected! GET http://ip:port/sockjs-node/info?t=some-number net::ERR_CONNECTION_TIMED_OUT sockjs.js?some-number Solution for me was: in package.json change “serve”: “vue-cli-service serve”, to “serve”: “vue-cli-service serve –host localhost”, or add module.exports = { devServer: { host: ‘localhost’ } } to vue.config.js 🙂
Where is the config files and why isn’t it anywhere in the top level folders, etc? The initial project doesn’t require the file to exist because you just created a project with fresh “default” settings that don’t require any config. Just create it yourself. it’s even mentioned in the README: Many aspects of a Vue … Read more
First: always read the official documentation. With Vue you can build a SPA, and a MPA is also no problem. Just follow the guides: https://cli.vuejs.org/ https://cli.vuejs.org/guide/html-and-static-assets.html#building-a-multi-page-app https://cli.vuejs.org/config/#pages You should create a new project with Vue CLI 3. Once you’ve created your project set it to be manually configured. Make sure you don’t choose the SPA … Read more
There are some out-of-date answers here. Because vue-cli 3 is using a zero configuration approach, the way to disable it is to just uninstall the module: npm remove @vue/cli-plugin-eslint
Vue 2 The following also works in Vue 3 but is deprecated. Sass: Â Â Use ::v-deep ::v-deep .child-class { background-color: #000; } Not using Sass: Â Â Use >>> >>> .child-class { background-color: #000; } With either syntax, the <style> tag for this component must be scoped: <style scoped> Vue 3 (and Vue 2.7) In Vue 3, the … Read more