marko-js/cli

command-line tools for Marko

Hosted by OpenJS Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓

marko-js/cli has 90+ stars and 30+ forks on GitHub, is written in TypeScript, and was last pushed on Sep 11, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 6 minutes ago
Type:CLI ToolCategory(s):Frontend FrameworksWeb Development
Added to GitGenius on October 15th, 2026
Created on September 17th, 2016
Open Issues & Pull Requests: 1 (+0)
GitHub issues: Enabled
Number of forks: 36
Total Stargazers: 98 (+0)
Total Subscribers: 11 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 1256.1 days
Mean response time: 1270.1 days
90th percentile: 3036.2 days
Tracked items: 19

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

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

Top labels

  • bug (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Marko CLI is a command-line tool for scaffolding new Marko applications.

The tool solves the problem of setting up a new Marko project by providing an interactive scaffolder that prompts developers for a project name and template selection. It supports the default starter template as well as any example project from the Marko examples repository, or custom git templates specified as user/repo references. Developers can pass options as flags to skip interactive prompts, including project name, template choice, installation directory, and package manager selection.

The tool is designed for developers starting new Marko projects who want a guided setup experience. It suits teams using Marko for web applications and those who prefer either interactive prompts or scripted, non-interactive setup. The scaffolder handles non-interactive environments gracefully by detecting CI systems and AI agents, using sensible defaults rather than blocking on missing input, making it suitable for automated deployment pipelines and agent-driven development workflows.

The project is organized as a pnpm workspace written in TypeScript with separate packages for the npm create entrypoint and the core scaffolder implementation. Development uses standard tooling including TypeScript compilation, Rolldown for bundling, Vitest for testing, and Changesets for managing releases. The codebase is formatted with Prettier and includes linting checks as part of the contribution workflow.