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 would like to use material-ui, and in my toolchain I use the google closure compiler, which does dead-code elimination and renames things. To prevent it from renaming we have to have .extern.js files.
This is a bit tedious at first, but it allows shipping only the code that is being used. It would also allow to use material-ui from ClojureScript (which uses the google closure compiler).
Could it be an option to add these files to material-ui ?
The text was updated successfully, but these errors were encountered:
@nenadalm React is a bit different. They are publishing one big optimized javascript file. We are publishing a lot of small files (e.g. each components) that users build system have to bundle. (different story for the umd bundle)
As far as I know, you can't have tree shaking with the React publishing approach, but it's fine as they don't need it. We do.
[feature request]
I would like to use material-ui, and in my toolchain I use the google closure compiler, which does dead-code elimination and renames things. To prevent it from renaming we have to have
.extern.js
files.This is a bit tedious at first, but it allows shipping only the code that is being used. It would also allow to use material-ui from ClojureScript (which uses the google closure compiler).
Could it be an option to add these files to material-ui ?
The text was updated successfully, but these errors were encountered: