Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Website: the docs site's own service worker can't install (navigateFallback "/" isn't precached)

Open Beginner friendly
#173 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
70/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript

Research direction

Start by checking the built .output/public/sw.js and the docs site's @vite-pwa/nuxt configuration. Choose one of the proposed fixes: remove the PWA integration, or set registerType to autoUpdate and workbox.navigateFallback to null. Confirm the service worker installs in DevTools.

Written by the indexing model from the issue text.

Description

bug

From the 2026-10-08 front-end review, checked in the built .output/public/sw.js.

sw.js registers NavigationRoute(createHandlerBoundToURL("/")), but / isn't in the precache manifest (only _payload.json files and _nuxt assets are). Workbox throws non-precached-url when the route is registered, so the worker fails to install. Our own PWA page warns readers about this exact navigateFallback trap.

If it did install, registerType defaults to 'prompt' and the site has no prompt UI, so new docs would wait until every tab is closed.

Fix. Either remove @vite-pwa/nuxt from the docs site (a docs site gains little from it), or set registerType: 'autoUpdate' and workbox.navigateFallback: null. Then confirm in DevTools that the worker installs.

Dominant language
Vue
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from components-web-app/docs

All issues in components-web-app/docs

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.