Mr Chief Intern Officer

1/ Making a wild guess here... @LFG_org's 1B+ worth of $BTC is all going into @THORChain's liquidity pools And the yield bearing BTC in turn is going @anchor_protocol borrow. @terra_money and @THORChain have the best synergy ever. Let's investigate 👇

@capajj @valtism @aidenybai Suffix means to put the word ‘Icon’ at the back, like ‘UserIcon’ prefix means to put the word ‘Icon’ at the front, like ‘IconUser’ He meant to use suffix in this case

@valtism @aidenybai You misspelled prefixed

this is so annoying why are icon libraries ranked above my own components

@crutchcorn @tan_stack Makes sense, thanks!

@CryptoMrCIO @tan_stack All state needs to live outside of the framework and still be reactive to be framework agnostic. Store is how we stay consistent while doing so

I just published @tan_stack Store 0.7, which now supports reactive Derived data sets and Effects: tanstack.com/store/latest/d… Check it out and let me know what you think!

@crutchcorn @tan_stack How is Form using Store?

@tan_stack This was a major blocker to @tan_stack Form v1 BTW 👀👀👀

@tannerlinsley @tan_stack Cool read! Also TanStack form V1 PLEASE

I can't state how pivotal Vinxi and Nitro were in making @Tan_Stack Start. Come read about how it was a game changer! "Why TanStack Start is Ditching Adapters" tanstack.com/blog/why-tanst…

@tannerlinsley @tan_stack When Tanstack Form v1? :(

Stoked to announce that @Tan_Stack Start is now officially BETA! 🎉 🎊 Please come and try it and help us get it ready for 1.0!

@ThePrimeagen I like const for consistency across the code base, treat functions as first class variables

WHY DO YOU DO THIS, CONST ARROW IS LONGER

@jherr Balatro if you like Roguelike deck builders and poker

Recommendation request. Steam game, $50 or less, Mac compatible, easy non-addictive play. Not an FPS.

@gluestack Jesus we haven’t even moved from NativeBase because we were waiting for Gluestack to become more stable. Breaking APIs really harming our productivity.

The gluestack-ui v2 is here! 🎉 🌬️ Uses NativeWind / Tailwind 📋 Copy-paste components for Next & Expo 🎨 All new design 🚀 Performance ⚛️ RSC support 🖌️ Figma Kit with variables, dark-mode and variants 🔁 Migration to v2 with a codemod

@toby_solutions Because it’s v0 😭

Tell me why you're not using Tanstack forms yet, please.

@pisarenco_gh @housecor Perfect for when I need to store state and don’t want rerenders to happen as a result :)

@housecor How useRef would help to handle the state? Refs don't interfere with component life cycle, so you cannot trigger rerender with them. In them end you would need useReducer or some of it derivates to re-render the component.

25+ ways to handle state in a React app in 2024: React: useState useReducer useRef useContext (to share useState, useReducer, etc) useOptimistic useSyncExternalStore useActionState React Server component (just return fetch result) General: Redux Jotai Zustand Valtio Mobx Recoil XState Remote state: Tanstack query swr Apollo RTK query Forms: Formik React Hook Form Routers: React Router loader Remix loader Tanstack Router loader Web platform: URL Cookie localStorage sessionStorage indexDB And this only a partial list of the most popular options!

@TkDodo Damn that’s a nuance I wouldn’t have caught just from skimming the docs. Thanks!

@CryptoMrCIO React Query awaits the result of the onSuccess callback internally: #L210-L218" target="_blank" rel="nofollow noopener">github.com/TanStack/query… Only after that, we set the mutation into `success` state: #L231" target="_blank" rel="nofollow noopener">github.com/TanStack/query…

📚 Automatic Query Invalidation after Mutations isn't a thing in React Query - but did you know that it takes just a couple of lines of code to build this in user-land? New blog-post is up now 🎉

@TkDodo Sweet, thanks for sharing!

@CryptoMrCIO The thing about async functions is that they always return a Promise, but if you already have a Promise to return and don't use the `await` key word, you don't need to make your function `async`. I have a blogpost about that, too: tkdodo.eu/blog/about-asy…

@gluestack Me, like several others, stuck to NativeBase’s prop-based styling because we liked it more than ‘tailwind’ styling. Hope it gets more love.

We're shaking things up by moving towards copy-pastable components in React & React Native. No more constraints of a component library! Our CLI tool streamlines the process: simply use npx gluestack-ui init to initialize gluestack-ui in your Next.js and Expo projects.

@TkDodo Reads nice from left to right*

📚 Getting back to valuable content: I wrote a blogpost today with all arguments I could find on why the generic notation (Array<string>) is better than the array notation (string[]) in TypeScript. Let me know if I missed anything: tkdodo.eu/blog/array-typ…

@housecor Much prefer styled-system, it’s like Tailwind but easier to read and easier to modify with JavaScript at runtime

Three misconceptions I’ve noticed among people who don’t “get” Tailwind: 1. People think it’s “inline styles”. (It’s not. It’s utility classes that smart people wrote for you.) 2. People think it’s repetitive/bloated. (It’s not. It’s designed for use with components like React/Vue/etc. Components encapsulate styles and support reuse. And the resulting CSS contains only the Tailwind classes you use.) 3. CSS “experts” think they can do it “better” from scratch. (They can’t. It’ll merely be a poorly documented alternative).

@InternetH0F “I can turn your floppy disk into a hard drive”

@TkDodo @diegohaz useMutation callbacks: run every time mutate() callbacks: run if component is still mounted?

@diegohaz I think it depends what the button is doing. For useMutation, we have two sets of callbacks: ones that always run, and ones that only run when the component is still mounted once the request completes (that's the parallel to setTimeout I'm seeing)

A friendly reminder — if you're using setTimeout within event handlers, ALWAYS clean it up when the component unmounts. Otherwise, you'll spend hours trying to fix bugs... like I just did. 🙃

@TkDodo Makes sense, thanks for the resource!

@CryptoMrCIO Oh yeah it's different for mutations - the callbacks are great there. For forms, have a read here: tkdodo.eu/blog/react-que…

I haven't written a blogpost in quite some time, because I'm busy doing other things. What would be a topic you'd be interested in reading more about?

@TkDodo I currently use it for things like updating default state of a form, showing toasts (mutations) etc

@CryptoMrCIO I'd be interested to know which code you run in onSuccess because I don't think there are lots of good use-cases for it