StencilJS Component Bundle Interaction with Node/Express Server During Deployment

Direct answer

A Node/Express stack trace points to a server-side module or file problem, not a Stencil component runtime failure. Express only serves the files Stencil emits; it does not execute the client bundle.

Missing module or polyfill failures

• Missing Node module: Cannot find module '<pkg>', MODULE_NOT_FOUND, or Require stack: in the Node process.
• Missing emitted asset: ENOENT on the server, or HTTP 404 for /build/... from express.static.
• Polyfill failures: browser console or Network tab errors only. They do not produce Node stack frames.

Service worker registration

Stencil does not register a service worker automatically by default. Enable it explicitly in the www output target, for example serviceWorker: true, or add manual registration code. Verify that the emitted directory contains a service-worker file and that generated HTML includes the registration snippet.

Confirming CSS extraction

Do not diagnose from the generic "Failed to load component stylesheet" message alone. Open the browser Network tab, find the exact stylesheet URL in the generated HTML, and confirm that file exists under the Express static root. A 404 usually means a static-root or base-URL mismatch; a 200 with the wrong MIME type means the server is not serving it as CSS.

Verification steps for this deployment

1. Run a clean build: npx stencil build.
2. Serve the emitted directory, typically www, with Express:

app.use(express.static(path.join(__dirname, 'www')));

1. Inspect stencil.config.ts for the www output target and check whether serviceWorker is set.
2. List emitted assets to confirm the file is on disk: ls www/build.
3. Reload the page, open DevTools Network, filter by JS/CSS, and record the exact failing URL, HTTP status, and MIME type.
4. Compare that URL against the files present under the Express static root.

Assumptions and uncertainty

• This assumes a standard Stencil www output target served as static files. If you use SSR, hydrate, or prerender, separate that Node runtime from the static bundle; SSR errors appear in the Node process, while component-load errors appear in the browser.
• Config option names and emitted filenames are version-sensitive. Verify them against your installed Stencil version before changing configuration.
• Enabling a service worker can cache stale bundles and hide 404s until the old worker is unregistered or updated.

One missing diagnostic detail changes the recommendation: the exact failing URL and HTTP status from the browser Network tab or Express access log. Without it, I cannot tell whether the problem is a missing static root, a base-URL mismatch, or a lazy-load path mismatch.