Jake Hebert

@akashdevcc I would love to take a look! I had off and on issues with storybook as well, I will take a look today to see if it's still an...

Yeah I had issues with any package manager except npm. Which is super odd because I’m using yarn4 in the project this repo is based on. I would prefer to...

@saiichihashimoto any updates or tips on this? New to your tool but running into this immediately. All relevant package versions: ``` "@sanity-typed/groq": "^1.8.14", "@sanity-typed/next-sanity": "^2.1.4", "@sanity-typed/types": "^6.3.5", "@sanity/client": "6.21.0", "@sanity/icons":...

@JWesorick I'm trying to find a way around adding `@jsxImportSource react` to every one of my server components. It's not a *huge* deal, but I feel like in a monorepo,...

@JWesorick Have you figured out a solution to the pop-in? I'm trying not to focus on it but I the pop-in is so pronounced in dev 😂

I fixed the pop-in issue! 🎉 For me, it's actually symptom of the `@expo/next-adapter` not nativewind. I found the solution in the [Solito repo](https://github.com/nandorojo/solito/blob/master/develop/appdir/app/styles-provider.tsx) Basically, just add this Provider to...

I would also still like to figure out how to remove the `/* jsxImportSource react*/` from every route, but not there yet.

@JWesorick Did you try the provider solution I added above? The stylesheet is getting loaded client-side if you don't explicitly wrap your code with it.

@shawnmclean Definitely not perfect, but this project I am working on has it working: https://github.com/panzacoder/fcc-monorepo

@shawnmclean Hmm, two things you might look into from 10m poking at it: 1. I had to add `/** @jsxImportSource react */` to the top of _every_ server component in...