What a time to be alive

Idk how I feel about this. ES Modules are the future, retrofitting CJS to work with ESM will just slow down the (already slow) shift to ESM since CJS now “just works” with ESM (with some caveats)

(I could be missing the point or misunderstanding, these were just my initial thoughts)

knip is cool, but last time I tried it, it didn’t support react native

A good example would be github.com/t3-oss/t3-env
But I did run into some issues getting that to work with expo, that's why I had to make my own basic env helper

I threw this together in a couple of minutes, but this is along the lines of what I got in mind.
gist.github.com/KaBankz/fc90...

For 9, is there any technical reason that expo router doesn't have a concept of "private folders" like Next.js's app router? It would be cool to colocate some components next to the related screens in a "_components" folder.

Finally, env’s in expo have been a huge pain for me, and this simplifies it a ton.

Any plans on making a typesafe env helper util? Currently I use zod to validate my envs and export a env object, but a first party expo solution would be cool.

Ik it’s pretty new, but how does it compare with Skia List that was announced not too long ago?

That’s pretty cool, I’ve used bootsolash before for animated splashes, but this seems a lot easier

Squash merge all the way

Skia List is looking promising