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
You wouldn’t have to deal with the hassle of manually adding the icons you’re going to use in the vite.config.js.
Even if your library has millions of icons, all of them would be available during development, but only the ones actually used would be included in the final build shipped to the client.
The text was updated successfully, but these errors were encountered:
@oktaysenkan This would be far more preferable than adding individual icon names to the build config or unnecessarily bloating the bundle with an entire collection. I'd love to recommend we adopt Monicon within my workplace, as the standard icon solution for all our apps, but unfortunately I can't do that if the DX every time is "use an icon.. check the config"
You wouldn’t have to deal with the hassle of manually adding the icons you’re going to use in the vite.config.js.
Even if your library has millions of icons, all of them would be available during development, but only the ones actually used would be included in the final build shipped to the client.
The text was updated successfully, but these errors were encountered: