Loading…
Topic
React
30 posts about React. Every summary links to the original.
- 30 posts
- 13 companies
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
Newest first
Posts
How AI-assisted development helped us build the new Dropbox experience
Dropbox is rolling out a new experience that helps users understand files and perform actions like organizing folders or combining documents into PDFs, with changes that can be undone. To meet a November launch deadline, engineers used two integration approaches: embedded web views for web parity and direct React component import for control, with AI helping trace dependencies. Coding agents were delegated defined tasks such as implementing 22 accessibility features, updating tests for five core web components, and retiring an older file list by completing 53 AI-handled tasks in one week. Engineers reviewed all agent output, and an agent discovered a Chat-history bug that was fixed before release. Customer feedback from eight design partners and usage signals helped prioritize improvements, with the agent workflow providing a consistent way to implement fixes.
Fixing the Google Translate crash in React without turning translation off
React applications crash with NotFoundError when Google Translate replaces text nodes with elements, because React still holds references to the detached nodes. The standard workaround of patching removeChild and insertBefore to skip detached nodes stops the crash but leaves stale translated text visible and new elements invisible. A mutation observer detects translation by monitoring for class=“translated-ltr” on , which appears about 190 ms before text swapping begins. The fix uses a WeakMap to pair each detached text node with its replacement , so removing the text removes its font and inserting before the text inserts before its font. The patches are only installed after translation is detected, leaving native DOM methods on untranslated pages so real bugs still reach error tracking.
Introducing the Auth0 SDK for TanStack Start
Auth0 released a dedicated SDK for TanStack Start, a full-stack React framework, to replace hand-rolled OIDC flows or adapted SDKs. The SDK provides hooks, components, route guards, server middleware, and server helpers that integrate with TanStack Start’s server functions, middleware, and file-based router. Setup involves installing the package, configuring environment variables for the Auth0 application, creating a server-side Auth0 instance, registering the auth0Middleware in the start file, and wiring the router context and Auth0Provider in the root route. The SDK automatically mounts auth routes for login, callback, logout, profile, and backchannel logout, and supports features like login, logout, protected routes via requireAuth, session reading on the server with getSession, and additional capabilities such as passkeys, organizations, MFA, and API scope checks. The fastest way to try it is the official quickstart, which scaffolds a fresh app and adds the SDK step by step.
Creating a whitelabeled connected account dashboard with embedded components
This tutorial explains how to build a whitelabeled connected account dashboard using Stripe Connect embedded components, eliminating the need to manually implement pagination, permissions, and state management. The example uses FurEver, a pet grooming SaaS platform, and integrates the ConnectPayments, ConnectPayouts, and ConnectNotificationBanner components for payments, refunds, dispute management, balance and payout views, and account enablement alerts. The server-side requires creating an account session with enabled components, while the frontend initializes ConnectComponentsProvider with the fetched client secret and publishable key. Platform user roles can be enforced by setting features such as refund_management based on admin status in the account session, automatically adjusting component behavior. The dashboard’s appearance matches the platform using the appearance API with variables for colors, fonts, and locale, and it receives automatic updates for new payment methods and compliance.
Harbor: Stripe’s AI-assisted prototyping tool
Harbor addresses a gap in Stripe’s AI-assisted workflows: designers needed dynamic information to assess stripe.com designs, but could not always justify a full engineering prototype. Built initially by one engineer in about 40 days, it lets designers describe an idea and use Stripe design systems and realistic mock data to generate shareable, browser-based prototypes without understanding code. Its agent writes a multi-file source tree, while Drydock compiles and renders React and TypeScript in the viewer’s browser; the agent can inspect pages, interact with elements, switch viewports, and iterate before publishing a single snapshot. Since May 2026, more than 3,000 Stripes have created 12,000 prototypes, and Harbor now integrates with other AI tools through MCP and Drydock’s standalone rendering contract, although live data and prototype-scoped state remain future goals.
Engineering Real-Time Mobile Personalization Across iOS, Android, React Native, and Flutter
Building real-time mobile personalization across iOS, Android, React Native, and Flutter required one architecture to handle different rendering models, lifecycles, identity flows, consent requirements, and release cycles without disrupting native app experiences. The team standardized schemas, event semantics, identity behavior, fallback handling, and SDK APIs, using bridge layers so React Native and Flutter could access native iOS and Android capabilities. Developers instrument apps once with constrained content zones and approved native components, while marketers configure templates, targeting, and content through Salesforce UI; metadata is published via a global CDN and rendered dynamically by the SDK. Data 360 performs server-side identity resolution and decisioning, limiting unnecessary raw profile storage on devices. An early customer implemented the system in two months and generated more than 150 million decisions within three weeks, while QR-code previews enabled testing against live profiles without app recompilation.
Adding Google Login to a React App with Auth0
The tutorial shows how to add Google login to a Vite-based React single-page app without implementing OAuth directly, using Auth0’s React SDK and Google social connection. It covers installing @auth0/auth0-react, creating an Auth0 Single Page Web Application, checking RS256 and OIDC Conformant settings, registering callback, logout, and web-origin URLs, and supplying the domain and client ID through Vite environment variables. The React code wraps the app in Auth0Provider, uses useAuth0 for loading and authentication state, and calls loginWithRedirect with connection: 'google-oauth2' to bypass provider selection. For production, it explains replacing Auth0’s shared development keys with Google Cloud credentials whose origin and redirect URI target the Auth0 domain, then storing them in the Auth0 social connection. It also points to route protection with withAuthenticationRequired, API access tokens from getAccessTokenSilently, and exact redirect-URI matching as important follow-on considerations.
TypeScript 7 in WebStorm: Faster Coding Assistance for Angular and React, No Migration Required
WebStorm 2026.2 introduces stable TypeScript 7 support for React and Angular projects, while teams can retain older TypeScript versions when infrastructure constraints require them. TypeScript 7 replaces the Node.js-based language service with a Go-based engine intended to provide equivalent or better coding assistance with less work. WebStorm integrates the engine natively rather than through its existing plugin layer, with the largest gains expected in larger codebases. For Angular, its Kotlin-based template transpiler and adapted Volar source-mapping solution translate requests between original and generated code, enabling inline template assistance; on Kibana, project load time fell from about 12 seconds to 3 seconds. React projects can select TypeScript 7 in preferences and use the Go-based engine, while Vue support remains under development.
Build a real-time market data app with ClickHouse and Massive
The post presents a real-time market-data application that ingests trade and quote ticks from Massive and stores them in ClickHouse for low-latency querying and visualization. It distinguishes quotes, which contain bid and ask prices and sizes, from trades, which record executed price, size, timestamps, and related fields. The implementation uses an authenticated Massive WebSocket subscription, Node.js ingestion, separate ClickHouse MergeTree tables ordered by symbol and one-minute timestamp buckets, and React charts. It also describes materialized-view aggregation for visualization and supplies a runnable repository with setup, build, start, admin, and synthetic-seed paths; the conclusion recommends durable delivery, replay, authentication, and workload-specific tuning before production use.
Welcoming Laura Beatris, our new Software Engineer
Resend announces that Laura Beatris is joining its team as a Software Engineer. She previously worked at Clerk and WorkOS, where she shipped authentication products with an emphasis on developer experience, and she has spoken on React, TypeScript, and learning in public. Laura describes a path that began with learning Python from free tutorials, continued through a technical degree and early project-building after repeated internship rejections, and eventually led to Amsterdam in 2021. At Resend, she says she was drawn to products where details matter, a culture of learning in public, and a new problem space for improving her developer-experience judgment; her advice is to learn, create, then teach, because teaching helps knowledge stick.
Sunsetting new.email
Resend is sunsetting new.email, which will remain available for template exports until August 7, 2026, before stopping new prompts and sends. Launched in February 2025, the tool let anyone create email templates with natural language, using React Email components and deliverability lessons from sending millions of emails daily; its goal was consistent, beautiful, responsive email. Resend says the core bet was right, but a separate brand and stack—repository, infrastructure, deployment, and operational conventions—made the product harder to maintain, while market feedback showed users did not need new templates constantly. The product’s ideas are moving into the Resend editor, which offers URL-based brand extraction, AI block rewriting, LLM content review, and email creation and editing through the Resend MCP server.
6 Tips for Accessible Emails
The Email Markup Consortium’s 2026 report analyzed 376,348 emails and found that only eight passed every accessibility check, while nearly all failures included Serious or Critical issues. The post focuses on six largely mechanical improvements: setting lang and dir, marking layout tables role=“presentation”, creating a heading hierarchy, writing descriptive link and image text, adding a specific title element, and meeting a 4.5:1 color-contrast ratio. It gives HTML examples, notes that clients may strip attributes from the html element, and distinguishes meaningful images from decorative ones that need empty alt text. It also describes updated React Email defaults for language, direction, image alt text, Markdown tables, and titles, while leaving content judgments such as headings, links, and contrast to authors.
Faire doubles PR throughput with Cursor Cloud Agents
Faire reports doubling weekly PR throughput after adopting Cursor Cloud Agents, replacing its in-house Samurai background-agent system and putting an 18-month MobX-to-native-React-state migration under one engineer’s coordination. Cloud agents run in isolated development environments with the dependencies, internal services, credentials, and tooling needed to write, test, verify, and ship changes; Faire configures these through agent-led repository onboarding or Dockerfiles. The team also uses more than 25 Cursor Automations for over 2,000 autonomous weekly runs, including Slack bug triage, CI-failure fixes, and PR routing. For the migration, Faire’s Swarm scraper records MobX usages in S3 and dispatches tasks sequentially to isolated virtual machines, while another cloud-agent effort created five stacked preview-build PRs in under a day. Faire says engineering output is approaching two to three times its previous level and is now examining bottlenecks elsewhere in product development.
National Australia Bank accelerates legacy migrations with Cursor
NAB standardized 6,000 developers on Cursor after evaluating Amazon Q and GitHub Copilot, and is expanding access to more than 10,000 technology employees. The bank uses Cursor across legacy modernization and new development: BizCalc's Silverlight/.NET monolith is being refactored into Java microservices and React, while Assembly-based core-banking programs are being migrated using generated flowcharts and business summaries. Engineers use Ask Mode, Plan Mode, custom NAB CEL skills, Composer, and Opus coding models to document systems, produce requirements and API specifications, parallelize implementation, and test changes. NAB reports that both modernization efforts are progressing three times faster than expected, while a hardware-agnostic payment app was built in under three weeks rather than four months; one team reported a 5–8x velocity improvement.
Launch Week 6: Wrap Up
Launch Week 6 concluded with five feature releases and one announcement covering email automation, content creation, developer tooling, tracking, and community events. Automations orchestrates lifecycle emails from application events with delays, waits, conditions, test runs before publishing, and real-time visibility into runs. The AI-extended editor turns URLs into on-brand drafts, supports inline block editing and mistake detection, and connects to agentic stacks through the Resend MCP server, while CLI 2.0 adds React-file sending, automation and event management, webhook listening, and AI-agent skills across more than 50 API commands. Custom tracking domains support click and open tracking, React Email 6 adds an embeddable editor and extensions API, and Resend Forward was announced as a San Francisco conference scheduled for October 21.
Resend CLI 2.0
Resend CLI 2.0 gives terminal-based access to the full Resend API and adds four features: sending emails from local React (.tsx/.jsx) files, managing automations and events, one-command webhook listening with automatic tunneling, and Agent Skills for autonomous API interaction. Users can now create automation runs, inspect results, and build multi-step workflows directly from the command line. The webhook listener automatically sets up a tunnel and forwards all event types to a local server, eliminating the need for separate tunneling tools. Agent Skills provide a structured interface enabling AI agents to independently manage their own inbox, sign up for accounts, receive confirmation emails, process attachments, and respond without manual intervention. Other improvements include programmatic log retrieval, enhanced API key storage via the system keychain (macOS Keychain, Linux Secret Storage, Windows Credential Manager), and the deprecation of the team command in favor of auth.
Interact with agent-created visualizations in canvases
Cursor introduces canvases, allowing agents to represent information through interactive visual interfaces instead of chat text or markdown. In the Agents Window, these durable artifacts sit alongside tools including the terminal, browser, and source control, and agents can build dashboards, PR review interfaces, architecture diagrams, and eval-failure investigations. Canvases use a React-based UI library with first-party tables, boxes, diagrams, and charts, plus existing Cursor components such as diffs and to-do lists; skills can teach agents to create specific canvas types. Cursor reports that combining observability data from Datadog, Databricks, and Sentry MCPs with local debug files makes time-series analysis easier, while eval skills group rollout failures to expose hidden harness bugs. The company is also using canvases to visualize autoresearch progress and current hypotheses during client-performance experiments.
A visual editor for the Cursor Browser
Cursor has released a visual editor for its Browser that combines a web app, codebase, and visual editing tools in one window. Users can drag rendered elements across the DOM tree, inspect React component props, adjust styles and design-system color tokens, and interactively test layout, typography, and component variants. Point-and-prompt interactions let users select interface elements and describe changes such as resizing, recoloring, or reordering; agents run these prompts in parallel and make changes live within seconds. Once a visual arrangement is settled, the agent locates relevant components and updates the underlying code. The release positions the editor as a way to connect visual design and coding more directly, with features documented for Cursor 2.2.
Create a React PWA with Social Login Authentication
The tutorial builds a React Progressive Web App (PWA) called Lister, combining offline support with authentication through Okta and Google Social Login. It creates an Okta OIDC single-page application, configures Authorization Code and Refresh Token grants, sets localhost redirect URIs, and wires Okta React and AuthJS into React Router routes. The implementation uses environment variables for the Okta domain and client ID, OAuth 2.0 and OpenID Connect scopes including openid, profile, email, and offline_access, and a Vite PWA plugin to provide a manifest, service worker, and installable behavior. Authenticated users receive a todo-list interface with CRUD operations, while the article notes that production deployments would need more advanced service-worker configuration and a proper database.
Testing a React App in Chrome with Heroku CI
The article presents a walkthrough for automating end-to-end browser tests for a React application in Heroku CI rather than relying on manual local testing. The sample app uses Jest and Puppeteer to check navigation to Puppeteer Documentation, retention of text entered into a form, and the greeting shown after submission, with headless Chrome supplied by the Chrome for Testing Heroku Buildpack. Local execution initially exposes a mismatch between the expected and received greeting, then passes after the application is fixed; a streamlined command starts the server and runs the suite. Heroku CI is configured with an app.json file containing Chrome for Testing and Node.js buildpacks, plus a test script that runs start-server-and-test and the Jest/Puppeteer tests. Pushes to the connected GitHub repository trigger the suite.
Related topics
All topics →Weekly digest
The best engineering reads, once a week.