[ENG-97] Use TailwindCSS in obsidian app

[trangdoan982]

Update Obsidian app to integrate Tailwind CSS with PostCSS and Autoprefixer support

• Added Tailwind CSS, PostCSS, and Autoprefixer to package dependencies
• Configured styles.css to include Tailwind directives
• Enhanced compile script to process styles using PostCSS with Tailwind and Autoprefixer

Summary by CodeRabbit

• New Features

  • Enhanced the styling workflow by integrating modern CSS tools to deliver a more consistent and refined visual experience. The system now intelligently processes primary styles together with additional styles, ensuring a seamless design.

• Chores

  • Updated internal styling dependencies and configurations to support improved CSS processing and maintain development efficiency.

[linear]

ENG-97 Obsidian - enable tailwind css

[vercel]

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

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
discourse-graph	⬜️ Skipped (Inspect)			Apr 14, 2025 7:33pm

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

📝 Walkthrough

Walkthrough

This pull request integrates Tailwind CSS into the project by updating development dependencies, adding configuration files for PostCSS and Tailwind, and modifying the CSS compilation process. The changes include modifications to the package configuration, the creation of new configuration files, and an update to the compile script to conditionally process CSS with PostCSS when a root styles file exists.

Changes

File(s)	Summary
apps/obsidian/package.json, apps/obsidian/postcss.config.js, apps/obsidian/tailwind.config.ts	Added new devDependencies (@repo/tailwind-config, tailwindcss, postcss, and autoprefixer) and introduced configuration files for PostCSS and Tailwind CSS.
apps/obsidian/scripts/compile.ts, apps/obsidian/styles.css	Updated the compile script to check for a root styles.css and process it with PostCSS using Tailwind CSS and Autoprefixer. Also, injected Tailwind directives at the top of the stylesheet.

Sequence Diagram(s)

sequenceDiagram
    participant Compiler as Compile Script
    participant FS as File System
    participant PostCSS as PostCSS Processor

    Compiler->>FS: Check if "styles.css" exists in root
    alt File exists
        FS-->>Compiler: Return styles.css content
        Compiler->>PostCSS: Process CSS (with Tailwind CSS & Autoprefixer)
        PostCSS-->>Compiler: Return processed CSS
        Compiler->>FS: Read additional styles from directory (if any)
        Compiler-->>Compiler: Combine processed CSS with additional directory styles
    else File not found
        FS-->>Compiler: File not found
        Compiler->>FS: Read CSS directly from directory
        Compiler-->>Compiler: Combine CSS files as before
    end

Loading

Poem

I'm a little rabbit, hopping through the code,
With Tailwind and PostCSS lighting my mode.
New dependencies sprout like carrots anew,
Config files and scripts join the dance too.
I compile with whiskered joy, crisp and clear,
Bounding through changes with a happy cheer! 🐇

---

🪧 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 plan to trigger planning for file edits and PR creation.
• @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.

[trangdoan982]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (3)

apps/obsidian/tailwind.config.ts (1)

1-7: Consider expanding the Tailwind configuration.

The current configuration correctly sets up content paths, but you might want to consider adding theme customization and other Tailwind options to match your project's design system.

For example, you could expand the configuration to include theme customization:

-const config: Pick<Config, "content" | "presets"> = {
+const config: Config = {
  content: ["./src/**/*.{js,jsx,ts,tsx}"],
+  theme: {
+    extend: {
+      // Add custom colors, fonts, spacing, etc.
+      colors: {
+        // Example: Add your app's brand colors
+      },
+    },
+  },
+  plugins: [],
};

apps/obsidian/scripts/compile.ts (1)

116-150: Good implementation of conditional CSS processing.

The implementation correctly handles both cases: when a root styles.css file exists (processing it with Tailwind) and when it doesn't (falling back to the previous behavior).

A small optimization suggestion:

-              const rootStylesPath = path.join(root, "styles.css");
-              if (fs.existsSync(rootStylesPath)) {
-                const css = fs.readFileSync(rootStylesPath, "utf8");
-                const result = await postcss([
-                  tailwindcss(path.join(root, "tailwind.config.ts")),
-                  autoprefixer(),
-                ]).process(css, { from: rootStylesPath, to: outputStylesFile });
-
-                let additionalStyles = "";
-                if (fs.existsSync(stylesDir)) {
-                  const styleFiles = fs
-                    .readdirSync(stylesDir)
-                    .filter((file) => file.endsWith(".css"));
-                  additionalStyles = styleFiles
-                    .map((file) =>
-                      fs.readFileSync(path.join(stylesDir, file), "utf8"),
-                    )
-                    .join("\n");
-                }
-
-                fs.writeFileSync(
-                  outputStylesFile,
-                  result.css + "\n" + additionalStyles,
-                );
-              } else if (fs.existsSync(stylesDir)) {
-                const styleFiles = fs
-                  .readdirSync(stylesDir)
-                  .filter((file) => file.endsWith(".css"));
-                const combinedStyles = styleFiles
-                  .map((file) =>
-                    fs.readFileSync(path.join(stylesDir, file), "utf8"),
-                  )
-                  .join("\n");
-                fs.writeFileSync(outputStylesFile, combinedStyles);
-              }
+              const rootStylesPath = path.join(root, "styles.css");
+              
+              // Extract function to get additional styles to reduce duplication
+              const getAdditionalStyles = () => {
+                if (!fs.existsSync(stylesDir)) return "";
+                const styleFiles = fs
+                  .readdirSync(stylesDir)
+                  .filter((file) => file.endsWith(".css"));
+                return styleFiles
+                  .map((file) => fs.readFileSync(path.join(stylesDir, file), "utf8"))
+                  .join("\n");
+              };
+              
+              if (fs.existsSync(rootStylesPath)) {
+                const css = fs.readFileSync(rootStylesPath, "utf8");
+                const result = await postcss([
+                  tailwindcss(path.join(root, "tailwind.config.ts")),
+                  autoprefixer(),
+                ]).process(css, { from: rootStylesPath, to: outputStylesFile });
+                
+                const additionalStyles = getAdditionalStyles();
+                fs.writeFileSync(
+                  outputStylesFile,
+                  result.css + "\n" + additionalStyles,
+                );
+              } else if (fs.existsSync(stylesDir)) {
+                fs.writeFileSync(outputStylesFile, getAdditionalStyles());
+              }

apps/obsidian/package.json (1)

15-15: Consider Specifying a Version for "@repo/tailwind-config"
The new dependency "@repo/tailwind-config": "*" is added with a wildcard version. While using "*" ensures you always get the latest release, it could also introduce unexpected breaking changes due to unpinned updates. Consider specifying a fixed version or a semver range to improve stability.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between dfed0bd and f1f7b99.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (5)

• apps/obsidian/package.json (2 hunks)
• apps/obsidian/postcss.config.js (1 hunks)
• apps/obsidian/scripts/compile.ts (2 hunks)
• apps/obsidian/styles.css (1 hunks)
• apps/obsidian/tailwind.config.ts (1 hunks)

🔇 Additional comments (4)

apps/obsidian/postcss.config.js (1)

1-6: LGTM! Standard PostCSS configuration.

This configuration correctly sets up PostCSS with Tailwind CSS and Autoprefixer plugins, which is necessary for processing the CSS with Tailwind directives.

apps/obsidian/styles.css (1)

1-3: LGTM! Standard Tailwind CSS directives.

These directives are essential for including Tailwind's base styles, component classes, and utility classes in your CSS.

apps/obsidian/scripts/compile.ts (1)

7-9: LGTM! Required imports for PostCSS processing.

These imports are necessary for the PostCSS processing pipeline added to the build process.

apps/obsidian/package.json (1)

24-27: TailwindCSS and PostCSS Tooling Dependencies Added Correctly
The additions of "tailwindcss": "^3.3.0", "postcss": "^8.4.24", and "autoprefixer": "^10.4.14" in the devDependencies accurately support the integration of Tailwind CSS into the project. The inclusion of "typescript": "4.7.4" in this segment (even if repositioned) is consistent with the existing setup. Overall, these changes meet the PR objectives for modern styling capabilities.

[trangdoan982]

test:

• code:
  
• result:

[mdroidian]

🔥