dify - 💡(How to fix) Fix [Refactor/Chore] Complete Tailwind v4 CSS-first migration cleanup [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
langgenius/dify#35755Fetched 2026-05-01 05:53:16
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
1
Author
Participants
Assignees
Timeline (top)
assigned ×1connected ×1
RAW_BUFFERClick to expand / collapse

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • This is only for refactors or chores; if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交,否则会被关闭 :)
  • Please do not modify this template :) and fill in all the required fields.

Description

Scope

  • Replace dynamic Tailwind class construction with statically discoverable classes.
  • Update dify-ui docs from the removed Tailwind preset flow to CSS-first usage.
  • Clean up unused/incorrect dify-ui plugin exports and internal icon plugin wording.
  • Remove unused custom opacity utilities.
  • Move web typography plugin config next to the Tailwind plugin wrapper.
  • Migrate legacy field help tooltip usage to the accessible Infotip pattern.

Motivation

No response

Additional Context

No response

extent analysis

TL;DR

Refactor the code to replace dynamic Tailwind class construction with statically discoverable classes and update relevant documentation.

Guidance

  • Review the dify-ui documentation to ensure it reflects the changes from removed Tailwind preset flow to CSS-first usage.
  • Identify and remove unused or incorrect plugin exports and internal icon plugin wording to clean up the codebase.
  • Remove custom opacity utilities that are no longer in use.
  • Update the web typography plugin configuration to be next to the Tailwind plugin wrapper for better organization.
  • Migrate legacy field help tooltip usage to the accessible Infotip pattern for improved accessibility.

Notes

The provided issue lacks specific technical details, so the guidance is based on the general description of the intended changes.

Recommendation

Apply workaround: Refactor the code according to the described changes, as there is no clear indication of a fixed version or alternative solution.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

dify - 💡(How to fix) Fix [Refactor/Chore] Complete Tailwind v4 CSS-first migration cleanup [1 participants]