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 am considering moving react-scripts to be a 'dev-dependency' to solve a security vulnerability issue. instead of keeping it as a 'dependency' as CRA has it.
I know there are tons of threads on why CRA has chosen to specify react-scripts as a dependency but they all always just talk about the polyfills. One such issue - #2696
If I don't care about older browsers support given by the polyfills, is there any other runtime resource provided by react-scripts to warrant not moving it to be a dev-dependency?
Is polyfills the only thing given by react-scripts that is used at run-time?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I am considering moving react-scripts to be a 'dev-dependency' to solve a security vulnerability issue. instead of keeping it as a 'dependency' as CRA has it.
I know there are tons of threads on why CRA has chosen to specify react-scripts as a dependency but they all always just talk about the polyfills. One such issue - #2696
If I don't care about older browsers support given by the polyfills, is there any other runtime resource provided by react-scripts to warrant not moving it to be a dev-dependency?
Is polyfills the only thing given by react-scripts that is used at run-time?
Beta Was this translation helpful? Give feedback.
All reactions