Fix(#4): Isolate Marquee component styles using CSS Modules to prevent global conflicts

[anonymousRecords]

I recently needed to implement a marquee and came across your library. 
It was incredibly easy to use, and I really appreciated how simple it made the process—thank you! 
However, I also encountered the same issue described in #4, which led me to create this PR. 
I’d appreciate any feedback you may have.

Related Issue

close #4

Summary of Changes

• All styles for the Marquee component are now scoped using CSS Modules (src/Marquee.module.css). This ensures that class names are locally scoped during build time, preventing global style conflicts.
• Removed global.css and utilities.css, which previously introduced global styles. All necessary styles are now encapsulated within Marquee.module.css using Tailwind’s @apply directive or custom declarations.

Before & After Comparison

Before:
Importing Marquee CSS brought in global Tailwind styles (@tailwind base/components/utilities), which caused layout and style conflicts across unrelated components.

After:
All Marquee styles are fully scoped and isolated. Users simply import the provided JavaScript and CSS files without affecting other parts of their application.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
marquee	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 27, 2025 2:13am