I've added popular Kannada songs across all mood categories. Each mood now includes iconic tracks like "Mungaru Maleye" for calm moments, "Rocking Star" for energetic vibes, "Chuttu Chuttu" for happy moods, and songs from popular films featuring artists like Sonu Nigam, Vijay Prakash, Raghu Dixit, and Armaan Malik. The Kannada songs blend seamlessly with the existing international tracks in each mood playlist.

I can see the issue - there's a CSS syntax error in the @custom-variant line. The @custom-variant syntax is incorrect for Tailwind CSS v4. Let me fix this:

I've fixed the CSS syntax error by removing the incorrect @custom-variant line that was causing the parsing issue. The dark mode styles are already properly configured through the .dark class selector and don't require the custom variant syntax in Tailwind CSS v4.

The error is related to the tw-animate-css import which has a CSS parsing issue. Let me remove that problematic import since we already have custom animations defined:

I've removed the @import "tw-animate-css"; line that was causing the CSS parsing error. The app already has custom animations defined (glow-pulse, float, rotate-slow) in the same file, so we don't need the external tw-animate-css library that was causing the syntax issue.

I found the issue! There's a duplicate styles/globals.css file that still has the problematic tw-animate-css import. Let me check and fix both files:

Found it! The styles/globals.css file has both the problematic @import 'tw-animate-css'; and the @custom-variant line. Let me fix this file and also delete it since we're using app/globals.css:

I've fixed the CSS parsing error by removing both the problematic @import 'tw-animate-css'; and the invalid @custom-variant syntax from the styles/globals.css file. These were causing the "Missing closing }" error in Tailwind CSS v4. The app now uses only the valid Tailwind import and standard CSS syntax.

I've deleted the duplicate styles/globals.css file and removed both the @import "tw-animate-css"; and @custom-variant lines from app/globals.css. These were causing the CSS parsing error. The app still has all the custom animations defined at the bottom of the file, so no visual effects are lost.