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
{{ message }}
This repository has been archived by the owner on Aug 3, 2023. It is now read-only.
The build process currently just bundles all of the code on a single index.js file, which is very inefficient when considering bundle-size. As an example, my application is about 1200kB (unzipped) in size, of which 500kB is from react-iconly.
I have very little knowledge about bundlers, so I have no idea what would be best way to go about doing this, but my educated guess is that using a different bundler (or maybe even just different options) would be enough.
My workaround was publishing a package with the whole source code (with some modifications made after my build process failed), and letting my bundler (my project is built with vite) do the dirty work.
After doing this, my bundle-size shrunk to about 800kB.
Hopefully something can be properly done about this in the near future.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The build process currently just bundles all of the code on a single
index.js
file, which is very inefficient when considering bundle-size. As an example, my application is about 1200kB (unzipped) in size, of which 500kB is fromreact-iconly
.I have very little knowledge about bundlers, so I have no idea what would be best way to go about doing this, but my educated guess is that using a different bundler (or maybe even just different options) would be enough.
My workaround was publishing a package with the whole source code (with some modifications made after my build process failed), and letting my bundler (my project is built with
vite
) do the dirty work.After doing this, my bundle-size shrunk to about 800kB.
Hopefully something can be properly done about this in the near future.
The text was updated successfully, but these errors were encountered: