Hot reload or watch does not work
I investigated and
- Deleted node_modules and install it again
- fs.inotify.max_user_watches = 524288
- Try to sudo start quasar dev
- use – --reset-cache
And all other suggestions I was able to find. But now I am desperate. I have no options left and it does not work.
dobbel last edited by
what’s the output of
I run quasar in WSL2 on windows 10 pro.
Questio:n has hot reload ever worked for you in this setup / did it recently stopped working. Or has it never worked?
I see you use WSL2 on windows.
What if you run the same project on ‘just’ windows?
It used to work, but I did not work on my project for 6 month so I do not know when it stopped working. If I try it on windows it fails because I need to remove node_modules folder and run
npm installagain under windows to get appropriate binaries. May be if I do it, it will work, but then commands under WSL will stop working.
This is how I fix this. I install another copy of Ubuntu as WSL 1 and run quasar from there. Now reload is working.
I have an issue where hot reload works great for a while, then suddenly stops and reverts back to the last full build. I’m also only able to get hot reload started by renaming the public directory (to anything else) and then changing it back to public so I can reach my laravel API. After a bit, I get a CORS error:
Access to XMLHttpRequest at ‘http://app.wb.localhost/user’ from origin ‘http://app.wb.localhost:8080’ has been blocked by CORS policy. For a while it was working pretty well, I’d have to reset once or twice a day, but suddenly it’s failing every few file updates. I’ve tried changing privileges on the storage directory, launching with sudo and making sure my config file is cached…
dobbel last edited by
What’s the output of
Honestly that are a
lotof things going very wrong. I personally would try to run it on another system and see how it behaves there.
I did a fresh install several times, each time documenting my steps, that’s how I was able to figure out if I rename the public directory it works. It has been working the last few weeks and suddenly having issues.
Operating System - Darwin(19.6.0) - darwin/x64
NodeJs - 10.0.0
Important local packages
quasar - 1.15.1 – Build high-performance VueJS user interfaces (SPA, PWA, SSR, Mobile and Desktop) in record time
@quasar/app - 2.1.14 – Quasar Framework local CLI
@quasar/extras - 1.9.14 – Quasar Framework fonts, icons and animations
eslint-plugin-quasar - Not installed
vue - 2.6.12 – Reactive, component-oriented view layer for modern web interfaces.
vue-router - 3.2.0 – Official router for Vue.js 2
vuex - 3.6.0 – state management for Vue.js
electron - Not installed
electron-packager - Not installed
electron-builder - Not installed
@babel/core - 7.12.10 – Babel compiler core.
webpack - 4.44.2 – Packs CommonJs/AMD modules for the browser. Allows to split your codebase into multiple bundles, which can be loaded on demand. Support loaders to preprocess files, i.e. json, jsx, es7, css, less, … and your custom stuff.
webpack-dev-server - 3.11.0 – Serves a webpack app. Updates the browser on changes.
workbox-webpack-plugin - Not installed
register-service-worker - 1.7.1 – Script for registering service worker, with hooks
@capacitor/core - Not installed
@capacitor/cli - Not installed
@capacitor/android - Not installed
@capacitor/ios - Not installed
Quasar App Extensions
Host - DylanMBP.lan
en0 - 192.168.101.18
Just realized that it was launching Safari instead of Chrome suddenly and the hot reloading seems to be working in Safari!
NodeJs - 10.0.0
For Quasar v1 you should use nodejs v12.x.
I did a fresh install several times, each time documenting my steps,
I meant running it on a Windows or linux based OS instead of Mac.
I live on a boat, and all I have is a mac. Thanks, I’ll check on the v of node. I am seeing more hot reload info in Safari, when it stops working, here’s what I get:
[HMR] Aborted because ./src/store/post.js is not accepted
Update propagation: ./src/store/post.js -> ./src/store/index.js -> ./.quasar/app.js -> ./.quasar/client-entry.js -> 0
I also noticed that if I rename my public directory from ‘public’ and refresh, the hot reload starts working again. I’m developing a mixed quasar environment with Laravel backend. I access the Laravel API through a virtual server and i’m running the hot reload on port 8080 with quasar dev with this command:
sudo quasar dev -H app.wb.localhost
You could consider using virtrual box to run it with another OS. Apart from that I unfortunately have no clues/ideas on how to fix your problem .
Hey, thanks for the suggestion and for taking the time to consider the issue i’m having. Virtual Box looks like it could work, might resolve some issues and add some other benefits!
I am having the same reload issue here, also using a Mac.
It started after adding support to Quasar and a package update.