This can cause long file names (URLs) to be truncated which in turn will break named hooks code (since it needs to load those file names).
(it's been disconnected by Fast Refresh), and calls untrackFiberID() to clear it from the Map.
     3. React flushes pending passive effects before it runs the next render,
        which logs an error or warning, which causes a new ID to be generated for this Fiber.
     4. DevTools now tries to unmount the old Component with the new ID.
    
     The underlying problem here is the premature clearing of the Fiber ID,
     but DevTools has no way to detect that a given Fiber has been scheduled for Fast Refresh.
     (The "_debugNeedsRemount" flag won't necessarily be set.)
    
     The best we can do is to delay untracking by a small amount,
     and give React time to process the Fast Refresh delay.
    untrackFibersSet.add(fiber);
    if (untrackFibersTimeoutID === null) {
      untrackFibersTimeoutID = setTimeout(untrackFibers, 1000);
    }
  }
  const untrackFibersSet: Set<Fiber> = new Set();
  let untrackFibersTimeoutID: TimeoutID | null = null;
  function untrackFibers() {
    if (untrackFibersTimeoutID !== null) {
      clearTimeout(untrackFibersTimeoutID);
      untrackFibersTimeoutID = null;
    }
    untrackFibersSet.forEach(fiber => {
      const fiberID = getFiberIDUnsafe(fiber);
      if (fiberID !== null) {
        idToArbitraryFiberMap.delete(fiberID);
         A
        clearErrorsForFiberID(fiberID);
        clearWarningsForFiberID(fiberID);