null is not an object (evaluating 'b.parentNode') in production

[Fonger]

I don't know how to reproduce but it seems it only happen in Safari.

My Sentry keeps receiving reports from users like this

app:///xxxx(path-to-the-page) in $RS at line 1:119385

with error message:

null is not an object (evaluating 'b.parentNode')

I search the HTML document reporting the error, I see

<script>$RS=function(a,b){a=document.getElementById(a);b=document.getElementById(b);for(a.parentNode.removeChild(a);a.firstChild;)b.parentNode.insertBefore(a.firstChild,b);b.parentNode.removeChild(b)};

This indicates that param b, which is document.getElementById(b) is somehow null.

This code seems to be replated to streaming rendering and this is how the server-sent data push to the client suspense <template id="xxx"/> slot.

Is it possible? how come $RS() calling tries to to insert a non-existing template slot id?

I can't produce it but sentry logs indicate the following environments. All of them are from Sarari.

Note these data with 3% sample rate and this indicating that the actual affected users are 33 times larger than this. And it's within 24hr.

[Behnoudmst]

I am having same issue on Nextjs 14.2

[icyJoseph]

This seems to come from React itself... 🤔 Could it be a browser extension, or perhaps people who tell their browser to translate the site?

• next.js/packages/next/src/compiled/react-dom/cjs/react-dom-server.node.production.js

  Lines 2277 to 2282 in 09aa303

  	var completeSegmentScript1Full = stringToPrecomputedChunk(
  	'$RS=function(a,b){a=document.getElementById(a);b=document.getElementById(b);for(a.parentNode.removeChild(a);a.firstChild;)b.parentNode.insertBefore(a.firstChild,b);b.parentNode.removeChild(b)};$RS("'
  	),
  	completeSegmentScript1Partial = stringToPrecomputedChunk('$RS("'),
  	completeSegmentScript2 = stringToPrecomputedChunk('","'),
  	completeSegmentScriptEnd = stringToPrecomputedChunk('")\x3c/script>');

[icyJoseph]

@Fonger @Behnoudmst I went over to the React repo, and found this, facebook/react#25710

Apparently, wrapping the entire HTML document with a Suspense boundary, could cause this issue: facebook/react#25710 (comment)

[vitalyiegorov]

facing same issue with the Next 15.3.1

[serhii-kucherenko]

Same with the 15.1.6