Fredrik Höglund

Gitlip Editors: Demo Launch 🌷 Gitlip is a collaborative coding platform, and today we’re launching the demo for Gitlip Editors - our take on collaborative coding environments. If you've ever wanted to collaborate on Markdown or code with the convenience of Google Docs, our demo is for you.

@cakemakerjake I realized my name was Ephem over there, so I updated it to my full name when I saw this to make me easier to find, so should be visible in search now. Thanks for pointing this out!

@ephemjs Strange, you didn't come up when searching for your name

🦋

@cakemakerjake Haha, it is not! 😂 This is me: bsky.app/profile/ephem.…

@ephemjs Where? Pretty sure this is not you! Although, Mark seems to believe so 😅

@jamannnnnn Good to hear and thanks for saying so, definitely helps motivation!

@ephemjs Always worked great for me, thank you for your work on this!

Oh wow, rollup-plugin-preserve-directives is almost at 30k weekly downloads, it's probably time to make a stable release.. 🙄 I should probably add a pipeline and tests too, especially with all the new directives flying around, I just wish days had more hours.

Interested in how to host Infinite Git Repos on @Cloudflare? ⛅️ At Gitlip we’ve accomplished this using - Cloudflare Workers - Durable Objects - @libgit2 - @nixos_org - WebAssembly - @emscripten and now we’ve written about how we did it.

@elibelly @ReactAdvanced Me! Me! 🙋‍♂️🤗

It's the @ReactAdvanced conf part of the week! Who am I seeing there tomorrow? 💂🏻‍♂️🎡🇬🇧

@TkDodo @phry @alvarlagerlof I KNEW there was something I forgot! 🤦‍♂️

@phry @alvarlagerlof I'll get one at the airport for double the price then 😂

Found it!

@alvarlagerlof @acemarke @ReactAdvanced I'm arriving Thursday afternoon, staying until Sunday, will be so great to meet both of you again!

@acemarke @ReactAdvanced I'm here until Saturday 👋

Arrived in London for @ReactAdvanced this week! Would love to hang out with folks here for the conf or anyone who's here already. Ping me if you're around the next couple days, or will be at the conf and want to say hi!

@alvarlagerlof This makes me want to add this function. What it would do is populate the cache entry with "🐟🐠🐡" as a helpful means of finding that you've made an error. Would also take longer than usual, because fishing is about waiting.

Me, writing prefish instead of prefetch

How did I not know these work in GitHub😍

@TkDodo I keep saying this could change library APIs in a huge way. 😀

@TkDodo Not only that, having "isomorphic" globals that are scoped per request on the server would also unlock moving a bunch of stuff off of context altogether. Imagine instead of having to do useQueryClient and pass that around, you could just import queryClient anywhere.

Can't even use state (or refs) for singletons anymore 😢

@sebastienlorber @pleunv @sophiebits @oljimenez Yeah, I can't decide if your example up top can accidentally break, or if it is accidentally working. Glass half full half empty kind of situation I guess. 😆

@ephemjs @pleunv @sophiebits @oljimenez Composition can sometimes create nasty bugs 😅

React 19 greatly simplify vanilla data fetching Previously we had to useEffect, handle race conditions, unmounts, loading/error state... Now you just: - store a promise - read it within Suspense/ErrorBoundary This makes a whole class of problems disappear

@pleunv @sophiebits @sebastienlorber @oljimenez Oh yeah, it only becomes a problem when it becomes a problem, like when your app is suddenly suspending at a level it didn't before. There are unexpected cases like an error happening on the server and that top level Suspense boundary is now used to retry on the client.

@ephemjs @sophiebits @sebastienlorber @oljimenez This behavior seems normal, as a component triggering a grandparent suspense would also unmount any parents. I wouldn't expect the same without Suspense, though, and I think this is a fairly common pattern for global instance providers.

@pleunv @sophiebits @sebastienlorber @oljimenez Yeah. We had bug reports in React Query about doing: const [queryClient] = useState(() => new QueryClient()) when there was a Suspense boundary above that. If that boundary was hit, a new queryClient was created. Same with this promise thing: codesandbox.io/p/sandbox/naug…

@sophiebits @sebastienlorber @oljimenez Wait... so singleton patterns where instances are created in a state initializer in order to avoid a rather nasty useRef+useEffect approach are not safe? Is this a v19 thing?

@TkDodo @tan_stack My brain always hurts when we talk, but in a good way! I feel the information density is always super high.

Had the best of discussions with @tan_stack query co-maintainer @ephemjs today - one of those where your brain hurts after 2 hours 😂. Here are the things we went over: - A component that can detect if you've prefetched too much or too little. I'll post the RFC later today. - The `use` PR by @alexdotjs (github.com/TanStack/query…), which we'll likely ship soon behind an experimental flag. Coincidentally, you will also be able to use that flag to trigger prefetches during render 🤯. - With the help of the nextJs and swr team, we think we found a way to make our experimental ReactQueryStreamedHydration plugin work with authenticated requests (@AdamRackis is gonna love this). It will likely need a re-write (new package), so don't expect anything too soon, but we think we could also make it independent of nextJs. Exciting 🤩