Ionify v0.1.38 is now published on npm.
This release represents an important milestone for Ionify, a Rust-powered frontend build engine exploring a different approach to build infrastructure: persistent builds rather than repeatedly reconstructing the same knowledge.
What shipped?
Version 0.1.38 is published as nine npm packages: the main @ionify/ionify package and eight platform-specific native packages covering supported macOS, Windows, and Linux architecture targets.
The release preserves Ionify's hybrid packaging boundary while distributing native binaries through npm.
All nine packages are now available at version 0.1.38, with their latest dist-tags updated.
Verification beyond publishing
Publishing packages is only part of a release. The more important question is whether developers can install and actually use them.
For v0.1.38, I verified the experience against the real npm registry on macOS ARM64 with Node.js 22.20.0:
- Fresh installation of
@ionify/ionify@0.1.38 - Native module loading and CLI execution
- Actual
npm create ionify@latestscaffolding - Dependency installation and successful build
- Development server startup
- Chrome navigation, direct route loading and page reload
The browser run completed without observed runtime errors. React Router future-flag warnings were recorded, and verification on other operating systems remains a separate concern.
The existing create-ionify@0.1.1 package continues to work without republishing, resolving the latest Ionify engine.
Why Ionify exists
Traditional frontend build workflows often repeat work across development, production builds and CI.
Ionify is built around a different architectural direction:
One Graph. One CAS. One Authority.
The goal is to make verified build facts reusable across lifecycle boundaries, while preserving deterministic execution and explicit ownership of build artifacts.
This release doesn't mean that every part of that vision is finished. It means the current published engine has passed a real consumer installation and startup path.
What's next?
The next engineering focus is bringing development, production artifact prewarming and production builds closer to a shared persistent authority.
That means improving reuse, reducing redundant transforms and validating correctness across lifecycle transitions.
The long-term goal isn't simply to make another bundler.
It's to make frontend build infrastructure remember what it already knows.
Try Ionify:
npm create ionify@latest
Website: https://ionify.cloud
npm: https://www.npmjs.com/package/@ionify/ionify
Top comments (0)