Drizzle v1.0.0-rc.1 is out 🚀
▪︎ Effect v4 native support
▪︎ JIT row mappers to reduce ORM overhead to ~0
▪︎ Reworked casing API (breaking change)
▪︎ Drizzle for LLM agents (preview)
Drizzle is now as fast as using raw driver and mapping(or not mapping) results by hand 🙃
we can't ship new releases because we've hit 100mb npm releases limit, trying to resolve this with npm support(almost 2 weeks so far)
big release is coming though, we'll definitely hit new limits right after this one too
we can't ship new releases because we've hit 100mb npm releases limit, trying to resolve this with npm support(almost 2 weeks so far)
big release is coming though, we'll definitely hit new limits right after this one too
we can't ship new releases because we've hit 100mb npm releases limit, trying to resolve this with npm support(almost 2 weeks so far)
big release is coming though, we'll definitely hit new limits right after this one too
we can't ship new releases because we've hit 100mb npm releases limit, trying to resolve this with npm support(almost 2 weeks so far)
big release is coming though, we'll definitely hit new limits right after this one too
Wrapped into a @DrizzleORM custom type
One-line swap from `vector()` to `float32Vector()`, same
DDL so no migration
Reads come back identical, only the insert payload shrinks
spicy year thus far.
drizzle-orm dethroned prisma for the first time. still no v1. prisma-next on the horizon.
kysely emerging as #3, dethroning it's spiritual ancestor knex.
mikro-orm breaking 500k.
npmtrends.com/@pgtyped/runti…
ALT npmtrends graph showing what the tweet talks about.
seeing several posts suggesting @prisma had layoffs or mass departures in the last 2-3 days but not seeing any blog posts.
i run prod systems on prisma products, so i'd appreciate transparency from @sorenbs on the company's state.
time to migrate to @PlanetScale@drizzleorm?