


You don’t need it for anything else at this point. Once a project folder has been generated, Quasar CLI will only help in running commands globally. The second package is the heart of it and it gets installed into every Quasar project folder. Quasar CLI is made up of two packages: and The first one is optional and only allows you to create a project folder and globally run Quasar commands. To continue your learning about Quasar, you should familiarize yourself with the Quasar CLI in depth, because you will be using it a lot. This one project can seamlessly handle all of them. Note that you don’t need separate projects if you want to build any of the available platforms. This is also true in Docker for Windows based development environments. Projects will build around 3X slower and HMR (Hot Module Reload) will not work ( without a hack) if the project files are on the Windows mount instead of the local linux file system. When using WSL2 (Windows Subsystem for Linux) Microsoft recommends keeping files in the linux file system to maximize performance. Microsoft’s recommended Nodejs development environment setup in WSL2.
