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

Bug: `Failed to fetch` during workflows run

Open
#2,686 3 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
github-actions, typescript
Domain
devops, testing-qa

Research direction

Start with the linked GitHub Actions workflow run and inspect the test step around step:5:96 for the failing chrome-extension://test-extension-id/page.html fetch. Locate the test and the fetch code that rejects the chrome-extension URL scheme, then reproduce the intermittent failure in that workflow. The change is done when the affected test no longer reports an unsupported URL scheme error.

Written by the indexing model from the issue text.

Description

contribution welcome pkg/wxt upstream

Failed to fetch from "chrome-extension://test-extension-id/page.html": URL scheme "chrome-extension" is not supported.

https://github.com/wxt-dev/wxt/actions/runs/40075085504/job/120816695984?pr=2652#step:5:96

It's happening for a couple of times during those tests.

Dominant language
TypeScript
Stars
10.6k
Forks
581
Avg merge
2d 8h
Merged PRs (30d)
46

Getting set up

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 wxt-dev/wxt

All issues in wxt-dev/wxt

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.