Jake Ginnivan

FWIW, I have taken a crack at switching the NX plugins repo for my old company across. https://github.com/sevenwestmedia-labs/nx-plugins/pull/61 My main issue so far are console output differences when running vitest...

I am trying to figure out the best approach for this as well. I have two main strategies 1) Single jest project with a tsconfig.test.json which includes source files for...

FWIW I have upgraded an internal Terraform plugin I have to use project crystal. I was able to write a migration to drop out a bunch of targets (apply, plan,...

My colleague had issues with some WSL process running away. I wonder if it's something to do with using Terminal (non-wsl) then behind the scenes NX is shelling commands which...

Another scenario which would be handy to fix is `glamorous(MyComponent)({})` throws the same error.

https://www.typescriptlang.org/docs/handbook/modules/reference.html#node16-nodenext is worth a read. If you use nodenext in the esm type checking it will enforce file extensions etc in the type checker which could help prevent downstream issues.

This is caused when you do not have `categories` in the front matter of a page it seems

I ended up switching to Drizzle + Postgres Flexible Server while waiting for https://github.com/drizzle-team/drizzle-orm/pull/1610

Thanks for the response @yorek! A quick spin didn't seem to work, but I think the issue is that Prisma has a native engine (written in Rust) which talks to...

Actually, the above error was the second attempt when I removed `tcp:` from the connection string. With that I got `PrismaClientInitializationError: The provided database string is invalid. Error parsing connection...