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
`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.
`
`
at Re (F:\AngularTailwindCss\node_modules\tailwindcss\dist\lib.js:33:1716)
at getStylesConfig (F:\AngularTailwindCss\node_modules\@angular-devkit\build-angular\src\tools\webpack\configs\styles.js:106:66)
at async Promise.all (index 1)
at async generateWebpackConfig (F:\AngularTailwindCss\node_modules\@angular-devkit\build-angular\src\utils\webpack-browser-config.js:74:22)
at async generateBrowserWebpackConfigFromContext (F:\AngularTailwindCss\node_modules\@angular-devkit\build-angular\src\utils\webpack-browser-config.js:129:20)
at async initializeBrowser (F:\AngularTailwindCss\node_modules\@angular-devkit\build-angular\src\builders\karma\browser_builder.js:109:24)
Please provide the environment you discovered this bug in (run ng version)
This is expected; the webpack-based builder does not read the postcss configuration file from the workspace, only the application-builder does. Tailwind v4 support is tracked in #28938.
Which @angular/* package(s) are the source of the bug?
Don't known / other
Is this a regression?
No
Description
Just created Angular project in webstorm and followed instruction to install and configure tailwindcss for Angular
https://tailwindcss.com/docs/installation/framework-guides/angular
It works fine in development or production, but it does not work when trying to run test via ng test (Jasmine and Karma)
`
Please provide a link to a minimal reproduction of the bug
https://github.com/DSplawski-CC/AngularTailwindCss
Please provide the exception or error you saw
Please provide the environment you discovered this bug in (run
ng version
)Anything else?
No response
The text was updated successfully, but these errors were encountered: