@sapphi-red I'm wondering if for the rolldown builtin refresh wrapper you access the ast and do something like:

let only_react_comp =
  !has_refresh &&
  // pseudo JS code
  ast.body.statements.some(
    (s) =>
      s.kind === 'ClassDeclaration' &&
      s.extends.name.match(/^(?:React\.)?(?:Pure)?Component$/),
  )

I guess we can also fix the error by changing this window with globalThis:

@sapphi-red I'm wondering if for the rolldown builtin refresh wrapper you access the ast and do something like:

It doesn't have access to the AST here since the transform hook is string-in-string-out.

I guess we can also fix the error by changing this window with globalThis

For the past years I've found benefits to keep using window there because it allowed to find cases with bad configuration or people over bundling files in their workers. The idea was also that if one day we figure out HMR for workers, it will not be a breaking change currently the client can't run there.

But maybe the chance is so low that we get there that we should make it no-op to load the HMR client in a worker

It doesn't have access to the AST here since the transform hook is string-in-string-out
And I suppose it would cost to much memory to pass it around via some kind of context?