The dev script uses cross-env but it's not listed in devDependencies. While this might work if it's available from the workspace root, it's a best practice to explicitly declare all dependencies used in package scripts. Add cross-env to devDependencies or use an alternative approach that doesn't require cross-env (such as using package.json scripts that work cross-platform without the tool).

The peerDependency uses "workspace:^" for @rstest/core, but when this package is published to npm, workspace: protocol won't be valid. This should be changed to a standard semver range like "^0.7.8" or "workspace:^" should be transformed during the publish process. Check that your build/publish pipeline properly resolves workspace: dependencies to actual version numbers, or use a standard version range.

The unmount function doesn't remove the container from the tracking arrays (mountedContainers and mountedRootEntries). This creates a memory leak where unmounted containers remain tracked. When a user calls unmount directly (instead of relying on cleanup), the container and root stay in memory, and subsequent cleanup calls will attempt to unmount already-unmounted roots. The unmount function should remove the container from both mountedContainers Set and mountedRootEntries array after unmounting.

The renderHook implementation updates result.current inside a useEffect, which runs after the initial render. This means result.current will be undefined immediately after the first render, until the useEffect fires. This could cause issues if tests access result.current synchronously before effects run. The value should be assigned synchronously during render, not in useEffect. Change the implementation to assign result.current directly: result.current = value; instead of wrapping it in useEffect.