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
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.
The text was updated successfully, but these errors were encountered:
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.
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:
Removing (or renaming)
tailwind.config.js
allows things likeng 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.The text was updated successfully, but these errors were encountered: