vuejs/vue-router

🚦 The official router for Vue 2

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 42 minutes ago
Added to GitGenius on September 3rd, 2026
Created on December 11th, 2013
Open Issues & Pull Requests: 125 (+0)
GitHub issues: Enabled
Number of forks: 4,968
Total Stargazers: 18,870 (+0)
Total Subscribers: 489 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

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

Recent activity

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

Top labels

  • feature request (6)
  • fixed on 4.x (5)
  • discussion (4)
  • needs RFC (4)
  • has PR (2)
  • improvement (2)
  • Typescript (1)
  • contribution welcome (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Vue Router is the official router for Vue 2, providing client-side routing and navigation for single-page applications built with that framework.

The tool solves the problem of managing navigation state and URL synchronization in Vue 2 applications. It works by mapping URL paths to Vue components, handling browser history, and managing the component tree as users navigate between routes. The router integrates deeply with Vue's reactivity system to keep the UI in sync with the current route.

Developers maintaining Vue 2 applications should be aware that both Vue 2 and Vue Router 3 have reached end of life. For new projects, Vue 3 users should adopt Vue Router 4 instead. The tool remains suitable for maintaining existing Vue 2 codebases that require routing functionality, but no new feature development is expected.

Maintainers respond to issues and pull requests within a day. Activity in the issue tracker centers on feature requests, requests for RFC discussion, and general discussion rather than bug fixes, reflecting the project's mature, stable state.