-
Notifications
You must be signed in to change notification settings - Fork 22
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
Oh vue icons is loading the whole bundle size instead of the selected ones #20
Comments
I am closing this issue since it has nothing to do with oh vue icons. But if anyone ran into the same issue, just configure your
Also, I think this should be added to the documentation. |
Thank you for point it out! I'll add it to the documentation later. |
using vite v5.0.10 Vite Dev Server with
downloads all the icons every time? |
@Renovamen After trying many things in the end removing the build transpile and optimizeDeps config from nuxt-config sped up the build back to good time, and reduced the bundles from nearly 1Gb to ~100mb again in local dev I think this is the same experience @Dino-Kupinic is having now I'm using "nuxt": "^3.9.0", and vue latest, latest nuxt appears to use vite ^5 |
I can confirm that using
is no longer working as expected. ("nuxt": "^3.11.2") With this code i get multiple script chunks downloaded and my page load goes up to 300MB total! With this code removed i get a single oh-vue-icons_icons.js file downloaded that is "only" 44.4 MB. |
First of all, thank you for creating this awesome library and making us cry less.
Hi, I am using vue 3 with vite. I noticed something strage. Oh vue icons is loading something like 108 MB of bundle size and it takes a lot of time to load even in vitejs.
Here's my setup
Then in my component:
You can see the problem below. I am conditionally controlling these six icons. That's why there are only one or two icons per card.
Why is it loading 108 MB of javascript? That doesn't make any sense. Also I am using vite with vue3. Do I need to add any extra configuration?
Thanks in Advance.
The text was updated successfully, but these errors were encountered: