Three booleans can put a React form in two states at once.
isSubmitting, isSubmitted and isError. Nothing stops a bug from setting two of them to true.
One status value can’t. It’s idle, submitting, success or error, and only one at a time.
#react#javascript#frontend
After migration to @rspack_dev Rsbuild, then try Rstest as a replacement for Jest. This reuse your Rsbuild config making your test runner behavior closer to your build and has single source. You can delegate the task to the agent. Meaning the annoying works when doing migration like replacing jest references to rs, changing the mocks, rewriting snapshots, etc majority of these will be handled by your agent. Just make sure you install Rstest skills and the agent is doing loop.
Our average shard with jest in CI is around 11mins. Down to 2 mins with rstest. Its just fast!
I always come back to this writeup from @Rich_Harris. It's been the oracle of most JS framework compiler work the past decade. This is why others failed where Svelte succeeded.
AI suggests we rethink this. We want restriction, not extension.
https://t.co/LjOijAGTsR
I talked about bundles lately because unrelated reasons at work:
- Finding JS path that should not be loaded
- Finding that some modules caused RAM issues
- Dev servers performance
These problems are contradictory.
[1/8]
New on our Frontier Red Team blog: using Claude to formally verify software at large scale.
Formal verification can prove that code is free of certain bugs, but historically it has only been feasible for small codebases (or required a lot of expert time).
With AI models, however, this is beginning to change. In collaboration with @theoremlabs, we used Claude to prove security properties in over one hundred real-world open-source libraries over the span of a few weeks.
Read our research in full here: https://t.co/zUyx8CjBEk
tsrs is a fast new TypeScript compiler port 🔥
This deep-dive blog post by @max_schwenk explains how he created the compiler and what makes it so fast.
Contains excellent infographic animations.
👀 Have you heard of this new experimental React MCP?
Now officially documented here:
https://t.co/Jnz5Zn2dmJ
Technically, it's not really an MCP
➡️ registers a group of tools to Chrome DevTools MCP
Hey @claudeai@lydiahallie , in the Claude desktop app, it works ctrl+q to toggle back and forth between sessions. Could you also add ctrl+p and ctrl+n shortcuts to navigate through sessions? Hopefully we can get customization especially for navigation.
Hey @ClaudeDevs@bcherny@lydiahallie Sometimes in the claude code desktop, i can only see my messages, the replies got hidden. It goes back after you reload. can you guys fix this annoying issue? It happen sometimes after getting response from claude.
@ClaudeDevs@bcherny@lydiahallie I have this thought, although obviously, Im wrong here just wondering if you folks at Anthropic actually use the Claude Code desktop app. The UX is not really for power user. I dunno maybe because you dont check the session anymore, but please try to improve it.
Cloudflare is taking ownership of tsrs, a port of TypeScript to Rust. It's 8x faster and uses 70% less memory than TypeScript 7.0.
We are not forking TypeScript – we are working with the TypeScript team and as a result 7.1 is already ~2.5x faster, too.
https://t.co/eXF9NzufID
@claudeai@ClaudeDevs you give us an ability to rename the claude code session title in mobile and desktop. But the agent still overrides this lol. Can you make sure the title will not be overriden after the custom title?
Give your agent a way to verify its work. This can dramatically improve the quality of output.
With this process in place, Claude Code was able to write 90%+ of its code itself. When generating software at a faster rate than you can review it, the bottleneck shifts to proving that it works. @bcherny and team invested enough in verification, we've been able to move fast while maintaining stability.
Code reviews aren't going away, but you need to think of it differently. One human reading through line-by-line is no longer going to work as a gate, it needs to evolve into a multi-layered verification system, built with fast deterministic feedback loops for your agents.
This is where e2e tests, feature maps (as @poteto has been advocating), property tests and multi-agent adversarial reviews come in. These all provide opportunities to catch errors early and fix them before things get out of hand.
You don't have enough eyeballs for the amount of code being written so your focus needs to be on product intent, risk assessment and evaluating evidence rather than reviewing code. Delegate the code checking work to your automated tests, scale your approvals based on risk, and turn your test failures into living evaluations. This approach helps maintain speed without losing reliability.
Let the agents do what they do best and let you focus on what makes you irreplaceable: judgement, direction, and ownership. We tried to capture how we handle code review and verification in this writeup. Hopefully it's helpful.
@bot just created a @ChatGPT codex session in my cloud VM. And through codex remote control, i can access the session to my phone. So I can now add codex to my task-to-pr workflow as my reviewer. Just let Grok bot orchestrates all of the works!
@poteto@bot Why not make the Grok bot computer truly persistent like a VPS and then provide an option to increase the specs? Grok manages my VM right now and Im happy with it. Think about moving the projects in Grok bot computer, that will be better.
https://t.co/otZg9dIh7u has fully moved off CSS-in-JS to CSS Modules, resulting in 55% less server-side render time and 25% faster component init. https://t.co/0AV4Fr3RSo
We’re also pushing Rstack and MF further within ByteDance, where we continually find and address bottlenecks in codebases with 10M+ lines of code
https://t.co/LKDzg9PtSs