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
In other words, when I finish my website and provide a distinct list of all of the imports from Qwik + Qwik City libraries at the top of my files, I end up with that list.
Those are used in all of my websites. Because of my architecture, I definitely use them.
Now, my question is this. What happens if I create a Vite pre-plugin that imports all of them at the top of every file? Is there any downside? After all, they are all included somewhere, so if I understand it correctly, then they are all included in the final bundle and won't be tree-shaken.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I develop my websites using Qwik. Let's say a website is made of 100 components. I know that I will import all of these items somewhere:
In other words, when I finish my website and provide a distinct list of all of the imports from Qwik + Qwik City libraries at the top of my files, I end up with that list.
Those are used in all of my websites. Because of my architecture, I definitely use them.
Now, my question is this. What happens if I create a Vite pre-plugin that imports all of them at the top of every file? Is there any downside? After all, they are all included somewhere, so if I understand it correctly, then they are all included in the final bundle and won't be tree-shaken.
Beta Was this translation helpful? Give feedback.
All reactions