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
{{ message }}
Repository navigation
Unable to create build after upgrading the app to react-scripts@5.0.0 #12024
I have upgraded my project from react-scripts@4.0.1 to react-scripts@5.0.0. npm start is working fine but when I am going for the build, I am getting the below error. The build is working fine when I downgraded the application to react-scripts@4.0.0
_Creating an optimized production build...
Failed to compile.
static/css/main.161533bd.css from Css Minimizer plugin
Error: Unexpected '/'. Escaping special characters with \ may help._
Did you try recovering your dependencies?
Yes, I tried recovering my dependencies with react-scripts@5.0.0, still, it is causing but working fine with react-scripts@4.0.1
npmPackages:
react: ^17.0.1 => 17.0.2
react-dom: ^17.0.1 => 17.0.2
react-scripts: 5.0.0 => 5.0.0
npmGlobalPackages:
create-react-app: Not Found
Steps to reproduce
(Write your steps here:)
There are different third-party dependencies, I have been using along with custom CSS.
The Application is working fine and the build is getting created with react-scripts@4.0.1
Looks like It is a CSSMinimizerPlugin causing the issue and in the older webpack version, the build is getting created.
Have got the issue of why it is happening after much effort, It is a comment issue (/* */) in the application, if you are facing the same issue, try to check your CSS files and see if you put any wrong comments or check the relative path for the images or background images which you might have given wrong can cause this issue. Hope it helps.
Activity
shubhdwiv12 commentedon Feb 5, 2022
Have got the issue of why it is happening after much effort, It is a comment issue (/* */) in the application, if you are facing the same issue, try to check your CSS files and see if you put any wrong comments or check the relative path for the images or background images which you might have given wrong can cause this issue. Hope it helps.
shubhdwiv12 commentedon Feb 5, 2022
I request the team to add a extra check so that such issues can be taken care of during the npm start