vercel.com observed a bug where a stylesheet hoisted using a `precedence` was reordered after an update. This is not correct semantics (once a hoisted stylesheet is inserted it should remain in place until removed)

Investigating the React implementation I observed that if you insert a hoisted stylesheet during a synchronous render and later render a new reference to that stylesheet in a transition React incorrectly considers the stylesheet not loaded and tries to coordinate it's loading the the commit. This is erroneous as once a stylesheet is in the DOM it should never be re-inserted (moved).
instance,
      count: 1,
      state: null,
    };
    scripts.set(key, resource);
    return;
  }
}
function preinitModuleScript(
  src: string,
  options?: ?PreinitModuleScriptOptions,
) {
  if (!enableFloat) {
    return;
  }
  const ownerDocument = getDocumentForImperativeFloatMethods();
  if (src) {
    const scripts = getResourcesFromRoot(ownerDocument).hoistableScripts;
    const key = getScriptKey(src);
    
    let resource = scripts.get(key);
    if (resource) {
      
      
      return;
    }
    
    let instance: null | Instance = ownerDocument.querySelector(
      getScriptSelectorFromKey(key),
    );