Created
July 9, 2018 08:49
-
-
Save come25136/45429893432ea77e70765f1efeb12156 to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
(node:16048) UnhandledPromiseRejectionWarning: CordovaError: Failed to fetch plugin [email protected] via registry. | |
Probably this is either a connection problem, or plugin spec is incorrect. | |
Check your connection and plugin name/version/URL. | |
Error: C:\Program Files (x86)\Nodist\bin\npm.exe: Command failed with exit code 1 Error output: | |
npm WARN tar EINVAL: invalid argument, futime | |
npm WARN tar EINVAL: invalid argument, futime | |
npm WARN tar EINVAL: invalid argument, futime | |
npm WARN tar EINVAL: invalid argument, futime | |
npm WARN tar EINVAL: invalid argument, futime | |
npm WARN tar EINVAL: invalid argument, futime | |
npm WARN tar EINVAL: invalid argument, futime | |
npm WARN tar EINVAL: invalid argument, futime | |
npm WARN tar EINVAL: invalid argument, futime | |
npm WARN tar EINVAL: invalid argument, futime | |
npm WARN tar EINVAL: invalid argument, futime | |
npm WARN tar EINVAL: invalid argument, futime | |
npm WARN tar EINVAL: invalid argument, futime | |
npm WARN tar EINVAL: invalid argument, futime | |
npm WARN tar EINVAL: invalid argument, futime | |
npm WARN tar EINVAL: invalid argument, futime | |
npm WARN tar EINVAL: invalid argument, futime | |
npm WARN tar EINVAL: invalid argument, futime | |
npm WARN tar EINVAL: invalid argument, futime | |
npm WARN tar EINVAL: invalid argument, futime | |
npm WARN tar EINVAL: invalid argument, futime | |
npm WARN tar EINVAL: invalid argument, futime | |
npm WARN tar EINVAL: invalid argument, futime | |
npm WARN tar EINVAL: invalid argument, futime | |
npm WARN tar EINVAL: invalid argument, futime | |
npm WARN tar EINVAL: invalid argument, futime | |
npm WARN tar EINVAL: invalid argument, futime | |
npm WARN tar EINVAL: invalid argument, futime | |
npm WARN tar EINVAL: invalid argument, futime | |
npm WARN tar EINVAL: invalid argument, futime | |
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules\fsevents): | |
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Error: EPERM: operation not permitted, rename 'K:\apps\busmap\node_modules\.staging\fsevents-76fbec70\node_modules\fs-minipass' -> 'K:\apps\busmap\node_modules\.staging\fs-minipass-d9a818ec' | |
npm ERR! code EINVAL | |
npm ERR! EINVAL: invalid argument, read | |
npm ERR! A complete log of this run can be found in: | |
npm ERR! C:\Users\toki\AppData\Roaming\npm-cache\_logs\2018-07-09T08_46_53_429Z-debug.log | |
at C:\Program Files (x86)\Nodist\bin\node_modules\cordova\node_modules\cordova-lib\src\plugman\fetch.js:173:37 | |
at _rejected (C:\Program Files (x86)\Nodist\bin\node_modules\cordova\node_modules\q\q.js:864:24) | |
at C:\Program Files (x86)\Nodist\bin\node_modules\cordova\node_modules\q\q.js:890:30 | |
at Promise.when (C:\Program Files (x86)\Nodist\bin\node_modules\cordova\node_modules\q\q.js:1142:31) | |
at Promise.promise.promiseDispatch (C:\Program Files (x86)\Nodist\bin\node_modules\cordova\node_modules\q\q.js:808:41) | |
at C:\Program Files (x86)\Nodist\bin\node_modules\cordova\node_modules\q\q.js:624:44 | |
at runSingle (C:\Program Files (x86)\Nodist\bin\node_modules\cordova\node_modules\q\q.js:137:13) | |
at flush (C:\Program Files (x86)\Nodist\bin\node_modules\cordova\node_modules\q\q.js:125:13) | |
at _combinedTickCallback (internal/process/next_tick.js:131:7) | |
at process._tickCallback (internal/process/next_tick.js:180:9) | |
(node:16048) 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(). (rejection id: 1) | |
(node:16048) [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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment