question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Chrome Warnings - GenerateSW has been called multiple times

See original GitHub issue

Describe the bug Console warnings when run to pwa mode:

[WDS] Warnings while compiling.
GenerateSW has been called multiple times, perhaps due to running webpack in --watch mode. The precache manifest generated after the first call may be inaccurate! Please see https://github.com/GoogleChrome/workbox/issues/1790 for more information

Codepen/jsFiddle/Codesandbox (required) not aplicable

To Reproduce Steps to reproduce the behavior:

  1. run in pwa mode
  2. update pages/index.vue
  3. save and auto-reload
  4. show warning in console

Expected behavior

Screenshots https://www.dropbox.com/s/qbqje4v7uy5sojp/bug1.png?dl=0

Platform (please complete the following information): OS: MacOS Catalina 10.15.5 Node: 10.18.1 NPM: 6.13.4 Yarn: Browsers: Chrome Version 83.0.4103.106 (Build oficial) (64 bits) iOS: Android: Electron:

Additional context Quasar/app v2 1.12.7

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:6 (2 by maintainers)

github_iconTop GitHub Comments

4reactions
jmunckhofcommented, Mar 16, 2022

I think I explained it clearly the first time. GoogleChrome/workbox#1790 It’s kind of out of our reach. Just ignore it as it will not break anything. @jmunckhof

Oh Okay, Is there a way to suppress these warnings?

3reactions
rstoenescucommented, Jun 23, 2020

Hi,

Like it is described in https://github.com/GoogleChrome/workbox/issues/1790 there is no good way to fix this (especially from Quasar side). However, we do not want to supply a dummy service worker in dev mode because that would make the whole developer experience awful. You’d be able to test your service worker only on production builds which adds a lot of overhead and time lost. But like we wrote in our docs, when you develop an app and your goal at that moment does not include handling the service worker, you can temporarily switch to “quasar dev -m spa”. Wish the workbox team would find a way to avoid the issue, but at the moment, it is what it is.

Read more comments on GitHub >

github_iconTop Results From Across the Web

PWA - hot reload causing errors - Quasar forum
GenerateSW has been called multiple times, perhaps due to running webpack in --watch mode. The precache manifest generated after the first call ...
Read more >
workbox-build - Chrome Developers
Keeping the runtime separate means that users will not have to re-download the Workbox code each time your top-level service worker changes.
Read more >
Why does workbox-webpack-plugin prepend "auto" to all ...
WARNING in InjectManifest has been called multiple times, perhaps due to running webpack in --watch mode. The precache manifest generated ...
Read more >
next-pwa - npm
After running next build , this will generate two files in your public ... The following setup has nothing to do with next-pwa...
Read more >
allanchain/gridsome-plugin-pwa - npm.io
It tries to be more similar to cli-plugin-pwa , but makes use of ... lead to a new service worker file being created...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found