Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Lighthouse: respond with a 200 when offline#175

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
yyx990803 merged 2 commits intovuejs:masterfromStevenYuysy:master
May 6, 2017

Conversation

StevenYuysy
Copy link
Contributor

@StevenYuysyStevenYuysy commentedMay 4, 2017
edited
Loading

@yyx990803yyx990803 merged commit5aad15b intovuejs:masterMay 6, 2017
@yyx990803
Copy link
Member

Thanks!

@astoimenov
Copy link

I don't know if I'm the only one experiencing this, but with this setting the Service worker caches the home page of my app and it's trying to get old versions of the main js files (0.js, main.js, app.js and manifest.js with their corresponding hashes).

@Sleashe
Copy link

Sleashe commentedJun 6, 2017
edited
Loading

@astoimenov I think this is normal. If you're using Chrome, simply check theUpdate on reload when developing (Under Applications > Security > Service Worker tab)

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

4 participants
@StevenYuysy@yyx990803@astoimenov@Sleashe

[8]ページ先頭

©2009-2025 Movatter.jp