This directory holds the actual configurations for both the development server and the production webpack build. Normally you don’t need to touch these files unless you want to customize Webpack loaders, in which case you should probably look at
This is the main configuration file that exposes some of the most common configuration options for the build setup.
This is where most of your application code will live in. How to structure everything inside this directory is largely up to you; if you are using Vuex, you can consult the recommendations for Vuex applications.
This is the template index.html for our single page application. During development and builds, Webpack will generate assets, and the URLs for those generated assets will automatically injected into this template to render the final HTML.
This directory is an escape hatch for static assets that you do not want to process with Webpack. They will be directly copied into the same directory where webpack-built assets are generated.
See Handling Static Assets for more details.
Component templates that you can use along Quasar CLI to generate
*.vue files for your App. See Generating Components.
The NPM package meta file that contains all the build dependencies and scripts (including build scripts used by Quasar CLI).