You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently, the globals.css file is located in styles/globals.css, but it would be more convenient to move it to src/app/globals.css. Many developers using the T3 stack often integrate Shadcn UI, and their cli processes expect CSS files to be located under src/app. This mismatch adds friction when configuring and managing styles.
Describe the solution you'd like to see
Move globals.css from styles/globals.css to src/app/globals.css. This adjustment aligns with the expectations of Shadcn UI and makes it easier for developers using T3 stack to integrate their styles seamlessly.
Describe alternate solutions
Update the default T3 stack configuration to include the correct path for globals.css in the build pipeline or CI/CD scripts.
Additional information
This change would streamline development and configuration for the majority of developers who use both the T3 stack and Shadcn UI. It removes the extra steps of updating paths manually..
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently, the globals.css file is located in styles/globals.css, but it would be more convenient to move it to src/app/globals.css. Many developers using the T3 stack often integrate Shadcn UI, and their cli processes expect CSS files to be located under src/app. This mismatch adds friction when configuring and managing styles.
Describe the solution you'd like to see
Move globals.css from styles/globals.css to src/app/globals.css. This adjustment aligns with the expectations of Shadcn UI and makes it easier for developers using T3 stack to integrate their styles seamlessly.
Describe alternate solutions
Update the default T3 stack configuration to include the correct path for globals.css in the build pipeline or CI/CD scripts.
Additional information
This change would streamline development and configuration for the majority of developers who use both the T3 stack and Shadcn UI. It removes the extra steps of updating paths manually..
The text was updated successfully, but these errors were encountered: