Skip to content

feat(v4): support CSS directives#82

Merged
colinaaa merged 2 commits intorstackjs:v4from
colinaaa:colin/0227/directives
Feb 27, 2026
Merged

feat(v4): support CSS directives#82
colinaaa merged 2 commits intorstackjs:v4from
colinaaa:colin/0227/directives

Conversation

@colinaaa
Copy link
Collaborator

Summary

Support using directives like @apply, @custom-variant, @variant and @utility in regular .css files.

@chatgpt-codex-connector
Copy link

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@gemini-code-assist
Copy link

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces support for various Tailwind CSS v4 directives like @apply, @custom-variant, @variant, and @Utility within regular CSS files. This is achieved by integrating the official @tailwindcss/postcss plugin into the Rsbuild PostCSS pipeline, enhancing the plugin's capabilities for modern Tailwind CSS usage.

Highlights

  • CSS Directives Support: Enabled the use of Tailwind CSS v4 directives such as @apply, @custom-variant, @variant, and @Utility directly in .css files.
  • PostCSS Plugin Integration: Integrated the @tailwindcss/postcss plugin into the Rsbuild PostCSS pipeline to automatically process these new CSS directives.
  • Improved Theme Resolution: Enhanced the theme path resolution logic to correctly handle relative paths for Tailwind CSS themes.
  • Comprehensive Test Coverage: Added new test cases and example files to validate the functionality of the newly supported CSS directives.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • README.md
    • Added a new section detailing the automatic support for CSS directives like @apply and @plugin.
    • Included a CSS code example demonstrating @apply usage.
  • package.json
    • Moved @tailwindcss/postcss from devDependencies to dependencies.
    • Added postcss as a devDependency.
  • pnpm-lock.yaml
    • Updated the lockfile to reflect the changes in package.json, specifically moving @tailwindcss/postcss and adding postcss.
  • src/index.ts
    • Imported tailwindPostCSSPlugins from the new postcss.ts file.
    • Modified the theme option resolution to ensure it's an absolute path.
    • Integrated the tailwindPostCSSPlugins into the Rsbuild PostCSS configuration, ensuring they run before other PostCSS plugins.
  • src/postcss.ts
    • Added a new file defining injectTailwindThemePlugin and tailwindPostCSSPlugins.
    • Defined injectTailwindThemePlugin as a PostCSS plugin that prepends an @import rule for the Tailwind theme.
    • Exported tailwindPostCSSPlugins as an array containing injectTailwindThemePlugin and the main @tailwindcss/postcss plugin.
  • test/css-directives/index.test.ts
    • Added a new test file to verify the correct application of @apply, @Utility, @custom-variant, and @variant directives using Playwright.
  • test/css-directives/src/app.css
    • Added a new CSS file containing examples of @custom-variant, @Utility, @apply, and @variant usage for testing.
  • test/css-directives/src/index.js
    • Added a new JavaScript file to create HTML elements and apply classes for testing the CSS directives.
  • test/functions/config/functions-theme.css
    • Removed the layer(theme) from the @import statement for tailwindcss/theme.
    • Removed the @layer components block, which was moved to a separate file.
  • test/functions/src/components.css
    • Added a new CSS file containing the @layer components block previously found in functions-theme.css.
  • test/functions/src/index.js
    • Added an import statement for the new components.css file.
Activity
  • No human activity has been recorded for this pull request yet.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request adds support for using Tailwind CSS directives like @apply in regular CSS files by integrating @tailwindcss/postcss. However, a CSS injection vulnerability was identified in src/postcss.ts where the theme option is not properly escaped when injected into an @import rule, potentially allowing arbitrary CSS injection. Additionally, I've found a potential runtime error in the new PostCSS plugin and a minor inconsistency in the README documentation.

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
@colinaaa colinaaa merged commit 80cb611 into rstackjs:v4 Feb 27, 2026
2 checks passed
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.

1 participant