vercel/ncc

Compile a Node.js project into a single file. Supports TypeScript, binary addons, dynamic requires.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 40 minutes ago
Added to GitGenius on September 6th, 2026
Created on November 13th, 2018
Open Issues & Pull Requests: 221 (+0)
GitHub issues: Enabled
Number of forks: 324
Total Stargazers: 9,838 (+0)
Total Subscribers: 101 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.6 days
Mean response time: 153.5 days
90th percentile: 667.5 days
Tracked items: 48

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 5% of issues opened in the past year have been closed. Three people close 81% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 31
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,090 days
Stale 30+ days: 30
Stale 90+ days: 28

Recent activity

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

Top labels

  • help wanted (12)
  • bug (11)
  • question (4)
  • released (4)
  • enhancement (3)
  • needs repro (1)
  • semantic-release (1)

Most active issues this week

Detailed Description

ncc is a Node.js compiler that bundles a project and its dependencies into a single executable file.

The tool solves the problem of distributing Node.js applications without requiring users to install dependencies or have Node.js available. It works by analyzing your project's dependency tree, including native binary addons and dynamically required modules, and compiling everything into one self-contained output file. This approach eliminates the need to ship node_modules directories or manage complex deployment configurations.

ncc suits projects that need to be distributed as standalone executables, such as command-line tools, GitHub Actions, or serverless functions where bundle size and startup time matter. It handles TypeScript source files automatically and preserves the ability to require modules dynamically at runtime. Teams building tools that end users will invoke directly benefit most from this approach, as it removes friction from installation and execution.

The project maintains active engagement with its codebase, regularly addressing reported issues and merging contributions that extend its capabilities. Development shows responsiveness to user needs, with fixes and enhancements flowing into releases. The maintainers demonstrate commitment to keeping the tool compatible with evolving Node.js ecosystems and handling edge cases that arise from real-world usage patterns.