-
-
Notifications
You must be signed in to change notification settings - Fork 26.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plugin modules #145
Comments
Not currently. Please see #99 (comment). |
That would be the beauty of using a plugin module (not a Webpack plugin). Usage would be:
If a better build tool emerges, release a new major version of everything and the user is none-the-wiser to what's happening behind the scenes. |
We don’t want to get into a situation where people created 100 addons for create-react-app using webpack, we switch away from webpack, and 100 addons need to be rewritten. |
Another problem with this is that people will want to install 10 different plugins, and Also, how would |
I think there's a decent way to do this without any explicit support in |
Inb4 somebody makes |
👍 I think this is what we’ll be recommending for SASS users. |
Fixed VSCode warning for tslint trailing-comma
Plugin modules would be one way to allow people to tweak for their preferred workflow (having just read the Sass issue #78) while keeping config out of the user's hands. This would also make it easier to port to something else if you ever move away from Webpack.
e.g. here's the complete Sass plugin for nwb - all it does is provide the config and dependencies required to add a new Webpack loader, with a
package.json
scan fornwb-*
modules in nwb itself.Is there a particular way of implementing plugins which could be supported in create-react-app?
The text was updated successfully, but these errors were encountered: