Unable to run 'npm install'

[Twigzie]

As the title states, I'm not able to run the command.

I was successful before breaker released and I was running Windows 10 and node v21.6.2

I'm now running a clean install of Windows 11 and the most recent version of node which is 'v21.7.1'. I open the project in VSCode, run 'npm install' and get this:

PS (fork directory)> npm install
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: 'loa-details@1.4.25',
npm WARN EBADENGINE required: { node: '^18', npm: '>= 6.13.4', yarn: '>= 1.21.1' },
npm WARN EBADENGINE current: { node: 'v21.7.1', npm: '10.5.0' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@quasar/app-vite@1.2.2',
npm WARN EBADENGINE required: {
npm WARN EBADENGINE node: '^24 || ^22 || ^20 || ^18 || ^16 || ^14.19',
npm WARN EBADENGINE npm: '>= 6.14.12',
npm WARN EBADENGINE yarn: '>= 1.17.3'
npm WARN EBADENGINE },
npm WARN EBADENGINE current: { node: 'v21.7.1', npm: '10.5.0' }
npm WARN EBADENGINE }

I've tried every node that i could've used before i installed Win11. I even tried the node version the 'package.json' says to use, which is "EXACTLY node 18.0.0" (^18) and still nothing.

[Herysia]

In the quoted text it says you were running with node 21, was it the same error with node 18 ?

[Twigzie]

Yes, same error with every version
Edit: attached the log file running the command using v18.0.0

2024-03-27T15_03_59_091Z-debug-0.log

[Herysia]

That's a different error. Here the build is failing because of an error with node-gyp

error npm ERR! ModuleNotFoundError: No module named 'distutils'

It probably is due to distutils not being included anymore since python 3.12. You can try installing it as suggested here https://stackoverflow.com/a/77638742

[Twigzie]

It probably is due to distutils not being included anymore since python 3.12.

I cant believe i didn't think about python. I obviously had a version older than 3.12 when i was running Windows 10 so i didn't know of anything being removed. good catch, everything seems to be working.

Thanks for the help!