Skip to content

A beautiful marquee component for React.

active 2024-01-152026-01-23 (UTC)

Complete coverage26,403 / 26,403 hourly files (100%) · 2 absent upstream2023-08-152026-08-19 (UTC)
Events
529
Pushes
14
Pull requests
12
Issues
9
Stars
450
Forks
19

Activity over time

Daily event counts in the loaded window

Line chart, 740 days from 2024-01-15 to 2026-01-23. Pushes: 14 total, peak 5 in a day. Pull requests: 12 total, peak 3 in a day. Issues: 9 total, peak 2 in a day. Comments: 22 total, peak 3 in a day. Stars: 450 total, peak 102 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

Recent activity

Latest issues, pull requests and releases

  • Issue comment#5elonpart22025-07-31 14:04
    Dynamic speed
  • Issue#16rabbitmouse2025-06-10 02:30
    In mobile Safari. When the first element reaches the left side, Marquee flicker occurs
  • Issue comment#4injae-kim2025-05-28 13:10
    styling is affected of components that don't use the marquee when importing
  • Issue comment#15vercel[bot]2025-05-26 16:39
    Fix(#4): Isolate Marquee component styles using CSS Modules to prevent global conflicts
  • Issue comment#14Ashish-simpleCoder2025-04-27 04:31
    any plan for react 19?
  • Issue comment#4Ashish-simpleCoder2025-04-27 04:29
    styling is affected of components that don't use the marquee when importing
  • Issue#14pangjianxin2025-03-27 01:17
    any plan for react 19?
  • Issue comment#7zacBkh2025-02-02 08:19
    Unhandled Runtime Error - Nextjs
  • Issue comment#13vercel[bot]2025-01-24 20:29
    chore: update Shiki Code Block react
  • Pull request#12selemondev2025-01-24 20:23
  • Issue comment#12vercel[bot]2025-01-24 08:45
    chore: update Shiki Code Block React
  • Pull request#12selemondev2025-01-24 08:45
  • Pull request#11devnomic2025-01-23 06:23
  • Issue comment#11vercel[bot]2025-01-21 12:17
    docs: use Shiki code block
  • Pull request#11selemondev2025-01-21 12:17
  • Pull request#10selemondev2025-01-21 12:11
  • Issue comment#10vercel[bot]2025-01-21 12:05
    docs: use Shiki code block
  • Pull request#10selemondev2025-01-21 12:05
  • Issue#7devnomic2025-01-15 11:17
    Unhandled Runtime Error - Nextjs
  • Pull request#9devnomic2025-01-15 11:17
  • Issue comment#9vercel[bot]2025-01-15 07:27
    chore: update .gitignore to exclude new files
  • Pull request#9selemondev2025-01-15 07:27
  • Issue comment#8vercel[bot]2025-01-15 07:21
    fix: unhandled runtime error
  • Pull request#8selemondev2025-01-15 07:21
  • Issue comment#7alexander-densley2025-01-06 18:27
    Unhandled Runtime Error - Nextjs

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 450 stars here means stars gained during the window, not the repo's star count.