ArkEnv v1 is out (Release Candidate)
• one schema → typed `env`
• bring ArkType, Zod, or Valibot
• fail-fast at startup, full-stack boundary included
this is the build we expect to ship as 1.0. try it and tell us what you rely on 👇
https://t.co/5qgciEs4Zk
fresh project:
npx arkenv init
from v0:
https://t.co/tSGJHkKiuh
from T3 Env:
https://t.co/HoPhLmDU2C
while we're happy with the api shape, we need real user feedback before v1 stable. reply here or leave your feedback on GitHub Discussions 🙏
ArkEnv v1 is out (Release Candidate)
• one schema → typed `env`
• bring ArkType, Zod, or Valibot
• fail-fast at startup, full-stack boundary included
this is the build we expect to ship as 1.0. try it and tell us what you rely on 👇
https://t.co/5qgciEs4Zk
keep your validator:
• ArkType → @arkenv/core
• Zod / Valibot → @arkenv/standard
same fail-fast DX either way. Next.js, Nuxt, Vite, Bun, TanStack Start- server secrets stay off the client.
@MansiCodez 🤷
Sounds like a problem that can be solved with an automation instead of dealing with people.
Write an automation to write that ticket. Tech lead is happy, project manager is definitely happy, and you get to focus on shipping, and remove friction in the team
@_yamcodes@tan_stack@vercel It is and continues to be. Vercel did not acquire TanStack, they became a partner, of which we have many (link). All of our software will always be agnostic https://t.co/GcpkGT1ll8
on the subject—if you're using an AI code review platform with per-seat pricing (CodeRabbit, Greptile, etc) consider how it perverts incentives.
these platforms are incentivized to use cheaper models to boost margins. if you want SOTA, use @pullfrogai and bring your own key ✨