Webpack builder not using postcss config file in workspace

[Eirmas]

Command

build

Is this a regression?

• Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was

No response

Description

Currently it's not possible to upgrade to Tailwind v4 with the Storybook webpack builder because the automatic tailwind configuration is looking for the wrong package.
In other builders, this is not a problem because adding a postcss config file to override the automatic import works fine.

It would be nice if the webpack builder could look for a postcss configuration file to use, or if it would import the correct tailwind postcss package based on the tailwind version.

Linked issue: #28938

Minimal Reproduction

• Create a angular storybook project using webpack
• Add Tailwind v4

Your Environment

Latest version of angular

Anything else relevant?

No response

[JoostK]

with the Storybook webpack builder

What is this referring to?

Create a angular storybook project using webpack

Could you please elaborate on what this actually means? This is not a concrete instruction to execute, so it's unclear what this means.

[JeanMeche]

AFAIK this issue is that postcssrc.json config file is only read by the application builder. See #28938 and particularly #28938 (comment)

[clydin]

As mentioned above, custom postcss configuration file usage requires the use of the application build system. Please consider migrating to take advantage of this and a variety of other features.

For updates on integrated Tailwind v4 support, please subscribe to #28938

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}