I do create-vk-mini-app, does it give an error?

Question

JavaScript

The error itself:

C:\Users\User_ml\Desktop\чай>create-vk-mini-app app
 Creating project...
⏱ Installing project dependencies — it might take a few minutes..
 npm error:
Error: Command failed: cd app && npm install [email protected]^7.0.3 [email protected]^4.13.0 [email protected]^4.0.3 --save-dev && npm install @vkontakte/[email protected]^1.92.0 @vkontakte/[email protected] @vkontakte/[email protected]^4.5.0 [email protected]^10.1.0 [email protected]^4.1.0 [email protected]^2.4.1 [email protected]^2.0.0 [email protected]^2.0.0  [email protected]^15.7.2 [email protected]^17.0.2 [email protected]^17.0.2 @vkontakte/[email protected] @vkontakte/[email protected]
npm WARN deprecated [email protected]: flatten is deprecated in favor of utility frameworks such as lodash.
npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated [email protected]: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated [email protected]: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated [email protected]: some dependency vulnerabilities fixed, support for node < 10 dropped, and newer ECMAScript syntax/features added
npm WARN deprecated @hapi/[email protected]: Moved to 'npm install @sideway/address'
npm WARN deprecated [email protected]: This package has been deprecated and is no longer maintained. Please use @rollup/plugin-babel.
npm WARN deprecated [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated [email protected]: babel-eslint is now @babel/eslint-parser. This package will no longer receive updates.
npm WARN deprecated [email protected]: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated [email protected]: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated @hapi/[email protected]: Switch to 'npm install joi'
npm WARN deprecated [email protected]: [email protected]<3.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: @vkontakte/[email protected]
npm ERR! node_modules/@vkontakte/vkjs
npm ERR!   @vkontakte/[email protected]"0.22.1" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @vkontakte/[email protected]"^0.20.0" from @vkontakte/[email protected]
npm ERR! node_modules/@vkontakte/vkui
npm ERR!   @vkontakte/[email protected]"4.5.0" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See C:\Users\User_ml\AppData\Local\npm-cache\eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\User_ml\AppData\Local\npm-cache\_logs\2021-09-28T16_55_26_944Z-debug.log

Answer 1

What version of node do you have?
Perhaps this will solve the issue: Fix the upstream dependency conflict, or retry this command with --force, or --legacy-peer-deps
You have this written in the log.
I also found an article about this: https://go.innoscripta.com/615eba813f727