Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Dev manifest loses lazy CSS when imported before HTTP startup

Abierto
  • ¿Algo no está bien?
#414 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@everton-dgn ya está trabajando en esto.

Desde el 14/10/2026.

  • #416 de @everton-dgn — abierto
  • #417 de @everton-dgn — abierto

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
25/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
build-system

Línea de trabajo

Start with devManifestBridgeUrl() and the code that generates virtual:solid-manifest, and find where it falls back to the JS-only manifest when the bridge URL is null. Use the reproduction in the issue: create the server with Vite's createServer(), delay server.listen() until the manifest is requested, then fetch with Accept: text/html and check whether the lazy CSS is included. Done means the manifest resolves the bridge URL lazily, so the lazy CSS appears even when the manifest loads before listening, and it handles a port change or a server closed before listening.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

With Nitro's Vite integration, the server runner can import virtual:solid-manifest before the HTTP server starts listening. devManifestBridgeUrl() returns null at that point, and the generated manifest keeps the JS-only fallback for the rest of the session.

The page renders successfully, but CSS imported by a lazy component is missing from the SSR response. The browser adds it during hydration, causing a visible layout change.

Reproduced with:

The relevant manifest code is unchanged in 3.0.0-next.50.

A small app is enough:

// src/App.tsx
import { lazy } from 'solid-js';

const Page = lazy(() => import('./Page.tsx'), undefined, 'src/Page.tsx');

export default function App() {
  return <Page />;
}

// src/Page.tsx
import './page.css';

export default function Page() {
  return <div class="bridge_probe">Nitro manifest probe</div>;
}

/* src/page.css */
.bridge_probe { font-size: 18px; }

Configure solid({ ssr: true, start: { devtools: false } }) and nitro({ serverEntry: false }).

To reproduce the startup ordering consistently, create the server through Vite's createServer() API and delay server.listen() until Nitro has requested virtual:solid-manifest. A preceding plugin's load hook can observe that request. Then start listening and fetch the page with Accept: text/html.

Actual result: HTTP 200, page content present, lazy CSS absent. Delaying the manifest load until the HTTP server is listening makes the same request include the CSS.

The bridge URL should remain usable when an external runner loads the manifest before the first request. The fix also needs to handle Vite choosing another port and closing the server before it starts listening.

Lenguaje dominante
TypeScript
Estrellas
522
Forks
73
Merge medio
1 d 5 h
PR fusionados (30 d)
34

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de solidjs/solid-vite-plugin

Todos los issues de solidjs/solid-vite-plugin

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.