browsersync/browser-sync

Keep multiple browsers & devices in sync when building websites. https://browsersync.io

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 34 minutes ago
Added to GitGenius on September 4th, 2026
Created on October 12th, 2013
Open Issues & Pull Requests: 575 (+0)
GitHub issues: Enabled
Number of forks: 750
Total Stargazers: 12,292 (+0)
Total Subscribers: 232 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 17.4 days
Mean response time: 420.8 days
90th percentile: 1950.2 days
Tracked items: 38

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 6% of issues opened in the past year have been closed. Three people close 58% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 24
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,355 days
Stale 30+ days: 22
Stale 90+ days: 21

Recent activity

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

Top labels

  • Windows (1)

Most active issues this week

Detailed Description

Browser-sync is a development tool that keeps multiple browsers and devices synchronized when building websites.

The tool solves the friction of manual browser refreshing during web development by injecting a script tag after the body element that monitors for file changes and automatically reloads or injects CSS across all connected browsers and devices. This approach works by establishing a connection between the development server and client browsers, allowing real-time synchronization of scrolling, form input, and page reloads across multiple viewing contexts simultaneously.

Developers working on responsive websites or those testing across multiple devices should consider this tool, particularly when building static sites or working in environments where a development server is already in place. The tool requires that the body tag be present in HTML for the injection mechanism to work, though custom snippet rules can be configured for alternative injection points. Teams building websites benefit most when testing across phones, tablets, and desktop browsers concurrently, as the synchronization eliminates the need to manually refresh each device.

The project maintains active community engagement through Discord for support and questions. Development activity shows ongoing maintenance with attention to the public API stability, as evidenced by careful handling of internal data structure changes across major versions while preserving backward compatibility for users who rely on documented interfaces.