Huxpro/huxpro.github.io

pwa影响了其他GitHub Pages

Open

#345 创建于 2020年1月19日

在 GitHub 查看
 (1 评论) (0 反应) (0 负责人)HTML (6,751 star) (4,539 fork)batch import
help wanted

描述

搭建了多个GitHub Pages情况下 访问 userName.github.io 没问题

当访问其他GitHub Pages， 访问 userName.github.io/repositoryName 时，会直接访问失败 访问 userName.github.io/repositoryName/ 时，访问成功

应该是由于pwa的原因，访问 userName.github.io/repositoryName/ 时会执行pwa的相关js

而使用隐身模式时一切正常

贡献者指南

技术栈
htmlcssjavascriptnodejs
领域
frontendperformance
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
basic knowledge of service workersunderstanding of GitHub Pagesfamiliarity with PWA concepts
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
40
研究方向
Investigate the service worker registration in the repository. The issue indicates that the PWA service worker is interfering with other GitHub Pages subdirectories (e.g., userName.github.io/repositoryName). Likely, the service worker is registered with a scope that covers the entire root, causing fetch events to handle requests to other repositories. Check the sw.js file (and any registration code) to see the scope parameter. If no scope is specified, the service worker defaults to the directory of the script, but since it's likely at the root, it may need to be scoped to the root only. Consider adding a scope of './' or checking if the service worker should be unregistered for subdirectories. Also, verify that the PWA is configured to not intercept cross origin or other subdirectory requests. The fix may involve limiting the service worker's fetch event handling to only the blog's own pages.