Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Affected functionality] Permanent website reloads #1807

Open
Michael-Kolpakov opened this issue Oct 23, 2024 · 0 comments
Open

[Affected functionality] Permanent website reloads #1807

Michael-Kolpakov opened this issue Oct 23, 2024 · 0 comments
Assignees

Comments

@Michael-Kolpakov
Copy link
Contributor

Michael-Kolpakov commented Oct 23, 2024

Environment: Windows 11 Pro, Google Chrome 130.0.6723.70
Reproducible: sometimes
Build found: eabb40e

Preconditions

  1. Run website locally.

Steps to reproduce

  1. Go to the main page.

Actual result
When you try to launch a website locally, it is highly likely that it falls into a state of permanent reloads and the only way that helps is either clearing the cache or restarting the website again (the last does not always help).

Expected result
Normally working website.

Additional information
The error that appears with this problem: 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.

@Michael-Kolpakov Michael-Kolpakov moved this to ✍Planned in StreetCode Oct 23, 2024
@Michael-Kolpakov Michael-Kolpakov changed the title [Affected functionality] Permanent website reloads. [Affected functionality] Permanent website reloads Oct 23, 2024
@Michael-Kolpakov Michael-Kolpakov moved this from 🏗 In progress to 👀PR in StreetCode Oct 30, 2024
@Michael-Kolpakov Michael-Kolpakov moved this from 👀PR to 🔎In Q/A in StreetCode Nov 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 🔎In Q/A
Development

No branches or pull requests

2 participants