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
I think it would be awesome if the project was modular and devs could pick plugins/modules that they prefer and suit their needs.
Having a standard way of plugin in some tool would relieve the project from the burden of having to choose or adopt any tech and also give the power for the dev to have all their build bundled somewhat together as dependencies.
A complex project setup could be something like a "babel preset", a bundle of multiple create-react-app plugged in one dependency.
The text was updated successfully, but these errors were encountered:
Thanks for the suggestion. If you search the issues you will find that this has been suggested multiple times.
The argument against is that we won't be able to ensure quality and hassle free setup if people can override everything. The intention of this project is to curate a stable set of tools and sane defaults, and ship them for users who don't want to spend days debugging slight configuration incompatibilities between two conflicting tools or extensions (which is what often happens with Babel or Webpack plugins).
I think it would be awesome if the project was modular and devs could pick plugins/modules that they prefer and suit their needs.
Having a standard way of plugin in some tool would relieve the project from the burden of having to choose or adopt any tech and also give the power for the dev to have all their build bundled somewhat together as dependencies.
A complex project setup could be something like a "babel preset", a bundle of multiple create-react-app plugged in one dependency.
The text was updated successfully, but these errors were encountered: