npm ERR! code 128 MDB 5 React

Akizuki230 commented 3 years ago

I don't understand, the certificate affects old devices or with old OS versions. This problem is also occurring on my pc, my local environment on my pc is new and works under ubuntu Ubuntu 20.04.3 LTS.

however I checked the certificates and it still gives me problems when compiling my project

''failed to compile. ./node_modules/mdb-react-ui-kit/dist/css/mdb/min.css ParserError: syntax error at the line:1, column 26"

Krzysztof Wilk staff commented 3 years ago

The problem with access token generation is related to the ca-certificate about which Grzegorz wrote above. An error with the build is caused by our package. For now, you can check one of the solutions provided here: https://mdbootstrap.com/support/react/mdb5-version-1-4-0-npm-run-build-error/. but we will fix it as soon as possible :)

Akizuki230 commented 3 years ago

I read that post before writing to you.(https://mdbootstrap.com/support/react/mdb5-version-1-4-0-npm-run-build-error/)

right now it lets me run npm install and npm start in my local environment but nmp run build to deploy a prod doesn't work for me

"Creating an optimized production build... Failed to compile.

./node_modules/mdb-react-ui-kit/dist/css/mdb.min.css ParserError: Syntax Error at line: 1, column 26"

I have been two days without being able to do any deployment to production

Krzysztof Wilk staff commented 3 years ago

Did you try to install a previous version?

Akizuki230 commented 3 years ago

yes, I tried to install version 1.3.0 and 1.2.0 without success.

I feel that you laugh at me, I have not been able to work for 3 days because I do not know if what I develop could deploy in PROD and I do not want to do it because I am afraid that this will affect my users.

I paid for this especially for the support and I do not feel that they are helping me.

And if they ask me to install an older version, why do they make a new version available?

Krzysztof Wilk staff commented 3 years ago

It seems that it is the problem with the postcss dependency. Updating this plugin affected our repository causing this error. Now we can't fix this issue without making a release and it needs some time to debug everything and make it work. All we can do for this moment is providing temporary solutions for users.