In order to run yarn build successfully we needed to remove the minify step from the build process. We need to be able to integrate it back to minify our code deployed to production.
tldr;
create-react-app uses uglify 2 and some of our dependencies (mostly from IPFS) where throwing an error when minifying (their codebase is built with es6 syntax and uglify 2 is not able to understand it).
By transpiling their code base before minifying we hoped the process would succeed, and it did, but another error popped up. This error is referenced here. Seems their library checks against class names. minify libraries overwrite class names thus the check fails.
Tried using uglify 3 since it understands es6 syntax but the name checking error still renders and the app does not work. Even with the keep_fnames: true and keep_classnames configuration params the app fails (the error is no longer about the classname but another one: Uncaught SyntaxError: Unexpected token ().
Tried using babili with the keepFnNames & keepClassName params and it did not work either.
AquiGorka
commented
6 years ago
Ref: here
In order to run
yarn buildsuccessfully we needed to remove the minify step from the build process. We need to be able to integrate it back to minify our code deployed to production.tldr;
create-react-appusesuglify 2and some of our dependencies (mostly from IPFS) where throwing an error when minifying (their codebase is built withes6syntax anduglify 2is not able to understand it).classnames.minifylibraries overwrite class names thus the check fails.uglify 3since it understandses6syntax but the name checking error still renders and the app does not work. Even with thekeep_fnames: trueandkeep_classnamesconfiguration params the app fails (the error is no longer about the classname but another one:Uncaught SyntaxError: Unexpected token ().babiliwith thekeepFnNames&keepClassNameparams and it did not work either.