cloudflare/vinext

Pages Router: CSS files with URL-encoded characters in path not served / not applied

Closed

#1,472 opened on May 22, 2026

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)TypeScript (371 forks)github user discovery
adapter-api-e2ehelp wanted

Repository metrics

Stars
 (8,563 stars)
PR merge metrics
 (Avg merge 1d 1h) (462 merged PRs in 30d)

Description

This issue was created by an agent analysing CI failures from the Next.js Deploy Suite (vinext main vs Next.js v16.2.6, 2026-05-22).

Problem

A page importing CSS via a path that contains special characters (URL-encoded) should produce a blue background. The test observes the default transparent background, meaning the CSS resource at the URL-encoded path is either not served or the asset URL is encoded incorrectly so the browser never loads the file.

Expected background `rgb(0, 0, 255)`, received transparent

Estimated Impact

~1 test failures across the deploy suite.

Affected Test Suites

  • test/e2e/app-dir/resource-url-encoding/resource-url-encoding.test.ts

Recommendation

  1. Reproduce first in vinext's own test suite. Add a Pages Router fixture that imports ./styles/with space.css and assert the rendered page has the expected colour.

  2. Round-trip the encoding. Make sure the emitted <link rel="stylesheet" href=...> URL is URL-encoded and that the static-asset server decodes paths before lookup, so the encoded URL resolves to the file on disk.

Contributor guide

Research direction
Add a Pages Router fixture that imports a CSS file with URL encoded characters (e.g., `./styles/with space.css`) and test that the rendered page has the expected blue background. Inspect the emitted `<link rel="stylesheet">` tag's href to verify it is URL encoded, then ensure the static asset server decodes the path before file lookup.
Tech stack
typescriptnodejsvite
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitNode.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70