June 27, 2023 at 1:58:21 PM UTC

	Since	posts	replies	likes	reposts and quotes	views
Bluesky	May 2023	1,039	8,236	23,127	2,380
Mastodon	Nov 2022	2,399	29,156	55,396	16,820
GitHub	Jul 2010	179	5,777 3,520	33,866	3,317
npm	Jul 2014	139	1,546			75,991,720
YouTube	Dec 2015	30		1,203		32,713
Letterboxd	Mar 2026	55
Blog	Nov 2025	20
Hacker News	Jan 2011	59	575	802
All	Jul 2010	4,807	37,967	114,394	22,517	76,024,433

Next.js bundles a Canary version of React to support a feature that Next has marked as stable (app dir): https://nextjs.org/blog/next-13-4#nextjs-app-router

This follows React design goals: https://react.dev/blog/2023/05/03/react-canaries#tldr

However, the weak link here is that React doesn’t guarantee semver in Canary releases, so *of course* things are going to break. If any deps up the chain break semver, your release also breaks semver.

Fred is right to call this out: https://twitter.com/FredKSchott/status/1673342700651704330

10 replies

Marty Party 7 min later

@zachleat interesting. I looked at app router a few weeks ago and deemed it to be too big a port to take on at this time. Glad I did I shall pump the breaks harder on us using it
1. Zach Leatherman 8 min later
  
  @martycoote so many weird choices happening there
Kevin Pennekamp 14 min later

@zachleat oh lord… this is really going downhills. Just looking at the react of Mark on this gives me the creeps. React says use with caution, but vercel basically says: “trust us, we tested it, react is wrong, it is stable”
1. Zach Leatherman 17 min later
  
  @kevtiq yeah, it isn’t rigorous.
  1. Mikael Gramont 1 hr later
    
    @zachleat @kevtiq “trust us, we tested it, react is wrong, it is stable” is exactly what I gathered too, but kept thinking that was too crazy, so I must have misunderstood.
    1. Kevin Pennekamp 2 hr later
      
      @mikamtb @zachleat the messaging is inconsistent from React’s side.
      - The canary version is “ready for adoption for frameworks”,
      - but it had “near to finish” features (so they can change).
      - A core member stated the current canary version does not follow the new process yet.
      - They say they cannot release “stable features” to the stable channel as new features are dependent on each other. But they are good enough for frameworks?
      1. Mikael Gramont 14 hr later
        
        @kevtiq @zachleat
        Best to stick to the next-to-latest version then. #NextToLatest.js
Emanuele Stoppa 7 hr later

@zachleat yeah, Next.js isn't handling their versioning very well, especially this app dir.
To be honest it's a framework that I don't trust anymore. They deprecated and removed features without a particular reason, only to push their Vercel products.
1. Zach Leatherman 8 hr later
  
  @ematipico what features?
  1. Emanuele Stoppa 15 hr later
    
    @zachleat there was this feature called `target: serverless` that would allow to emit pages as artefacts for serverless environments. It was deprecated and removed without explanation