Mrhs121 commented on issue #18181: URL: https://github.com/apache/dolphinscheduler/issues/18181#issuecomment-4277656859
Thanks for the clarification. I also tried downgrading pnpm locally to v7 (`npm install -g pnpm@7`), and with that version the project installs successfully. However, from the installation logs I observed that the actual installed version is: `+ @types/lodash 4.14.195` This does not satisfy the declared range `^4.18.0`, which suggests that pnpm v7 is simply using the existing lockfile without re-resolving dependencies. I also checked the latest CI run: https://github.com/apache/dolphinscheduler/actions/runs/24630365185/job/72016559462?pr=18183 The CI explicitly installs pnpm v7: `npm install pnpm@7 -g` And the logs show: * `Lockfile is up to date, resolution step is skipped` * `@types/lodash 4.14.195` is installed <img width="478" height="320" alt="Image" src="https://github.com/user-attachments/assets/3140b3ca-f22f-4b88-9f99-b78bc3c00482"; /> This indicates that CI is also relying on the existing lockfile and not re-resolving dependencies. However, in commit e827f2f, `@types/lodash` was updated to: `"@types/lodash": "^4.18.0"` This version range is invalid, because the latest published version of `@types/lodash` is currently `4.17.24`, and there is no `4.18.x` release. So the behavior seems to be: * pnpm v7 + existing lockfile → install succeeds (using 4.14.195) * newer pnpm → lockfile is considered incompatible → dependencies are re-resolved * re-resolution fails because `@types/lodash@^4.18.0` does not exist In other words, newer pnpm is not introducing a new issue, but exposing an existing inconsistency between `package.json` and the lockfile. As a possible fix, it might be worth updating the dependency to a valid range (e.g. ^4.17.24) and regenerating the lockfile, so that installation works consistently across different pnpm versions without relying on the existing lockfile behavior. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
