marko-js/run

The Marko application framework

Hosted by OpenJS Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓

marko-js/run has 150+ stars and 10+ forks on GitHub, is written in TypeScript, and was last pushed on Oct 16, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 6 minutes ago
Added to GitGenius on October 15th, 2026
Created on November 4th, 2022
Open Issues & Pull Requests: 34 (+0)
GitHub issues: Enabled
Number of forks: 17
Total Stargazers: 175 (+0)
Total Subscribers: 6 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 10.4 hours
Mean response time: 50.7 days
90th percentile: 87.1 days
Tracked items: 15

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 15
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 347 days
Stale 30+ days: 12
Stale 90+ days: 12

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Marko Run is an application framework that provides a zero-configuration way to build full-stack web applications using the Marko templating language.

The framework solves the problem of reducing setup complexity for Marko applications by providing sensible defaults and convention-based routing. It uses a file-based routing system where files prefixed with `+` in a routes directory automatically become pages, layouts, or request handlers. Pages use Marko components for server-side rendering with automatic streaming and partial hydration. Layouts wrap nested pages and receive request context as input. Handlers are TypeScript or JavaScript files that export HTTP verb functions for API routes. The tool ships with a default Vite configuration and Node-based adapter, eliminating the need for manual build setup.

Marko Run suits developers building full-stack applications who want minimal configuration overhead and prefer convention over configuration. The framework scales from simple single-page projects to production applications with multiple deployment targets. It is particularly well-suited for projects where server-side rendering, streaming responses, and automatic code splitting are valuable. The tool is currently in beta, which means it is still stabilizing and developers should be prepared for potential breaking changes or missing features.

The project maintains active development with regular updates to its core functionality. The codebase is written in TypeScript, providing type safety and editor support throughout the framework. Development activity shows ongoing refinement of the routing system, handler validation, and deployment adapters. The team continues to expand platform support beyond the default Node adapter, working toward the stated goal of running anywhere through web standards alignment.