Cannot work with JMix 2.3

Support
#1

I am on a new PC where i cannot run my application after update to JMIX 2.3.1

> 2024-07-18T08:16:20.721+02:00 ERROR 8404 --- [onPool-worker-1] c.v.f.s.frontend.TaskUpdatePackages      : Command `C:\Users\Asus\.vaadin\node\node.exe C:\Users\Asus\.vaadin\node\node_modules\npm\bin\npx-cli.js --yes --quiet pnpm --shamefully-hoist=true --ignore-scripts install` failed:
> ?WARN? GET https://registry.npmjs.org/semver/-/semver-7.6.3.tgz error (ERR_PNPM_EPERM). Will retry in 10 seconds. 2 retries left.
> ?WARN? GET https://registry.npmjs.org/@babel/core/-/core-7.24.9.tgz error (ERR_PNPM_EPERM). Will retry in 10 seconds. 2 retries left.
> ?WARN? GET https://registry.npmjs.org/@babel/compat-data/-/compat-data-7.24.9.tgz error (ERR_PNPM_EPERM). Will retry in 10 seconds. 2 retries left.
> ?WARN? GET https://registry.npmjs.org/semver/-/semver-7.6.3.tgz error (ERR_PNPM_EPERM). Will retry in 1 minute. 1 retries left.
> ?WARN? GET https://registry.npmjs.org/@babel/generator/-/generator-7.24.10.tgz error (ERR_PNPM_EPERM). Will retry in 10 seconds. 2 retries left.
> ?WARN? GET https://registry.npmjs.org/terser/-/terser-5.31.3.tgz error (ERR_PNPM_EPERM). Will retry in 10 seconds. 2 retries left.
> ?WARN? GET https://registry.npmjs.org/@babel/types/-/types-7.24.9.tgz error (ERR_PNPM_EPERM). Will retry in 10 seconds. 2 retries left.
> ?WARN? GET https://registry.npmjs.org/@babel/helper-module-transforms/-/helper-module-transforms-7.24.9.tgz error (ERR_PNPM_EPERM). Will retry in 10 seconds. 2 retries left.
> ?WARN? GET https://registry.npmjs.org/@babel/core/-/core-7.24.9.tgz error (ERR_PNPM_EPERM). Will retry in 1 minute. 1 retries left.
> ?WARN? GET https://registry.npmjs.org/is-core-module/-/is-core-module-2.15.0.tgz error (ERR_PNPM_EPERM). Will retry in 10 seconds. 2 retries left.
> ?WARN? GET https://registry.npmjs.org/@types/node/-/node-20.14.11.tgz error (ERR_PNPM_EPERM). Will retry in 10 seconds. 2 retries left.
> ?WARN? GET https://registry.npmjs.org/@swc/core-win32-x64-msvc/-/core-win32-x64-msvc-1.7.0.tgz error (ERR_PNPM_EPERM). Will retry in 10 seconds. 2 retries left.
> ?WARN? GET https://registry.npmjs.org/node-releases/-/node-releases-2.0.17.tgz error (ERR_PNPM_EPERM). Will retry in 10 seconds. 2 retries left.
> ?WARN? GET https://registry.npmjs.org/electron-to-chromium/-/electron-to-chromium-1.4.829.tgz error (ERR_PNPM_EPERM). Will retry in 10 seconds. 2 retries left.
> ?WARN? 5 deprecated subdependencies found: glob@7.2.3, inflight@1.0.6, rollup-plugin-terser@7.0.2, sourcemap-codec@1.4.8, workbox-google-analytics@7.0.0
> ?ERR_PNPM_EPERM? EPERM: operation not permitted, stat 'D:\.pnpm-store\v3\files\81\6440dcc4ebc4aeb793ce86c5a6deb24cb09316e999d5e101b33368236ccdf705c385b40bafaaa0c1dd748e68d8ba19e219f7baa66aac6c822d6eafb60d9592'
> 
> This error happened while installing a direct dependency of D:\JMix\CRM
> ?WARN? GET https://registry.npmjs.org/@babel/compat-data/-/compat-data-7.24.9.tgz error (ERR_PNPM_EPERM). Will retry in 1 minute. 1 retries left.

The execution of
C:\Users\Asus>C:\Users\Asus\.vaadin\node\node.exe C:\Users\Asus\.vaadin\node\node_modules\npm\bin\npx-cli.js --yes --quiet pnpm --shamefully-hoist=true --ignore-scripts install

Der Befehl ““node”” ist entweder falsch geschrieben oder
konnte nicht gefunden werden.

Changing in the correct subdir
C:\Users\Asus\.vaadin\node>node.exe C:\Users\Asus\.vaadin\node\node_modules\npm\bin\npx-cli.js --yes --quiet pnpm --shamefully-hoist=true --ignore-scripts install
ERR_PNPM_NO_PKG_MANIFEST No package.json found in C:\Users\Asus.vaadin\node

Deleting .vaadin does not help either.

Edition Windows 11 Pro
Version 22H2
Installiert am ‎30.‎10.‎2022
Betriebssystembuild 22621.3880
Leistung Windows Feature Experience Pack 1000.22700.1020.0

Any hints ?

#3

Hi,

Unfortunately, I cannot reproduce the problem. As an option, try to remove node_modules and src/main/bundles folders and restart the project.

Regards,
Gleb

#5

Hi Gleb

I did try a lot including deleting and reinstalling IntelliJ and JMix from the scratch.

The only solution was at the end to delete the .pnpm-store directory …

We can delete this thread or keep it for some people which will perhaps have the same problem ?

Thank you for your try

Regards

Felix

#6

No need to delete the topic, it may be helpful for people with the same problem. Thank you for your solution.

Regards,
Gleb