nexts/clusterize.js

Tiny vanilla JS plugin to display large data sets easily

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 1 hour ago
Added to GitGenius on September 9th, 2026
Created on April 26th, 2015
Open Issues & Pull Requests: 56 (+0)
GitHub issues: Enabled
Number of forks: 404
Total Stargazers: 7,264 (+0)
Total Subscribers: 142 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.1 hours
Mean response time: 424.2 days
90th percentile: 848.3 days
Tracked items: 2

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 2
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,066 days
Stale 30+ days: 2
Stale 90+ days: 2

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

No issue events were indexed in the last 7 days.

Detailed Description

Clusterize.js is a lightweight JavaScript library for rendering large datasets efficiently in the browser.

The problem it solves is the performance degradation that occurs when displaying thousands of DOM elements at once. Clusterize.js uses a virtual scrolling approach, rendering only the visible portion of a dataset and dynamically updating the DOM as the user scrolls. This keeps the number of active DOM nodes minimal, dramatically improving rendering speed and memory usage even with very large lists.

The tool suits projects that need to display substantial amounts of tabular or list data without sacrificing responsiveness. It works as a vanilla JavaScript plugin with no framework dependencies, making it easy to integrate into existing projects. The small bundle size makes it practical for performance-sensitive applications where adding heavy dependencies is not feasible. Developers should choose this approach when they need straightforward virtual scrolling without the complexity of a full data grid library or framework-specific solution.

The project maintains a stable codebase with infrequent but deliberate updates. Pull requests receive careful review before merging, indicating a quality-focused approach to changes. Issue responses are thoughtful and substantive rather than perfunctory, suggesting active engagement with user needs. The maintainers prioritize backward compatibility and do not introduce breaking changes casually.