Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Catch-all route chunks are named `_...404_-<hash>.js`; the `..` trips path-traversal guards and breaks the lazy preload

オープン
  • 何か問題がありますか？
#391 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

@everton-dgn がすでに取り組んでいます。

2026年10月3日 から。

  • #393 @everton-dgn による — オープン

評価

難易度
3/5
見積もり時間
1〜2日
初心者へのやさしさ
68/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
typescript, vite
領域
build-system, tooling

調査の方向性

Start by reading the client-build configuration in src/index.ts (config and configEnvironment) and src/ssr/index.ts. Reproduce with the linked solid-v2/fullstack example and inspect the production chunk name for [...404].tsx. Done means client route chunk names no longer contain path-traversal-like dot runs, while a user-supplied sanitizeFileName is preserved.

索引モデルが issue の本文から書いたものです。

説明

Summary

A catch-all route file such as [...404].tsx builds to a client chunk named _...404_-<hash>.js. Any server, static host, CDN or WAF whose path-traversal guard rejects URLs containing .. refuses that chunk. The lazy route's module preload then fails, and hydration of that route breaks:

  • Without a <Loading> boundary: the document-root fallback dies with Hydration Mismatch, and the page is dead.
  • With one: the boundary re-imports the chunk, fails again, and the root is replaced by the entry's error UI.

Every [...rest] route is affected, deterministically, in production.

This was split out of solidjs/solid#3338, where it came up as a second, deterministic cause of the reporter's dead-page symptom.

Reproduction

From the reproduction on solidjs/solid#3338: the solid-v2/fullstack template (solid-js / @solidjs/web 2.0.0-rc.6, @solidjs/router 2.0.0-next.21, @solidjs/vite-plugin 3.0.0-next.39), with the fileRoutes() catch-all [...404].tsx, as a production build served by the template's server.js:

$ curl -i http://localhost:3000/assets/_...404_-BW0HgTxD.js
HTTP/1.1 404 Not Found
content-type: text/html; charset=utf-8

The template's server.js refuses any URL containing .., so the chunk request falls through to SSR and comes back as the 404 HTML page. The guard is being fixed in the template separately (resolved-path containment instead of a substring check). But substring .. checks are common in hosts and middleware the plugin doesn't control, so the chunk name itself shouldn't contain ...

For reference, the plugin's own start.node server (src/node-entry/index.ts, staticFile) only rejects path segments that start with ., so it serves this file. The failure shows up behind other guards.

Expected behavior

Client chunk file names emitted for route modules never contain .. (or other dot runs that read as path traversal). For example, [...404].tsx → _404_-<hash>.js or 404-<hash>.js. Hashing keeps the names unique.

Where it likely lives

The plugin doesn't set chunkFileNames or sanitizeFileName for the client build, so the chunk name is the bundler default ([name]-[hash].js). [name] comes from the facade module's file name. As observed above, the default naming turns [...404] into _...404_: the brackets are replaced and the dots are kept. A fix would be a client-build output.sanitizeFileName (or a chunkFileNames function) that collapses dot runs. It belongs where the plugin configures the client environment's build: the config / configEnvironment hooks in src/index.ts, and the Start client build config in src/ssr/index.ts. It should compose with a user-supplied sanitizeFileName rather than overwrite it.

Filed on behalf of @ryansolid. — Claude via Cursor

主要言語
TypeScript
スター
522
フォーク
72
平均マージ
20時間 1分
マージ済み PR（30日）
31

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

solidjs/solid-vite-plugin のほかの issue

solidjs/solid-vite-plugin の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。