Desktop app Tailwind 4 #1438
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| @@ -1 +1,8 @@ | ||||||||||||||||||||||||||||
| // module.exports = require("@cap/ui/postcss"); | ||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||
| module.exports = { | ||||||||||||||||||||||||||||
| plugins: { | ||||||||||||||||||||||||||||
| "@tailwindcss/postcss": {}, | ||||||||||||||||||||||||||||
| autoprefixer: {}, | ||||||||||||||||||||||||||||
| }, | ||||||||||||||||||||||||||||
| }; | ||||||||||||||||||||||||||||
|
Comment on lines
+1
to
+8
Contributor
There was a problem hiding this comment. 🧩 Analysis chain🏁 Script executed: fd -type f -name "postcss.config.*"Repository: CapSoftware/Cap Length of output: 174 🏁 Script executed: find . -type f -name "*postcss*" | grep -E "\.(ts|js|cjs|mjs)$" | head -20Repository: CapSoftware/Cap Length of output: 174 🏁 Script executed: find . -path "*/cap/ui/*" -type f | grep -iE "(postcss|index)" | head -20Repository: CapSoftware/Cap Length of output: 174 🏁 Script executed: rg -t js -t ts "@cap/ui/postcss" --max-count 20Repository: CapSoftware/Cap Length of output: 174 🌐 Web query:
💡 Result: Short answer: Yes — in Tailwind CSS v4 the new @tailwindcss/postcss plugin + Lightning CSS make separate autoprefixer (and postcss-import / postcss-preset-env) generally redundant. What changed
What to do
Sources: Tailwind v4 docs and migration guidance. [1] [2] [3] Remove JS comment and redundant Two things to fix here:
Corrected config: -// module.exports = require("@cap/ui/postcss");
-
module.exports = {
plugins: {
"@tailwindcss/postcss": {},
- autoprefixer: {},
},
};📝 Committable suggestion
Suggested change
🤖 Prompt for AI Agents |
||||||||||||||||||||||||||||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🌐 Web query:
@tauri-apps/cli 2.9.5 release notes changelog💡 Result:
Here are the release notes / changelog entries for @tauri-apps/cli v2.9.5:
Bug fixes:
Performance improvements:
Dependencies:
Sources: [1] Tauri release page for @tauri-apps/cli v2.9.5, [2] tauri-apps/tauri GitHub release (tauri-cli v2.9.5).
🌐 Web query:
@tauri-apps/cli 2.9.5 @tauri-apps/api 2.5.0 compatibility💡 Result:
Short answer: not recommended — upgrade @tauri-apps/api to a 2.9.x release to match @tauri-apps/cli 2.9.5.
Why: the Tauri ecosystem expects matching/close releases across packages (tauri, @tauri-apps/api, tauri-cli/@tauri-apps/cli). @tauri-apps/cli 2.9.5 is part of the 2.9.x ecosystem; @tauri-apps/api 2.5.0 is an older 2.5.x release and may miss APIs/behavior introduced since 2.5.0. For best compatibility, use @tauri-apps/api 2.9.x with @tauri-apps/cli 2.9.5. [1][2]
Sources:
References:
[1] Tauri Core Ecosystem Releases (shows tauri/@tauri-apps/api and cli 2.9.x alignment).
[2] @tauri-apps/api v2.5.0 release page.
Upgrade @tauri-apps/api to 2.9.x for compatibility with @tauri-apps/cli 2.9.5.
The version constraint for @tauri-apps/cli was updated to
^2.9.5, but @tauri-apps/api is pinned at 2.5.0. The Tauri ecosystem requires matching or close release versions across packages; using cli 2.9.5 with api 2.5.0 creates a significant version mismatch (4 minor versions apart). This can result in missing APIs or behavioral inconsistencies. Upgrade @tauri-apps/api to a 2.9.x release to ensure ecosystem alignment.🤖 Prompt for AI Agents