Marko
Marko — UI framework with streaming SSR and compiled templates.
Stack Components
Why
Compiles to optimized JS, streams HTML for fast TTFB, built-in component model. 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 SSR-heavy apps needing fast first paint. Avoid for pure client-side SPAs.
How
Example
Common Problems
- ⚠Template compilation errors — check syntax in .marko files
- ⚠Hydration mismatch — ensure server/client data consistency
- ⚠Configuration drift between environments — use infrastructure-as-code (Terraform/Pulumi) to keep dev/staging/prod identical
Best Practices
- ✓Use streaming rendering for large pages
- ✓Leverage <await> for async data in templates
- ✓Set up health checks and graceful shutdown — handle SIGTERM to drain in-flight requests before exit
FAQ
What is Marko and what projects is it for?
Marko — UI framework with streaming SSR and compiled templates. 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 Marko in 10 minutes?
Two steps: (1) npm create marko@latest; (2) Write .marko templates. 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 Marko and how do I avoid it?
The most common pitfall is: Template compilation errors — check syntax in .marko files. 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 Marko?
Best practices for Marko include: Use streaming rendering for large pages; Leverage <await> for async data in templates; Set up health checks and graceful shutdown — handle SIGTERM to drain in-flight requests before exit. The first one — "Use streaming rendering for large pages" — should be set up at project init to avoid costly rework later.
When should I NOT choose Marko?
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). Marko shines for mid-to-high complexity full-stack and API work — don't over-engineer simple static pages with it.