marko-js/tags

Not quite core components.

Hosted by OpenJS Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓

marko-js/tags has 20+ stars and 10+ forks on GitHub, is written in JavaScript, and was last pushed on Nov 11, 2025. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 14 minutes ago
Added to GitGenius on October 15th, 2026
Created on August 18th, 2018
Open Issues & Pull Requests: 25 (+0)
GitHub issues: Enabled
Number of forks: 10
Total Stargazers: 22 (+0)
Total Subscribers: 2 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 47.7 hours
Mean response time: 44.4 days
90th percentile: 86.8 days
Tracked items: 2

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

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Tags is a monorepo collection of utility components for the Marko templating framework that are not part of core but enhance the ecosystem.

The project addresses common patterns in Marko applications by providing reusable component utilities. It includes context for sharing data through component hierarchies, match-media for applying media queries within templates, portal for rendering content to different DOM locations, subscribe for declarative event handling, and destroy-when-detached for automatic cleanup of components when their containers are removed. Each utility solves a specific templating or component lifecycle problem without requiring custom implementation.

Developers working with Marko who need these particular patterns should consider adopting individual packages from the collection. The utilities suit projects that require data sharing across deeply nested components, responsive template behavior, DOM portals, or careful resource cleanup. The monorepo structure allows teams to adopt only the packages they need rather than taking a dependency on the entire collection.

The project maintains a consistent build and test environment across all packages with automated formatting on commits. Test coverage is tracked and reported, and the repository uses continuous integration to validate changes across the suite.