[Proposal] : Ability to load PostCSS config file from project root directory if exists

[pavinthan]

Ability to load PostCSS config file from project root directory if exists

I believe create react app help to build awesome web pages and applications by the way developer face a lot of issues with styling their pages or applications now days more of PostCSS plugins reduce that workflows

eg:

1. stylelint
2. Tailwind CSS
3. PostCSS Assets

if create react app load PostCSS config file from project root directory if exists that will allow developers to configure their own configurations to build their awesome web pages and applications.

This is most useful for who like to run yarn eject but fingers is not allow it.

[ratheeps]

@pavinthan This seems like a pretty good idea. for using PostCSS plugins, I'm also facing those issues.

[pavinthan]

thanks @ratheeps,

It's good to have postcss.config.js configurable, @iansu or any core team members could you please add your review about this ?

[KogulVimal]

@pavinthan, It's a good way dude. I hope it'll be more useful.

[iansu]

Adding a config file for PostCSS or any other tool (Babel, webpack, etc.) is not in line with this project's goals. We do allow PostCSS to be adjusted via the browserslist in package.json but we're not planning to allow configuration beyond that at this time.

[pavinthan]

@iansu if we need to add any PostCSS plugins do we need to eject react-script?

[iansu]

Yes, that would be the case. That's also the case for Babel and webpack. The reason being we want to keep things simple for users and we only have the resources to support our primary config. If you start adding plugins there are suddenly a huge number of possible configurations and we don't have the bandwidth to support that.

We will be adding support for custom templates (as well as the existing support for custom scripts) so someone could always create a PostCSS template to use with Create React App in the future.