Hi,
I have a React app. If I want to build this I get an error
Failed to compile.
./node_modules/@progress/kendo-theme-default/dist/all.css
ParserError: Expected closing parenthesis at line: 1, column 5
however, when i check all.css it looks ok.
how can i fix this?
Thank You, Jens
2 Answers, 1 is accepted
Hello, Jens,
We noticed that the same error message can occur if the react-scripts package is using version 3*:
https://www.npmjs.com/package/react-scripts
Another option is to try updating the @progress/kendo-theme-default package to the latest version as well, as we only had these reports for the previous version.
I can suggest firstly updating the theme version and if the issue still occurs to update the react-scripts package as well.
Regards,
Stefan
Progress Telerik
Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.
Rank 1
Iron
C:\c_backup\MYSTUF\Thinira\Thinira\goldagenda\goldAgendReact\source_code\node_modules\@progress\kendo-theme-default\dist\all.scss
comment this line
Rank 1
Hi there !
We were getting the same error, tried updating react-scripts and @progress/default (5.2.0) but no luck. We commented out this line (THANKS STEPHEN!!) and it built successfully.
We don't want to deploy like this - is there a solution or explanation of how to fix this?
Hello,
We have made different tests and in them, the error disappeared after updating the react-scripts version to 4+. Still, we are maybe missing some important details based on which the error still occurs after an update.
If anyone can share an example where the error still occurs after the update we will be very grateful and we will investigate what could be causing it and provide a fix.
Rank 1
are there any updates on this?
We were getting the same error, tried updating react-scripts and @progress/default (5.2.0) but no luck. We commented out this line (THANKS STEPHEN!!) and it built successfully.
We don't want to deploy like this - is there a solution or explanation of how to fix this?
Because I don't want to deploy like that
or else I would have to stop ignoring my node_modules which is very huge
Hello,
Is it possible to provide an example where this error is reproduced after the update so that we can inspect it further and find a solution?
Regards,
Filip
Rank 1
hi,
i also get error :
Do you have any solution for this?
Hi, Raffi,
I can recommend deleting the node_modules and then doing a clean npm install.
Regards,
Filip
Hello,
We are sorry to hear about your experience with the product. We have over 1500+ different examples and sometimes it takes time to update all of them with all new versions of the themes and other third-party libraries.
Based on the attached error it seems that it cannot find a package, but the error message is cut and I cannot see the full error. Could you please share with us and we will be happy to assist.
Hello,
Thank you for the full error message. Based on the message it seems a package is not found in the registry:
There could be two reasons for this:
1) The package was removed from the registry - This is a @babel package and we are not the ones distributing and supporting it. It is used internally by create-react-app.
2) I see that you are using yarnnpkg registry instead of the default npm registry, that could be a reason for the missing package:
https://github.com/yarnpkg/yarn/issues/6123 (similar error for a package missing is their registry)