Skip to content

Tests fail when tailwind.config.js is present #21

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
EdKaim opened this issue Feb 9, 2025 · 1 comment
Closed

Tests fail when tailwind.config.js is present #21

EdKaim opened this issue Feb 9, 2025 · 1 comment
Assignees

Comments

@EdKaim
Copy link
Member

EdKaim commented Feb 9, 2025

During the Tailwind v4 migration it was discovered that the current state of the platform fails to test if tailwind.config.js is present.

The error you get is:

An unhandled exception occurred: It looks like you're trying to use `tailwindcss` directly as a PostCSS plugin. The PostCSS plugin has moved to a separate package, so to continue using Tailwind CSS with PostCSS you'll need to install `@tailwindcss/postcss` and update your PostCSS configuration.

Removing (or renaming) tailwind.config.js allows things like ng test to run as intended but breaks other builds. It does not appear that there is a clean workaround at the moment, so we're going to disable the test step of CI/CD temporarily. Once the underlying issue is resolve we will re-enable CI/CD testing.

EdKaim added a commit that referenced this issue Feb 9, 2025
@EdKaim EdKaim self-assigned this Feb 12, 2025
@EdKaim
Copy link
Member Author

EdKaim commented May 18, 2025

This was ultimately worked around by just renaming the tailwind.config.js file to tailwind.config.lightnap.js and updating the reference from styles.css. As long as there isn't a file named tailwind.config.js (even if it's empty) the Angular/Karma testing works fine.

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

No branches or pull requests

1 participant