apertureless/vue-chartjs

📊 Vue.js wrapper for Chart.js

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 34 minutes ago
Added to GitGenius on September 11th, 2026
Created on June 26th, 2016
Open Issues & Pull Requests: 29 (+0)
GitHub issues: Enabled
Number of forks: 805
Total Stargazers: 5,715 (+0)
Total Subscribers: 67 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.9 days
Mean response time: 28.7 days
90th percentile: 46.5 days
Tracked items: 20

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 9
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,152 days
Stale 30+ days: 8
Stale 90+ days: 6

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 (6)
  • good first issue (3)
  • Hacktoberfest (2)
  • ☂ feature-request (2)
  • ❓ question (2)
  • Need Repo (1)
  • documentation (1)
  • improvement (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Vue Chart.js is a Vue.js wrapper for Chart.js that simplifies integrating Chart.js charting capabilities into Vue applications.

The tool solves the problem of using Chart.js within Vue components by providing Vue-native wrappers around Chart.js functionality. Rather than managing Chart.js instances directly in Vue lifecycle hooks, the wrapper exposes Chart.js charts as reusable Vue components, allowing developers to declare charts declaratively using Vue's component model and pass data through props.

The project suits Vue applications that need charting functionality and want to leverage Chart.js without managing the impedance mismatch between Vue's reactive component model and Chart.js's imperative API. Developers building dashboards, analytics interfaces, or any Vue application requiring pie, doughnut, or other Chart.js-supported visualizations should consider this wrapper. The tool supports both Vue 2 and Vue 3, making it applicable across different Vue versions.

Development activity shows consistent engagement with the codebase. The project maintains active issue triage with prompt responses to user questions and bug reports. Pull requests receive timely review and feedback, indicating regular maintainer attention. The codebase receives ongoing updates to address compatibility concerns and user-reported issues. Documentation is actively maintained to reflect current usage patterns and API changes.