This page looks best with JavaScript enabled

Quasar Dev Stuck Without Errors

 ·   ·  ☕ 2 min read

Do you see quasar dev stuck but no errors reported anywhere? The fix was quite easy - only the way to get to the fix was frustrating.

I faced this issue in a medium-sized project that I was playing around with. I was stupid enough to change a few lines in multiple components, and lo and behold - I don’t see the changes being compiled. Restarting quasar dev doesn’t help either.

The command simply does not move ahead beyond a point..


The first and foremost thing you do is to revert things to where they were. With no real commits, I could only fidget around till I get to a working state, or go back to the original.

After trying about 10 minutes, I gave up and was exploring package.json and quasar CLI params to see whether I could anything else. And.. saw this.

"scripts": {
    "lint": "eslint --ext .js,.vue --ignore-path .gitignore ./",
    "test": "echo \"No test specified\" && exit 0"

I see commands, I run them. So, lint it was.

npm run lint


Looks like quasar dev breaks without errors if there are errors in templates - who knew..? I do remember seeing errors in Vue CLI for similar issues - should go back, compare them, and report the issue back to the teams (soon 🐌).

Also, linting helps. Again, who knew.. :)?

The fix by itself was easy enough. All it needed was a change in two lines of code in distinct components. And, I was all set to continue breaking the application further.

Stay in touch!
Share on

Prashanth Krishnamurthy
Prashanth Krishnamurthy
Technologist | Creator of Things