Tailwind v4 and DaisyUI v5 upgrades

[scosman]

Fixes: #182

Summary by CodeRabbit

• New Features

  • Introduced a modern, customizable theme with fresh color palettes and enhanced typography for a more engaging look.

• Refactor

  • Refined visual styling by adjusting shadows, gradients, and layout spacing across various sections, ensuring a cleaner, more consistent interface.

• Chores

  • Updated underlying styling integrations and streamlined dependencies to boost performance and maintain a robust design system.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This update revises the project’s dependency and CSS configuration. In package.json, a new dependency is added while some existing ones are updated or removed. The PostCSS configuration now replaces separate plugins with a consolidated @tailwindcss/postcss entry. The main CSS file has been overhauled by replacing Tailwind directives with modular @import and @plugin statements, and it introduces a new DaisyUI theme. Additionally, several Svelte component files in both the admin and marketing routes have minor CSS class updates, and the dedicated Tailwind configuration file has been removed.

Changes

File(s)	Change Summary
package.json	Added dependency: @tailwindcss/postcss@^4.0.9; Updated dependencies: daisyui from ^4.7.3 to ^5.0.0 and tailwindcss from ^3.4.1 to ^4.0.9; Removed dependency: autoprefixer@^10.4.15
postcss.config.js	Replaced individual plugin configurations for tailwindcss and autoprefixer with a single entry for @tailwindcss/postcss
src/app.css	Restructured the CSS by removing @tailwind directives, adding an @import "tailwindcss"; statement, and introducing @plugin directives for typography and DaisyUI; added a new DaisyUI theme (saasstartertheme) and an @layer base section to support Tailwind CSS v4 requirements
src/routes/(admin)/account/(menu)/+page.svelte, src/routes/(admin)/account/(menu)/settings/**.svelte	Updated CSS classes: replaced shadow with shadow-sm in various admin Svelte components
src/routes/(marketing)/...	Multiple Svelte files in marketing routes had CSS changes including: - Gradient class replacement from bg-gradient-to-r to bg-linear-to-r - Margin and flex class updates (flex-grow to grow) - Shadow adjustments from shadow to shadow-sm - Element change from an <a> styled as a button to an actual <button> - Table header backdrop blur change from backdrop-blur to backdrop-blur-sm
tailwind.config.js	File removed; this file previously contained Tailwind CSS configuration including typography and DaisyUI plugin setups along with a custom DaisyUI theme

Poem

Hop, hop, what a change today,
Dependencies and styles in a brand new way!
From Tailwind twists to DaisyUI delight,
My code-carrot garden feels ever so bright.
Wiggling my nose, I cheer with glee—
Updates make a happy, bouncy spree!
🐇🥕

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3883159 and d48368d.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (15)

• package.json (2 hunks)
• postcss.config.js (1 hunks)
• src/app.css (1 hunks)
• src/routes/(admin)/account/(menu)/+page.svelte (3 hunks)
• src/routes/(admin)/account/(menu)/settings/change_password/+page.svelte (1 hunks)
• src/routes/(admin)/account/(menu)/settings/settings_module.svelte (1 hunks)
• src/routes/(marketing)/+layout.svelte (2 hunks)
• src/routes/(marketing)/+page.svelte (6 hunks)
• src/routes/(marketing)/blog/(posts)/how_we_built_our_41kb_saas_website/+page.svelte (1 hunks)
• src/routes/(marketing)/blog/+page.svelte (1 hunks)
• src/routes/(marketing)/contact_us/+page.svelte (2 hunks)
• src/routes/(marketing)/pricing/+page.svelte (1 hunks)
• src/routes/(marketing)/pricing/pricing_module.svelte (1 hunks)
• src/routes/(marketing)/search/+page.svelte (2 hunks)
• tailwind.config.js (0 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[cloudflare-workers-and-pages]

Deploying saasstarter with    Cloudflare Pages

Latest commit:	d48368d
Status:	✅  Deploy successful!
Preview URL:	https://d45a1614.saasstarter.pages.dev
Branch Preview URL:	https://tailwind-4-dui-5.saasstarter.pages.dev

View logs