Replies: 2 comments 5 replies
-
Hi @VeroPap! Tailwind only scans the current working directory (cwd) and its subdirectories. In this case, your cwd is apps/console/, and the CSS file itself (
|
Beta Was this translation helpful? Give feedback.
5 replies
-
removed second style.css file |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone, I'm encountering an issue while upgrading Tailwind CSS from version 3 to 4 in my monorepo project.
Project structure
Here’s an overview of my monorepo structure:
In the root tailwind.config.js file, I’m exporting the centralized configuration like this:
module.exports = require("./packages/tailwind-config/tailwind.config.cjs");
Additionally, the various global.css files import the centralized styles like this:
@import "@rc/tailwind-config/styles.css";
Issue encountered
When I try to upgrade Tailwind to version 4 in the apps/console directory, I get the following error:
It looks like Tailwind cannot find the CSS file because it is located in packages/tailwind-config instead of inside apps/console.
For simplicity, I only mentioned console, but I actually have multiple similar directories inside apps/.
Question
Is there a proper way to upgrade Tailwind to v4 while keeping this structure? Has anyone encountered a similar issue in a monorepo?
Thanks in advance for your help! 😊
Beta Was this translation helpful? Give feedback.
All reactions