From f5bf08e7f941fbd8bf26bc08bd9d5d8ef3e402cb Mon Sep 17 00:00:00 2001 From: Ariful Hoque Date: Sun, 19 Jul 2026 19:49:18 +0600 Subject: [PATCH] Allow React 19 in the peer range MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The package declared peer react/react-dom ^18.0.0. Consumers on React 19 cannot install it at all under npm, which fails the resolution outright: Found: react@19.2.7 Could not resolve dependency: peer react@"^18.0.0" from @wedevs/plugin-ui@2.0.0 pnpm installs anyway but then builds this package's nested tree against a React it was not resolved for, and the prepare step fails on CI with a webpack parse error that gives no hint of the real cause. Nothing here depends on React 18 specifics — FlyHR already runs this library against React 19 in production — so the ceiling is stale rather than real. Verified: builds clean and a React 19 consumer installs without ERESOLVE. --- package.json | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/package.json b/package.json index de04e5a..66c1123 100644 --- a/package.json +++ b/package.json @@ -57,8 +57,8 @@ "prepare": "npm run build" }, "peerDependencies": { - "react": "^18.0.0", - "react-dom": "^18.0.0" + "react": "^18.0.0 || ^19.0.0", + "react-dom": "^18.0.0 || ^19.0.0" }, "dependencies": { "@base-ui/react": "^1.1.0",