Hot reload or watch does not work

Serhioromano

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

@Serhioromano

what’s the output of quasar info?

Serhioromano

I run quasar in WSL2 on windows 10 pro.

Operating System - Linux(4.19.128-microsoft-standard) - linux/x64
NodeJs - 10.23.0

Global packages
  NPM - 6.14.10
  yarn - Not installed
  @quasar/cli - 1.1.2
  cordova - 9.0.0 (cordova-lib@9.0.1)

Important local packages
  quasar - 1.14.7 -- Build high-performance VueJS user interfaces (SPA, PWA, SSR, Mobile and Desktop) in record time
  @quasar/app - 1.9.6 -- Quasar Framework local CLI
  @quasar/extras - 1.9.12 -- Quasar Framework fonts, icons and animations
  eslint-plugin-quasar - Not installed
  vue - 2.6.11 -- 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 - 7.3.3 -- Build cross platform desktop apps with JavaScript, HTML, and CSS
  electron-packager - 14.2.1 -- Customize and package your Electron app with OS-specific bundles (.app, .exe, etc.) via JS or CLI
  electron-builder - Not installed
  @capacitor/core - Not installed
  @capacitor/cli - Not installed
  @capacitor/android - Not installed
  @capacitor/ios - Not installed
  @babel/core - 7.12.3 -- Babel compiler core.
  webpack - 4.43.0 -- 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 - 4.3.1 -- A plugin for your Webpack build process, helping you generate a manifest of local files that workbox-sw should precache.
  register-service-worker - 1.7.1 -- Script for registering service worker, with hooks
  typescript - 3.8.3 -- TypeScript is a language for application scale JavaScript development

Quasar App Extensions
  @quasar/quasar-app-extension-icon-genie - 1.1.3 -- A Quasar CLI Extension for Making All Your Icons

Networking
  Host - HadesCanyon
  eth0 - 172.21.188.***

dobbel

@Serhioromano

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?

Serhioromano

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 install again 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.

dylanglockler

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

@dylanglockler

What’s the output of quasar info?

Honestly that are a lot of things going very wrong. I personally would try to run it on another system and see how it behaves there.

dylanglockler

@dobbel

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

Global packages
NPM - 6.14.8
yarn - 1.13.0
@quasar/cli - 1.1.3
@quasar/icongenie - Not installed
cordova - Not installed

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
typescript - 3.9.5 – TypeScript is a language for application scale JavaScript development
@capacitor/core - Not installed
@capacitor/cli - Not installed
@capacitor/android - Not installed
@capacitor/ios - Not installed

Quasar App Extensions
None installed

Networking
Host - DylanMBP.lan
en0 - 192.168.101.18

dylanglockler

Just realized that it was launching Safari instead of Chrome suddenly and the hot reloading seems to be working in Safari!

dobbel

@dylanglockler

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.

dylanglockler

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
hotApplyInternal@http://app.wb.localhost:8080/app.js:558:39
hotApply@http://app.wb.localhost:8080/app.js:412:35
http://app.wb.localhost:8080/app.js:387:30
promiseReactionJob@[native code]

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

dobbel

@dylanglockler said in Hot reload or watch does not work:

I live on a boat, and all I have is a mac.

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 .

dylanglockler

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!

JBGoldberg

I am having the same reload issue here, also using a Mac.
It started after adding support to Quasar and a package update.

dylanglockler

@dobbel I setup Laravel Homestead with Vagrant using VirtualBox (on mac os). I’m able to run the site as a virtual server but when I run the dev -H for hot reload, I’m getting site not found - I’m thinking maybe has to do with the port. I tried using a port in the Homestead.yaml, but then dev with hot reload advances to the next port.

dobbel

This post is deleted!

dobbel

@dylanglockler

Sorry I don’t really understand your setup and what is running where and why.

I run the dev -H for hot reload

that’s for setting a hostname, -H . What has this to do with hot reload? Quastion : without -H quasar dev does show a site?

dobbel

@dylanglockler

I found some info about hot reload fixes in the docs:

If there appears to be an issue with hot reload, you can try two fixes:

Change the permissions for the project folder with

sudo chown -R username: .
or run the dev server with root privileges

sudo quasar dev

(scroll down, last entry)
https://quasar.dev/quasar-cli/commands-list#Dev

dylanglockler

@dobbel

Appreciate the note - fundamentally I’m trying to setup Qasar front-end with a Laravel back-end (API) WITH hot reload working (otherwise development is unreasonably cumbersome). It works, with one little trick: I have to rename larave/public to public_x, run the command: sudo quasar dev -H app.wb.localhost

And then rename public_x back to public (so the app can access the API through the Laravel side on a virtual host I setup)

And then it’s AMAZING - I can work so quick, editing my quasar vue files, hot reload refreshes as expected - maintains state and logs me out of the app when I make changes to config or store files - all good!

But after a while, it will suddenly revert to the last version created when I last ran the build command. For a while it was only doing this once or twice a day and I was just working with that… but now, after just a few edits, it resets. I can find no errors in any logs nor can I find any common step that causes it to suddenly stop using the hot reload files and suddenly start serving the previous production build.

From your earlier suggestion, I did try switching over to a VirtualBox - built on Homestead + Vagrant. I’m able to get the server up and serving either Laravel or Quasar but having a time figuring out how to get both running simultaneously. Every time I try to run quasar dev it seems to work but but the browser can’t connect to server. I have the route in my hosts etc:
192.168.10.10 wanderbird.test

and my quasar info:

Operating System - Linux(5.4.0-65-generic) - linux/x64
NodeJs - 14.15.4

Global packages
NPM - 6.14.11
yarn - 1.22.10
@quasar/cli - 1.1.3
cordova - Not installed

Important local packages
quasar - 1.11.3 – Build high-performance VueJS user interfaces (SPA, PWA, SSR, Mobile and Desktop) in record time
@quasar/app - 1.8.10 – Quasar Framework local CLI
@quasar/extras - 1.8.1 – Quasar Framework fonts, icons and animations
vue - 2.6.11 – Reactive, component-oriented view layer for modern web interfaces.
vue-router - 3.2.0 – Official router for Vue.js 2
vuex - 3.4.0 – state management for Vue.js
electron - 7.1.4 – Build cross platform desktop apps with JavaScript, HTML, and CSS
electron-packager - Not installed
electron-builder - Not installed
@capacitor/core - Not installed
@capacitor/cli - Not installed
@capacitor/android - Not installed
@capacitor/ios - Not installed
@babel/core - 7.7.4 – Babel compiler core.
webpack - 4.43.0 – 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 - 4.3.1 – A plugin for your Webpack build process, helping you generate a manifest of local files that workbox-sw should precache.
register-service-worker - 1.7.1 – Script for registering service worker, with hooks
typescript - 3.8.3 – TypeScript is a language for application scale JavaScript development

Quasar App Extensions
None installed

Networking
Host - homestead
eth0 - 10.0.2.15
eth1 - 192.168.10.10

Any thoughts you might have would be greatly appreciated!

dobbel

@dylanglockler

I will read your post more thoroughly later, but just quick comment about your quasar info output:

NodeJs - 14.15.4

Use Nodejs v12.x ( no other version for Qv1 apps)

See:
https://quasar.dev/quasar-cli/installation

No More Posting New Topics!

Hot reload or watch does not work