@necmettin recently I’ve worked with a simple tool called Ngrok. Which you can download here: https://ngrok.com/ . Just follow the instructions on the website and you should be able to expose your localhost to a generated url (or a name you choose yourself, see https://ngrok.com/docs#subdomain). You can send that url to your clients, or whoever you want.
Have fun gathering feedback and impressing your clients
@Sujan-Dev Upgrading the CLI shouldn’t break anything. The build process is defined by the starter kit that you are using (see /build folder in your project’s folder). You say that you build and then serve the dist folder from an apache server and it doesn’t works. If it worked before upgrading the CLI, it should work just the same after upgrading it. Nothing changed regarding build. The problem is elsewhere. I am a little confused as you then say “the project is run in dev mode”. Are you serving the distributable (/dist) or are you running the development server? In both situations, upgrading CLI won’t break anything. It may be your apache at fault. Have you tried with quasar serve command after making a build? It does an ad-hoc web server pointed to your distributable – so basically same thing as apache.
I tried cmd, git bash, npm.cmd & node independently
Problem was that npm install -g quasar-cli was not installing the quasar.cmd files in the .bin file of nodist(node/npm version control).
I had to reinstall nodist (and node and npm) after an update.
quasar.cmd was installed properly and am up & running.
Mind you I’ve got to update a couple of node_modules now
@cherry314159 it’s indeed a “bug” that sneeked into one of latest webpack builds. I fixed it in the base file.
As for “bigness”, quasar is not big yet in terms of nr of contributors, but it is in terms of completeness. On top of that, it’s high quality code/ low bugs. At least that’s been my experience for last 3 months. Also gitstars are rising rapidly.