-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
初始化完app运行dev报错 #7130
Comments
npm run dev:h5 这个可以 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
相关平台
React Native
使用框架: Vue2
复现步骤
npm run dev:rn
期望结果
可以运行
实际结果
无法运行
环境信息
补充信息
报错如下:
� Taro v3.0.5
生成 package.json D:\web\mini-program\dsm-web\package.json
开始安装依赖~
(node:7280) UnhandledPromiseRejectionWarning: Error: Command failed: npm install
npm WARN deprecated core-js@1.2.7: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm WARN deprecated left-pad@1.3.0: use String.prototype.padStart()
npm ERR! code ETARGET
npm ERR! notarget No matching version found for @tarojs/components-rn@^3.0.5.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! notarget
npm ERR! notarget It was specified as a dependency of 'dsm-web'
npm ERR! notarget
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\xxzj990\AppData\Roaming\npm-cache_logs\2020-07-21T10_07_39_935Z-debug.log
(node:7280) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag
--unhandled-rejections=strict
(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)(node:7280) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
The text was updated successfully, but these errors were encountered: