Repository navigation
Add ability to configure Webpack plugins without eject #1592
Description
I am missing 2 things that I like in my project and I don't want to eject.
- Eslint Auto fix
- StyleLint
adding them can be done with a simple configuration in webpack.
plugins: [
new StyleLintPlugin(),
new webpack.LoaderOptionsPlugin({
options: {
eslint: { fix: true },
},
}),
]
can we add plugins to webpack without eject?
Activity
viankakrisna commentedon Feb 20, 2017
@shai32 No. There's been a lot of discussion regarding this, we don't currently expose webpack config to user, if you don't want to eject, you can maintain a fork https://medium.com/@shubheksha/tweaking-configuration-for-react-scripts-in-create-react-app-d91e9d03a42f#.wrtg9nbb1. This decision is made so we can transparently move to other module bundler without affecting external api. If you try other hacks to configure cra's webpack config, it's not guaranteed that the hack will work when react-scripts update.
I think if you are comfortable with webpack you can just fork or eject :)
shai32 commentedon Feb 20, 2017
Ok, I agree with this approach.
gaearon commentedon Feb 20, 2017
Also feel free to search issues before creating a new one 😉
#99 #145 #460 #481 #1060 #1103 #1111 #1308
gaearon commentedon Feb 20, 2017
Autofix has known problems with eslint-loader, sometimes entering infinite cycles. I would not recommend using it in this setup. It also wouldn't be very useful because our lint rules intentionally don't include any style rules. For enforcing style, I recommend you to try Prettier which works fine without ejecting.
You can express support for it in this PR: #1216.