Stencil SPA

Stencil for framework-agnostic web components.

FrontendModerate

Stack Components

FrameworkStencil 4

BuildStencil compiler

StateStencil store

StylingCSS vars

Why

Compiles to standard custom elements, works with any framework. JavaScript is used by 62% of developers per the Stack Overflow 2024 survey, and React holds 40% framework market share (State of JS 2024).

Vite replaced Webpack as the default bundler, cutting dev server startup from 30s to <1s.

When

Use for cross-framework design systems. Avoid for single-framework apps.

How

1. npm init stencil myapp 2. Define components with @Component 3. stencil build 5. Add environment configuration — cp .env.example .env && edit values 6. Run tests — npm test or pnpm test to verify setup 7. Deploy — git push to trigger CI/CD or manual deploy

Example

@Component({ tag: 'my-counter' }) export class Counter { count = 0; render() { return <button onClick={() => this.count++}>{this.count}</button> } }

Common Problems

⚠SSR hydration — Stencil has experimental SSR
⚠Event naming — use CustomEvent with detail
⚠Configuration drift between environments — use infrastructure-as-code (Terraform/Pulumi) to keep dev/staging/prod identical

Best Practices

✓Use decorators for props and state
✓Enable dist-custom-elements for bundle size
✓Set up health checks and graceful shutdown — handle SIGTERM to drain in-flight requests before exit

FAQ

What is Stencil SPA and what projects is it for?

Stencil for framework-agnostic web components. It pairs layered technologies for end-to-end type safety and out-of-the-box deploys, fitting everything from MVPs to production SaaS.

How do I spin up a working demo with Stencil SPA in 10 minutes?

Two steps: (1) npm init stencil myapp; (2) Define components with @Component. Get the local dev server running, then wire one real data source to verify the end-to-end loop.

What is the most common pitfall with Stencil SPA and how do I avoid it?

The most common pitfall is: SSR hydration — Stencil has experimental SSR. Avoid it by adding the matching checklist to your PR template and running type-check + lint + unit tests in CI — three gates before merge.

What are the best practices for Stencil SPA?

Best practices for Stencil SPA include: Use decorators for props and state; Enable dist-custom-elements for bundle size; Set up health checks and graceful shutdown — handle SIGTERM to drain in-flight requests before exit. The first one — "Use decorators for props and state" — should be set up at project init to avoid costly rework later.

When should I NOT choose Stencil SPA?

Pick something else in three cases: (1) the team has zero experience with the core framework and the deadline is tight (learning-curve risk); (2) it's a pure content/marketing site (Astro is lighter); (3) you need very high throughput (>10k RPS) or strict-consistency microservices (Go/Rust). Stencil SPA shines for mid-to-high complexity full-stack and API work — don't over-engineer simple static pages with it.