postcss-loader error after update with @apply for tailwind custom class in storybook

[Yimiprod]

After upgrading postcss-loader to latest version i get this error on build for storybook:

Theses classes are defined with the config of tailwind via theme:

const config = {
  theme: {
    colors: {
      current: 'currentColor',
      transparent: 'transparent',
      inherit: 'inherit',

      lightSand: 'hsl(var(--color-lightSand) / <alpha-value>)',
      saffron: 'hsl(var(--color-saffron) / <alpha-value>)',

      /* LAYOUT */
      pearl: 'hsl(var(--color-pearl) / <alpha-value>)',
    },
  },
};

any idea why they are not detected as "injected" ?
Tailwind seem to not have any problem when used in nextjs and its only in storybook that this problem appear.

Here is the main.ts used by storybook:

import type { StorybookConfig } from '@storybook/react-webpack5';

const config: StorybookConfig = {
  framework: {
    name: '@storybook/react-webpack5',
    options: {},
  },
  stories: ['../doc/**/*.stories.mdx', '../lib/**/*.stories.@(mdx|tsx)'],
  addons: [
    '@storybook/addon-a11y',
    '@storybook/addon-links',
    '@storybook/addon-essentials',
    '@whitespace/storybook-addon-html',
    '@storybook/addon-themes',
    {
      name: '@storybook/addon-styling-webpack',

      options: {
        rules: [
          {
            test: /\.css$/,
            sideEffects: true,
            use: [
              'style-loader',
              {
                loader: 'css-loader',
                options: { importLoaders: 1 },
              },
              {
                loader: 'postcss-loader',
                options: { implementation: require.resolve('postcss') },
              },
            ],
          },
        ],
      },
    },
  ],
  typescript: {
    reactDocgen: 'react-docgen-typescript',
  },
  docs: {
    autodocs: true,
  },
};

export default config;

[alexander-akait]

Hello, still valid?

[Yimiprod]

still yes

[alexander-akait]

@Yimiprod can you put your code in the test repo and provide the link with small description about your problem, thank you

[Yimiprod]

Closing: I can no longer reproduce the error. it fixed by itself through a lot of updates of various modules.