Reaction widget: React + Vite.
Backend: NextJs + MongoDB.
Hosting: VM in Hetzner Cloud.
Embeds as two script tags on any website — cacheable deps react and reactdom (gzip: 54.29 kB - to optimize or drop completely) + widget (gzip: 7.83 kB)

I'd just like to interject for a moment. What you're referring to as React, is in fact, React + ReactDOM, or as I've recently taken to calling it, React plus ReactDOM. React is not a complete library unto itself, but rather a core component of a fully functioning web development stack.

We've identified specific locations in the ReactDOM dev/prod bundles. When analyzing a sourcemapped app, we want to find those specific locations so we can insert instrumentation.

But, Next pre-builds combined artifacts, changes whitespace and parenthesization, etc. So, exact strings won't match.

That looks _doable_, technically... but that's definitely not how I _want_ to write this.

Specifically, we're trying to look for known copy-pasted fragments from the ReactDOM prod/dev artifacts to pinpoint locations, but whitespace may differ across app bundles. Would like to keep fragments as-is.

I think what we're trying to do is a lot more complex than that.

We have a few dozen very specific fragments we've collected, with arbitrary code inside. Usually full statements, but also some comma-separated expressions, etc.

The actual use case is finding locations in ReactDOM bundles.

Just looked at NPM download stats for ReactDOM, Next, Vite React, and CRA.

CRA usage peaked 2 years ago, but still significant. Vite React is 2/3 of Next. For Oct:

- ReactDOM: 108M
- Next: 33M
- Vite: 23.8M
- CRA: 12M

npm-stat.com/charts.html?...

more reason to provide migration paths!

A new React 19 feature that might have gone unnoticed:

ReactDOMStatic.prerender(<App />)

It's like the old renderToString API, but unlike renderToString, prerender will wait for Suspense boundaries to finish before returning the HTML.

React フォームに reCAPTCHA を導入する方法
analyzegear.co.jp/blog/2929
#React #ReactRouter #reCAPTCHA #PHP #ReactDOM #エックスサーバー #アナライズギア #analyzegear #AG

Also, I am not entirely sure what RSCs in a SPA looks like yet.

In a SPA, we can get everything from a CDN and I think ReactDOM handles .rsc and can start committing it to the DOM right away. So I don't think you would have to wait on react to render client components to see content.

Maybe?

speaking as someone who once wrote a whole project in machine code for fun: man fuck this lol

What you guys are referring to as React, is in fact, React/ReactDOM, or as I've recently taken to calling it, React plus ReactDOM. React is not an UI framework unto itself, but rather another free component of a fully functioning GUI system made useful by the underlying DOM handling library

okay idfk what im doing wrong i keep getting a "cannot read properties of null (reading useState)" error along with an invalid hook call. but i think im doing everything right ??? its not like its anything complicated here, just a button and a display

import React from 'react';
import ReactDOM from 'react-dom';

function Welcome() {
return <h1>Welcome!</h1>;
}

ReactDOM.render(
<Welcome/>,
document.getElementById('root')
);