tighten/ziggy

Use your Laravel routes in JavaScript.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 1 hour ago
Added to GitGenius on September 16th, 2026
Created on August 2nd, 2017
Open Issues & Pull Requests: 9 (+0)
GitHub issues: Enabled
Number of forks: 273
Total Stargazers: 4,317 (+0)
Total Subscribers: 41 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.0 hours
Mean response time: 14.0 days
90th percentile: 28.0 days
Tracked items: 47

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 4
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 129 days
Stale 30+ days: 4
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

  • needs more info (3)
  • bug (1)
  • enhancement (1)
  • help wanted (1)
  • types (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Ziggy is a JavaScript library that exposes your Laravel routes to your frontend code.

The problem it solves is the friction of maintaining route definitions in two places when building Laravel applications with JavaScript frontends. Rather than hardcoding URLs or duplicating route logic in JavaScript, Ziggy generates a JavaScript representation of your Laravel routes at build time, allowing you to call routes by name with parameters just as you would in Laravel's Blade templates. This approach keeps your route definitions single-sourced in Laravel while making them available throughout your JavaScript application.

Ziggy suits Laravel projects that use JavaScript for frontend logic, whether that means Vue, React, or vanilla JavaScript. It works particularly well in monolithic Laravel applications where routes are defined in a single place and you want to avoid the maintenance burden of syncing URLs across your backend and frontend code. The library is especially valuable when your routes have parameters or when you frequently need to generate URLs dynamically in JavaScript.

The project maintains steady engagement with regular updates addressing edge cases and compatibility concerns. The maintainers respond actively to issues and pull requests, indicating ongoing investment in the tool's reliability. The codebase shows careful attention to test coverage and documentation, with examples and guides kept current. Development activity reflects a pragmatic focus on solving the specific problem of route synchronization rather than scope creep, with changes typically addressing real-world usage patterns reported by the community.