VoidFlag
feature flags that NEVER silently break production
6 followers
feature flags that NEVER silently break production
6 followers
Feature flags have a typing problem. Every tool lets you reference flags as raw strings. A typo compiles, ships, and breaks silently in production. VoidFlag fixes this. Define flags once in a schema, and from that point, everything is typed. Your editor knows every flag, and mistakes don’t reach production. They don’t even compile. Finally, feature flags your compiler actually understands.
Hello everyone,
The idea for VoidFlag came from a real incident, a flag that was "disabled" but kept hitting production. Turns out someone referenced it with the wrong string. and it silently shipped with no problem
That's the problem every feature flag tool ignores. They all assume you'll type the flag name correctly, every time, across every file, forever
VoidFlag takes a different approach: schema-first, fully typed, CLI-driven. Your flags live in your code. Your editor knows them. Your compiler catches the mistakes before they ship
vf dev to start locally. vf push to go live. simple as that
No more tabbing to your dashboard just to double-check a flag name you're not sure you typed right
VoidFlag is very close to its beta release. The core is solid, more is coming. Early access is open, would love to have you in. VOIDFLAG
Happy to answer anything, about the architecture, the approach, or why I think loose strings are the original sin of feature flagging.