Menu

#Ionify

10 posts

Feed·
10 of 10 posts
Tree-Shaking is Over! Are you done with the limitations and repetition of traditional tree-shaking?
🖼️
0

Tree-Shaking is Over! Are you done with the limitations and repetition of traditional tree-shaking?

DEV Community·KhaledSalem·about 1 month ago
#9SR36qfP

From Dev.to - javascript: Tree-Shaking is Over! Are you done with the limitations and repetition of traditional tree-shaking?

15s
Read More
📰
0

Ionify vs Vite: What Actually Happens Inside Your Build Tool

DEV Community: webpack·KhaledSalem·about 1 month ago
#MxynnrHR
#dev#class#build#ionify#code#article

Most developers use Vite and trust it. It's fast, well-designed, and gets out of the way. But there's a fundamental assumption baked into Vite's architecture — and every other major build tool — that we decided to challenge when building Ionify.…

15s
Read More
build time from 2.4s to 459ms
📰
0

build time from 2.4s to 459ms

DEV Community: vite·KhaledSalem·about 1 month ago
#sr3RLezC
#dev#ionify#auto#width#photo#article

A project from +11K module had 1500 ms warm build using Ionify. Today we reached 400 ms. While Vite8 takes 2.2s. I am publishing this new version of Ionify now! We don't run the same loops twice.…

15s
Read More
Moving from Webpack and Vite to Ionify is filling this gap
📰
0

Moving from Webpack and Vite to Ionify is filling this gap

DEV Community: webpack·KhaledSalem·about 1 month ago
#dp8EBbuY
#dev#ionify#auto#width#photo#article

Modern frontend tooling is stateless, forcing repeated work on every build. This leads to slow feedback loops, wasted compute, and poor scalability as applications grow. Moving from Webpack and Vite to Ionify is filling this gap!!…

15s
Read More