New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bundle size #12
Comments
The react library fully supports tree-shaking, so it likely comes down to your bundler configuration or the way you're importing the icons. In apps bootstrapped with import { Smiley, Rainbow } from "phosphor-react"; Using the default import, If you need to, you can import icons directly from the bundled source: import Smiley from "phosphor-react/dist/icons/Smiley.esm.js"; |
Thanks for the explanation, I was using destructuring imports and the bundle was still big.. But, Happily the problem was in the lib version I was using (1.0.0) I've just updated to 1.2.1 and, great news, problem solved!! 😄 |
This is still happening in [1.4.1] |
Same here using 1.4.0! |
I confirm, still happening in |
Some news on this ? |
@lmichailian can you provide details on your environment, bundler, and usage? As stated before, the current version of this package is tree-shakeable, but that does not mean your bundler can do it. |
Hi, I've been using phosphor-react in some projects and I identified some bundle size problems.. Analysing the bundle I could realize that phosport-react is using almost 60% of the space used.
I don't know it's the expected behavior so I opened this issue to report this situation!
The text was updated successfully, but these errors were encountered: