JMIX 2.7.4 - Pnpm install has exited with non zero status. Some dependencies are not installed. Check pnpm command output

Dear JMIX team,

We are facing an error of Pnpm install has exited with non zero status after upgrading to 7.2.4

We have review other topics in the forum and follow the instructions like deleting these folders.

src/main/bundles
build
node_modules
frontend/generated

We also try to delete the whole project and donwloaded again, but we are still with the same issue.

¿Do you have any additional idea what to do?

Thank you

026-01-30T11:59:19.545+01:00 ERROR 21820 — [in-dev-server-1] c.v.f.s.frontend.TaskUpdatePackages : Command C:\Users\SGCP0178\.vaadin\node\node.exe C:\Users\SGCP0178\.vaadin\node\node_modules\npm\bin\npx-cli.js --yes --quiet pnpm --shamefully-hoist=true --ignore-scripts install failed:
WARN 5 deprecated subdependencies found: backbone-undo@0.2.6, glob@7.2.3, inflight@1.0.6, source-map@0.8.0-beta.0, sourcemap-codec@1.4.8
EBUSY EBUSY: resource busy or locked, rename ‘C:\Users\SGCP0178\IdeaProjects\gestion-de-informes\pnpm-lock.yaml.3719996912’ → ‘C:\Users\SGCP0178\IdeaProjects\gestion-de-informes\pnpm-lock.yaml’

2026-01-30T11:59:19.545+01:00 ERROR 21820 — [in-dev-server-1] c.v.f.s.frontend.TaskUpdatePackages : >>> Dependency ERROR. Check that all required dependencies are deployed in pnpm repositories.
2026-01-30T11:59:19.584+01:00 ERROR 21820 — [nio-8080-exec-1] i.j.f.exception.UiExceptionHandlers : There is no io.jmix.flowui.exception.UiExceptionHandler can handle the exception

java.lang.IllegalStateException: com.vaadin.flow.server.ExecutionFailedException: Pnpm install has exited with non zero status. Some dependencies are not installed. Check pnpm command output
at com.vaadin.base.devserver.AbstractDevServerRunner.getCause(AbstractDevServerRunner.java:795) ~[vaadin-dev-server-24.9.10.jar:na]
at com.vaadin.base.devserver.AbstractDevServerRunner.getCause(AbstractDevServerRunner.java:791) ~[vaadin-dev-server-24.9.10.jar:na]
at com.vaadin.base.devserver.AbstractDevServerRunner.handleRequestInternal(AbstractDevServerRunner.java:640) ~[vaadin-dev-server-24.9.10.jar:na]
at com.vaadin.base.devserver.DevBundleBuildingHandler.handleRequest(DevBundleBuildingHandler.java:94) ~[vaadin-dev-server-24.9.10.jar:na]
at com.vaadin.flow.server.VaadinService.handleRequest(VaadinService.java:1879) ~[flow-server-24.9.10.jar:24.9.10]
at com.vaadin.flow.server.VaadinServlet.service(VaadinServlet.java:398) ~[flow-server-24.9.10.jar:24.9.10]
at com.vaadin.flow.spring.SpringServlet.service(SpringServlet.java:106) ~[vaadin-spring-24.9.10.jar:na]
at jakarta.servlet.http.HttpServlet.service(HttpServlet.java:614) ~[jakarta.servlet-api-6.0.0.jar:6.0.0]

We solved the issue after running.

  1. Gradle clean.
  2. Vaadin clean,
  3. Gradle assemble
  4. Vaadin FrontEnd

Most likely there was no need to to run the 4 of them, but now is solved.