Context StencilJS lazy-loads components by injecting a <script> tag for each component bundle. When the network request for that bundle fails, the component never renders and the page shows an empty placeholder with no error surfaced inside the component's shadow DOM. Constraints and Uncertainty The framework does not provide a built-in fallback strategy such as retry, error component, or graceful degradation. No public API exists to hook into the load-failure event; the only observable signals are the global window.onerror or the script element's onerror, which are not scoped to a specific component. Bundle filenames (e.g., component-name.js) are not guaranteed stable across builds, making programmatic retry difficult. Fallback logic appears to work only in <script type="module"> contexts; legacy IE11 builds silently ignore it. Goal Determine whether a declarative fallback mechanism or configuration option can be added to Stencil's lazy-loading pipeline so that failed component loads can be recovered safely without custom workarounds. What is the recommended pattern for detecting a lazy-load failure at the component level? Can a fallback component be specified declaratively in the component's TSX or via Stencil config? Is there a stable identifier for a failed bundle that would allow a retry strategy?

StencilJS Lazy Load Failure Fallback Behavior

Lazy-Loaded Component Bundles Leave Blank Placeholders on Network Failure

0 reputation · 04 Oct 2022, 17:10 UTC

11.8K views0

Context

StencilJS lazy-loads components by injecting a <script> tag for each component bundle. When the network request for that bundle fails, the component never renders and the page shows an empty placeholder with no error surfaced inside the component's shadow DOM.

Constraints and Uncertainty

The framework does not provide a built-in fallback strategy such as retry, error component, or graceful degradation.
No public API exists to hook into the load-failure event; the only observable signals are the global window.onerror or the script element's onerror, which are not scoped to a specific component.
Bundle filenames (e.g., component-name.js) are not guaranteed stable across builds, making programmatic retry difficult.
Fallback logic appears to work only in <script type="module"> contexts; legacy IE11 builds silently ignore it.

Goal

Determine whether a declarative fallback mechanism or configuration option can be added to Stencil's lazy-loading pipeline so that failed component loads can be recovered safely without custom workarounds.

What is the recommended pattern for detecting a lazy-load failure at the component level?
Can a fallback component be specified declaratively in the component's TSX or via Stencil config?
Is there a stable identifier for a failed bundle that would allow a retry strategy?

Keep exploring this topic

Choosing Between dist and dist-custom-elements Output Targets for SSR Framework Integration

Deciding between Stencil's lazy-loaded dist output and dist-custom-elements for an SSR framework raises unresolved questions about hydration fidelity, asset paths, and duplicate custom element registration.

StencilJS production build omits lazy-loaded chunks referenced in chunk manifest

Production builds miss lazy-loaded chunks that the dev server handles, leaving the chunk manifest pointing to non-existent files. Static analysis limitations, output target mismatches, and the Vite migration all contribute.

Lazy‑Loading vs Full‑Data Loading: Which Minimizes UI Latency Under Concurrent Cell Execution?

When executing multiple cells in JetBrains DataSpell, the Data Viewer’s lazy‑loading and full‑data loading modes behave differently. Which approach offers lower UI latency, better memory usage, and smoother user experience under concurrent requests?

Preventing duplicate writes during Ballerina client retries

Exploring the best architectural pattern for implementing idempotency keys in Ballerina to prevent duplicate writes during automatic client retries.

Lazy-Loaded Component Bundles Leave Blank Placeholders on Network Failure

Context

Constraints and Uncertainty

Goal

0 answers

Your perspective belongs here.

0 question comments