Matt Brophy

Matt Brophy

@brophdawg11.com

Helping folks build better websites Remix/React Router @Shopify ๐Ÿ’ฟ Philadelphia

845 followers211 following503 posts

React Router v8 is ready for prerelease testing!

React Router@reactrouter.com

React Router v8 is now in prerelease mode! Please give it a try and let us know if you running into any issues. Learn more by reading the changelog: github.com/remix-run/re...

Matt Brophy reposted

We just published 7 CVEs identifying security vulnerabilities in React Router and Remix v2 We recommend updating to the latest appropriate versions: - React Router v7 -- 7.16.0 - React Router v6 -- 6.30.4 - Remix v2 -- 2.17.5 Details, links, and package ranges are listed below

Matt Brophy reposted

Remix 3.0.0-beta.2 is available - 140 commits since beta.0 - nearly 30 bug fixes and stability improvements - tons of API polish - reduced client JS payload - improved documentation - improved template/getting started experience Check out the changelog for more details: github.com/remix-run/re...

github.comgithub.com

Matt Brophy reposted

React Router 7.15.1 is now available! This release introduces a new useRouterState (unstable) hook which consolidates access to active and pending router states. We've also corrected useFetchers to now return a stable identity and fixed several other outstanding bugs.

Apps should see some nice perf improvements with RR 7.15.0 - give it a shot and let us know!

React Router@reactrouter.com

React Router v7.15.0 is now available - Stabilized APIs in preparation for v8 - Route matching optimizations for Framework/Data Mode - ~10-30% faster server-side request handling in benchmarks - Bug fixes around revalidation, Scripts nonce, and more reactrouter.com/changelog#v7...

Matt Brophy reposted

Finally a great use of AI for my daily routine - Prompted Playlists on Spotify is a feature I've wanted for a long time. I don't have the energy/memory to go through and manually curate playlists (I still mostly listen to 90s music) so really hoping this proves to work well

Matt Brophy reposted

The Policy Director for the President of the United States said that the VA nurse was murdered because he was an โ€œassassin.โ€ And not one Republican in Congress will say a god damn word about because they are spineless cowards.

Matt Brophy reposted

Republicans are in favor of having a gun to defend yourself from a tyrannical government unless you have a gun to defend yourself from a tyrannical government

Radley Balko@radleybalko.bsky.social

Pretti clearly did not brandish his gun. Which means the government is saying he was killed for legally exercising his right to carry. Itโ€™s as clear-cut a violation of the Second Amendment as I can possibly imagine. And weโ€™re about to see the bulk of the gun rights crowd defend his murder.

Matt Brophy reposted

This is the most astonishing graph of what the Trump regime has done to US science. They have destroyed the federal science workforce across the board. The negative impacts on Americans will be felt for generations, and the US might never be the same again. www.nature.com/immersive/d4...

Scumbags

Radley Balko@radleybalko.bsky.social

A few days ago, Fox News was whining about ICE agents getting heckled at a Mexican restaurant in Minneapolis. Meanwhile, in the town of Willmar, ICE agents had lunch at a Mexican restaurant, waited until it closed, then confronted and arrested three workers as they left.

Matt Brophy reposted

We just published 6 CVEs identifying security vulnerabilities in React Router and Remix v2 We recommend updating to the latest appropriate versions: React Router v7 -- 7.12.0 React Router v6 -- 6.30.3 Remix v2 -- 2.17.2 Details, links, and package ranges are listed below

Matt Brophy reposted

Replying to @react.dev

We found that the fix to address the DoS vulnerability in React Server Components (CVE-2025-55184) was incomplete and does not prevent an attack in a specific case. This is disclosed as CVE-2025-67779. New patches are available now, please update immediately.

Matt Brophy reposted

Researchers have found two new vulnerabilities in React Server Components while attempting to exploit the patches last week. These are new issues, separate from the critical CVE last week. The patch for React2Shell remains effective for the Remote Code Execution exploit.

I've heard folks express concern about React Router since the Remix 3 announcement Some variation of "is it on hold?"/"is it a secondary focus?"/"will it stop getting features?" etc No, No, and No ๐Ÿ˜€ To back it up, I thought I'd put together a little "React Router Wrapped" for 2025 ๐ŸŽ„

View full thread

And here's a few other things in the pipeline that will likely land in early 2026: Call-site revalidation opt out (PR open) Consolidated `useRouterState()` hook (RFC) Typesafe fetcher alternatives (RFC) Contextual fetcher success/error handling (RFC) `<Link rewrite>` (RFC)

I've heard folks express concern about React Router since the Remix 3 announcement Some variation of "is it on hold?"/"is it a secondary focus?"/"will it stop getting features?" etc No, No, and No ๐Ÿ˜€ To back it up, I thought I'd put together a little "React Router Wrapped" for 2025 ๐ŸŽ„

View full thread

Sub-resource Integrity support (unstable future flag) Granular `route.lazy` object format `routeDiscovery` config option Automatic types for Future Flags Vite 7 support RSC support in Data and Framework mode (unstable) Client side `onError` handler (unstable) `fetcher.reset()` ...

Type-safe `useRoute` hook (unstable) Concurrent pre-rendering (unstable) Instrumentation APIs (unstable) Improved React 19 transition support (unstable) ...

I've heard folks express concern about React Router since the Remix 3 announcement Some variation of "is it on hold?"/"is it a secondary focus?"/"will it stop getting features?" etc No, No, and No ๐Ÿ˜€ To back it up, I thought I'd put together a little "React Router Wrapped" for 2025 ๐ŸŽ„

View full thread

Here's an incomplete list of features we landed in 2025: Type safe `href` Prerendering w/ a SPA Fallback SPA Mode root `loader` support Split Route Modules (future flag) Vite Environment API Support (future flag) Client Side `context` support Server- and Client-side Middleware (future flag) ...

I've heard folks express concern about React Router since the Remix 3 announcement Some variation of "is it on hold?"/"is it a secondary focus?"/"will it stop getting features?" etc No, No, and No ๐Ÿ˜€ To back it up, I thought I'd put together a little "React Router Wrapped" for 2025 ๐ŸŽ„

View full thread

This new model accomplishes 3 main things IMO: - More accurately ship what the users are asking for via public RFC upvotes - More successful community contributions because the APIs + implementation are discussed in RFCs ahead of time - Earlier community feedback via alpha/beta feature releases

Looking back at 2025, we shipped 36 releases! 31 v7.x releases and 5 v6.x releases That's an average of **3 per month**, and I expect we'll do another one before EOY

I've heard folks express concern about React Router since the Remix 3 announcement Some variation of "is it on hold?"/"is it a secondary focus?"/"will it stop getting features?" etc No, No, and No ๐Ÿ˜€ To back it up, I thought I'd put together a little "React Router Wrapped" for 2025 ๐ŸŽ„

Remember, it's not just Michael and Ryan anymore - we've got a whole team working on RR, and even a few external contributors on the Steering Committee nowadays

Matt Brophy reposted

The new fetcher.unstable_reset function is so nice Previously, to accomplish this little UX I'd have to pull in useState and keep another state in sync. Now I can just do this: onChange={() => { if (isSuccess) { fetcher.unstable_reset(); } }} Thanks @brophdawg11.com

Matt Brophy reposted

This is RSC-specific, and should be called out as such. There's *tons* (the majority, I'd wager) of React sites that are completely unaffected by this. They should probably upgrade regardless, but for those that may not be in a position to do so, they might not need to freak out.

Matt Kane@mk.gg

The original React2shell PoC is now public. This is as bad as it gets โ€“ full RCE. You must upgrade now. There are mitigations in place in CDNs including Cloudflare, Netlify, Vercel and AWS (and sites on Workers aren't vulnerable to this sort of attack), but there are variants in the wild now.

Matt Brophy reposted

The changed code is a small fraction of an open source contribution. Your commitment to understand the issue, how your proposed solution fits with the project, and be ready to own and push the review process forward is the biggest chunk of the work. Your effort is the contribution, not the code.

Getting older means more and more manual/analog things in your life โ˜•๏ธ Pour over coffee w/freshly ground beans โฑ๏ธ Mechanical watches ๐Ÿ”‰ Vinyl music ๐Ÿ““ Heck I'm even trying to use a handwritten daily notebook more I wonder what's next?