v13 - PostCSS resolving changes broke tailwind used by a lib

Current Behavior

• I have an app and a UI lib in my project.
• The UI lib has its own postcss config together with a tailwind one.
• The app consumes this UI library
• Until now, when building the app, the library’s postcss config was used and everything worked as expected
• in v13, I am required to update my app’s postcss config to include the settings I have in the UI lib

It is expected that a library will hold all its configurations and assets and they will be built with them when consumed by different apps.

Worked as expected in v12.10

Steps to Reproduce

• Create a workspace with v13 with a React app
• Add a lib with Tailwind setup (tailwind+postcss)
• Add tailwindcss/nesting to the library’s PostCSS config
• Add a component to the library with a CSS file that has nesting, e.g.:

.button {
  &.status-danger {
     @apply text-red-500;
  }
}

• Consume the component in your app - color is not applied

[jaysoo]

We have updated the logic such that the app’s tailwind config is picked up even when the libs don’t have their own config. It was done to address https://github.com/nrwl/nx/issues/7040

We can probably make this logic support picking up the lib’s config, and falling back to app if nothing is detected.

[shervElmi]

@jaysoo

Thank you for your response, It will be great.