Oof. I just read your post in the most uncharitable, pedantic way possible, and I gotta tell ya: it's not looking good for you.
01.03.2026 15:04
👍 10484
🔁 2194
💬 60
📌 63
Oof. I just read your post in the most uncharitable, pedantic way possible, and I gotta tell ya: it's not looking good for you.
@tannerlinsley.com Hi! Some feedback. I visited tanstack.com/start/latest... and felt lost in the navigation. Would be great if the left nav menu autoscrolled to the active item on initial load. Also, I would increase highlight the active menu item since i missed it first time I scrolled through.
so i tried connecting chatgpt to github and linear expecting to at the very least ask "what are my current tasks i'm working on" and "what are my open prs", but i have no idea how to have it trigger it using the apps?
Have you instead considered Greenland taking over US?
If you hate someone who recently had a baby, you can gift them baby clothing with buttons. The more buttons, the better.
ah, thank you! super useful!
Thank you for the explanation, Joe! Looking forward to it :)
Yeah found that as well! That seem to be slightly different than this PR i found scavenging @capt.dev who was cc'd github.com/captbaritone... , which also references your link.
looking forward to it!
in the meantime, may i ask if this PR is still up to date with the latest thinking on concurrent stores, or are there other resources i can look up? are there any thoughts around how to subscribe to parts/slices of an external store? github.com/facebook/rea...
noo
yes please persist across app reloads and have it sync between devices. also have it configurable for different lists. for inspo ice cubes does this pretty good.
👋 @ricky.fm if you have time
I was hoping React Compiler would only rerender children if their sliced part of a larger state was updated - unfortunately all children gets updated :'(
Curios what the recommended way is to solve this while not opting out of concurrent rendering? playground.react.dev#N4Igzg9grgTg...
Fighting the urge to develop a custom todo app to resolve my issues of not being able to commit to todos.
nice! i don’t want to contribute to the thread as I’m not really a next.js user, but seeing the possible solution being to perform static analysis to determine whether args are being used rather than encourage explicit mapping of args with linting confirms my feelings that next is too magic for me
Having fun building my own scheduler component! Currently focusing on getting the interactions and layout feel right and smooth, with proper keyboard support. Recurring event support also in the works!
it literally has react in the name and is presumably intended to be used within a react app oh my god
a bit too assertive for my taste
try me!
Toying with patterns to update css variable without triggering rerenders. Is the anti-useEffect crowd ok with this use case? (cc @tkdodo.eu)
My main complaint about steam machine :(
interface when possible, types when necessary
I'm now apparently pluck hair from ear canal years old.
I’ve found it only working if i spend a lot of time compiling the flashcards myself. Pre-made collections aren’t nearly as effective.
the european mind cannot comprehend this
If rolldown-vite wants to be a drop-in replacement from vite v7, and it changes css parser, isn’t it also a rolldown-vite issue?
:( Will try to extract this to a reproducible example, but would be great with a better stack trace showing the faulty css file.
aah, I see - thanks for the clarification! although I wish there was a way to globally set cancelRefetch to false.
@tkdodo.eu hi! would you be open to expose `useQueryResult.invalidate()`, instead of having to do `queryClient.invalidateQueries(query.queryKey)`? I'm noticing colleagues reaching for `queryResult.refresh()` simply because it's more easily available.
Anyway I’m excited for it because I could introduce new code organization practices in our SPA and the day I manage to convince people of BFF being worth it it’s just flip a switch *poof* server rendered!
