@iklemm Did you unregister the service worker within the updated() method in the service worker itself, or in your app code?

Just to expand this topic a bit. I’ve been using Quasar for about 6 months on two different machines. Setting breakpoints has always been problematic. Typically, I can set breakpoints in pure .js files just fine, while breakpoints shown in any .vue file appears as “unbound breakpoint”. Then, magically, some day / build / version / phase of the moon I will hit a breakpoint in a .vue file giving me false hope, which is invariably dashed soon thereafter. Frustrating.

Like the above, I too am using a mixin, hmm… Of course I can “quasar create” a new app which hits every breakpoint just fine.

I’ve tried:

• Updating webpack and all other related node_modules.
• launch.json: Playing with dozens of variations of:
  “webRoot”: “${workspaceFolder}/ClientApp/src”,
  “sourceMaps”: true,
  “sourceMapPathOverrides”: {
  “webpack:///./src/": "${webRoot}/”
  }
• Updating Chrome, VSCode, Debugger for Chrome
• babel.config.js
  module.exports = {
  presets: [
  ‘@quasar/babel-preset-app’
  ]
  }
• quasar.conf.js
  build: {
  vueRouterMode: “history”, // available values: ‘hash’, ‘history’
  devtool: “source-map”, // tried lots of variations here!
  analyze: false, // jayb
  extendWebpack(cfg) {
  // cfg.plugins.push(new Analyzer.BundleAnalyzerPlugin()); // jayb added
  cfg.plugins.push(new WorkerPlugin()); // jayb added
  },
  },

STOP THE PRESSES. I just tried commenting out “devtool” and “analyze” in quasar.conf.js (since a “quasar create” project doesn’t include these lines), and I’m hitting breakpoints again! Another moment of false hope? I’ll report back soon…

This example should be in the docs!

THE ABOVE IS THE MOST IMPORTANT POST ON THE ENTIRE INTERNET!!! VEXED? I WAS WAY BEYOND VEXED! I WAS DAZED! CONFUSED! CONTEMPLATING A BITTER END TO THINGS! GOING OFF THE DEEP END! WINDING MY WAY THROUGH A LONG DARK TUNNEL! DROWNING IN A POOL OF MY OWN TEARS! AT THE END OF MY ROPE!

thank you