emmetio/emmet

The essential toolkit for web-developers

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 1 hour ago
Added to GitGenius on September 15th, 2026
Created on February 15th, 2010
Open Issues & Pull Requests: 87 (+0)
GitHub issues: Enabled
Number of forks: 511
Total Stargazers: 4,539 (+0)
Total Subscribers: 150 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 17.5 hours
Mean response time: 155.7 days
90th percentile: 1061.3 days
Tracked items: 19

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 14
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 757 days
Stale 30+ days: 14
Stale 90+ days: 14

Recent activity

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

Top labels

  • ya-osn (8)
  • Enhancement (2)
  • Editor-specific (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Emmet is a web-developer toolkit for expanding abbreviations into HTML, CSS, and other code fragments.

Emmet solves the problem of writing repetitive markup and stylesheet code by allowing developers to type CSS-selector-like abbreviations that expand into complete code structures. The approach parses abbreviations dynamically as they are typed, interpreting familiar syntax for element nesting, attributes, classes, and IDs without requiring predefined snippets. For stylesheets, it offers special syntax for CSS properties with embedded values, such as converting `bd1-s#f.5` into `border: 1px solid rgba(255, 255, 255, 0.5)`. The toolkit includes an extraction function to identify abbreviations within source code, enabling editor integration workflows.

Developers should choose Emmet if they work frequently with HTML, CSS, or related templating languages and want to reduce typing overhead. The tool suits projects using popular syntaxes including HAML, Pug, JSX, SCSS, and SASS. This repository contains only the core parsing and expansion module; editor plugins are maintained separately. The monorepo structure allows the parsing modules in the packages folder to be used independently for other purposes like syntax highlighting.

The project maintains active development with regular commits across the codebase. The maintainers respond to issues and pull requests, indicating ongoing engagement with the user community. The codebase is organized as a monorepo with clear separation between the core expansion logic and reusable parsing modules, suggesting deliberate architectural choices for modularity and extensibility.