Skip to content

Migrate iRacing overlay to Svelte 5 and Tailwind 4#9

Open
xikxp1 wants to merge 1 commit intomainfrom
claude/upgrade-svelte-tailwind-2uTWp
Open

Migrate iRacing overlay to Svelte 5 and Tailwind 4#9
xikxp1 wants to merge 1 commit intomainfrom
claude/upgrade-svelte-tailwind-2uTWp

Conversation

@xikxp1
Copy link
Copy Markdown
Owner

@xikxp1 xikxp1 commented Jan 16, 2026

  • Update tailwindcss from 3.4.17 to 4.1.3
  • Update daisyui from 4.12.24 to 5.0.9
  • Add @tailwindcss/vite plugin for Vite integration
  • Remove autoprefixer (no longer needed with Tailwind 4)
  • Migrate configuration from JS to CSS-based approach:
    • Delete tailwind.config.js (replaced by CSS config)
    • Delete postcss.config.js (using Vite plugin instead)
    • Update app.css with @import "tailwindcss" and @plugin "daisyui"
    • Configure custom iRacing theme via CSS variables
  • Update deprecated Tailwind classes:
    • Replace bg-opacity-X with bg-color/X syntax
    • Replace text-opacity-X with text-color/X or opacity-X

Note

Modernizes styling stack and configuration around Tailwind CSS.

  • Upgrade tailwindcss to v4 and daisyui to v5; add @tailwindcss/vite and register it in vite.config.js
  • Remove JS/PostCSS configs (tailwind.config.js, postcss.config.js) and migrate to CSS-based config in src/app.css using @import "tailwindcss", @plugin "daisyui", @theme, and CSS variables for the iracing theme
  • Update deprecated class syntax across overlays (e.g., replace text-opacity-X/bg-opacity-X with text-color/X or /X forms) in Relative.svelte, Standings.svelte, and src/routes/overlay/*/+page.svelte
  • Lockfile updates and minor transitive bumps (e.g., lightningcss)

Written by Cursor Bugbot for commit d0f7c21. This will update automatically on new commits. Configure here.

Copy link
Copy Markdown

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

This is the final PR Bugbot will review for you during this billing cycle

Your free Bugbot reviews will reset on March 2

Details

You are on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

- Update tailwindcss from 3.4.17 to 4.1.3
- Update daisyui from 4.12.24 to 5.0.9
- Add @tailwindcss/vite plugin for Vite integration
- Remove autoprefixer (no longer needed with Tailwind 4)
- Migrate configuration from JS to CSS-based approach:
  - Delete tailwind.config.js (replaced by CSS config)
  - Delete postcss.config.js (using Vite plugin instead)
  - Update app.css with @import "tailwindcss" and @plugin "daisyui"
  - Configure custom iRacing theme via CSS variables
- Update deprecated Tailwind classes:
  - Replace bg-opacity-X with bg-color/X syntax
  - Replace text-opacity-X with text-color/X or opacity-X
@xikxp1 xikxp1 force-pushed the claude/upgrade-svelte-tailwind-2uTWp branch from c7a1d9c to d0f7c21 Compare January 16, 2026 22:30
Copy link
Copy Markdown

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

@import "tailwindcss";
@plugin "daisyui" {
themes: iracing --default;
}
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing daisyUI base:false configuration option in migration

Medium Severity

The old tailwind.config.js explicitly set base: false in the daisyUI configuration to disable daisyUI's base styles. This setting was not migrated to the new CSS-based @plugin "daisyui" configuration. If daisyUI 5 still supports this option and defaults to true, the application will now receive additional base/reset styles that weren't present before, potentially causing visual regressions or style conflicts.

Fix in Cursor Fix in Web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants