Trying to build a dev version of an APK (Android) but I keep getting the following error.
14572 timing reify:rollback:createSparse Completed in 5948ms
14573 timing reify:rollback:retireShallow Completed in 14ms
14574 timing command:install Completed in 278406ms
14575 verbose stack Error: command failed
14575 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/#npmcli/promise-spawn/lib/index.js:63:27)
14575 verbose stack at ChildProcess.emit (node:events:527:28)
14575 verbose stack at maybeClose (node:internal/child_process:1092:16)
14575 verbose stack at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5)
14576 verbose pkgid #expo/html-elements#0.0.2
14577 verbose cwd /Users/faisaliqbal/.turtle/workingdir/android/sdk42
14578 verbose Darwin 21.3.0
14579 verbose node v16.15.1
14580 verbose npm v8.11.0
14581 error code 1
14582 error path /Users/faisaliqbal/.turtle/workingdir/android/sdk42/packages/html-elements
14583 error command failed
14584 error command sh -c expo-module prepare
14585 error /Users/faisaliqbal/.turtle/workingdir/android/sdk42/node_modules/commander/index.js:837
14585 error throw new Error(executableMissing);
14585 error ^
14585 error
14585 error Error: 'expo-module-prepare' does not exist
14585 error - if 'prepare' is not meant to be an executable command, remove description parameter from '.command()' and use '.description()' instead
14585 error - if the default executable name is not suitable, use the executableFile option to supply a custom name
14585 error at ChildProcess.<anonymous> (/Users/faisaliqbal/.turtle/workingdir/android/sdk42/node_modules/commander/index.js:837:15)
14585 error at ChildProcess.emit (node:events:527:28)
14585 error at Process.ChildProcess._handle.onexit (node:internal/child_process:289:12)
14585 error at onErrorNT (node:internal/child_process:478:16)
14585 error at processTicksAndRejections (node:internal/process/task_queues:83:21)
14586 verbose exit 1
14587 timing npm Completed in 278532ms
14588 verbose unfinished npm timer reify 1656882423113
Here are the versions of the app I am using.
Note: This project is working and compiling fine on another machine.
OS - darwin 12.2.1 (Monterey)
turtle - 0.27.4
Java (2) Versions:
java 18.0.1.1 2022-04-22
openjdk 11.0.15 2022-04-19
expo - 5.4.12
nodejs - v16.15.1
npm - 8.11.0
setup:android is all good
setup:ios is all good
IPA (IOS Binary) compiles without any issue.
Command to start the build:
turtle build:android \
--keystore-path ./keystore/keystore_android.jks \
--keystore-alias "store (redacted)" \
--allow-non-https-public-url \
--gradle-args "--warning-mode all" \
--public-url expo_url (redacted) \
-t apk
What might be the causing this?
Downgrading NodeJS version from 16 to 14 helped.
I originally installed NodeJS using official installer and after removing the installed version I reinstalled node using brew:
brew install node#14
(everything else I specified in my question was left untouched.
Related
After downloading watchman through brew and an expo blank template for my project I have attempted to run a yarn start within the terminal however, I get back the following error:
2022-06-21T09:09:00,229: [] while computing sockname: failed to create /opt/local/var/run/watchman/theflood-state: No such file or directory
Watchman: watchman --no-pretty get-sockname returned with exit code=1, signal=null, stderr= 2022-06-21T09:09:00,229: [] while computing sockname: failed to create /opt/local/var/run/watchman/theflood-state: No such file or directory
/Applications/Telsa-project/TelsaClone/node_modules/metro-hermes-compiler/src/emhermesc.js:77
throw ex;
^
Error: watchman --no-pretty get-sockname returned with exit code=1, signal=null, stderr= 2022-06-21T09:09:00,229: [] while computing sockname: failed to create /opt/local/var/run/watchman/theflood-state: No such file or directory
at ChildProcess.<anonymous> (/Applications/Telsa-project/TelsaClone/node_modules/fb-watchman/index.js:198:18)
at ChildProcess.emit (node:events:527:28)
at maybeClose (node:internal/child_process:1092:16)
at Socket.<anonymous> (node:internal/child_process:451:11)
at Socket.emit (node:events:527:28)
at Pipe.<anonymous> (node:net:709:12)
Emitted 'error' event on Client instance at:
at spawnError (/Applications/Telsa-project/TelsaClone/node_modules/fb-watchman/index.js:170:10)
at ChildProcess. (/Applications/Telsa-project/TelsaClone/node_modules/fb-watchman/index.js:198:7)
at ChildProcess.emit (node:events:527:28)
[... lines matching original stack trace ...]
at Pipe. (node:net:709:12)
error Command failed with exit code 7.
I've tried to reinstall watchman but that doesn't seem to make a difference.
Does anyone know how I might go about fixing this error?
I am getting a bit confused about what’s been happening to me recently.
Whenever I want to create a new vue project, it fails with:
Vue CLI v4.5.11
✨ Creating project in /home/admin/Documents/dev/my_projects/vThesaurus/thesaurus.
⚙️ Installing CLI plugins. This might take a while...
npm ERR! code ERR_SOCKET_TIMEOUT
npm ERR! errno ERR_SOCKET_TIMEOUT
npm ERR! request to https://registry.npm.taobao.org/jsonfile failed, reason: Socket timeout
npm ERR! A complete log of this run can be found in:
npm ERR! /home/admin/.npm/_logs/2021-03-17T06_40_10_793Z-debug.log
ERROR command failed: npm install --loglevel error --legacy-peer-deps
another packages from prev attempts:
request to https://registry.npm.taobao.org/core-js-compat failed, reason: Socket timeout
request to https://cdn.npm.taobao.org/micromatch/-/micromatch-4.0.2.tgz failed, reason: Socket timeout
request to https://registry.npm.taobao.org/querystring-es3 failed, reason: Socket timeout
request to https://registry.npm.taobao.org/file-loader failed, reason: Socket timeout
… and many more
Log: (last part)
4675 timing command:install Completed in 378261ms
4676 verbose type system
4677 verbose stack FetchError: request to https://registry.npm.taobao.org/jsonfile failed, reason: Socket timeout
4677 verbose stack at ClientRequest.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/minipass-fetch/lib/index.js:97:14)
4677 verbose stack at ClientRequest.emit (events.js:315:20)
4677 verbose stack at TLSSocket.socketErrorListener (_http_client.js:463:9)
4677 verbose stack at TLSSocket.emit (events.js:327:22)
4677 verbose stack at emitErrorNT (internal/streams/destroy.js:100:8)
4677 verbose stack at emitErrorCloseNT (internal/streams/destroy.js:68:3)
4677 verbose stack at processTicksAndRejections (internal/process/task_queues.js:84:21)
4678 verbose cwd /home/admin/Documents/dev/my_projects/vThesaurus/thesaurus
4679 verbose Linux 5.4.0-67-generic
4680 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "--loglevel" "error" "--legacy-peer-deps"
4681 verbose node v14.2.0
4682 verbose npm v7.6.3
4683 error code ERR_SOCKET_TIMEOUT
4684 error errno ERR_SOCKET_TIMEOUT
4685 error request to https://registry.npm.taobao.org/jsonfile failed, reason: Socket timeout
4686 verbose exit 1
the weirdest part is that it always fails on a different package …
I tried:
to remove nodejs and vue, reinstall again but no luck …
to increase timeout in the ~/.npmrc but no luck again … (I don’t have slow internet connection - ping 3ms, d: 96Mbps, u: 9.6Mbps)
nothing I found on the internet seems to be working …
changing IPs (nordvpn) to reach to diff servers (CDN) but no luck
vue2 and vue3 ends up with the same failure (random package failure all the time)
manually accessing the failed package - guess what, it works great
tried to add { "useTaobaoRegistry": false } in the ~/.vimrc … no luck again
tried different network provider... no luck :(
nothing seems to be working …
npm -v
7.6.3
vue --version
#vue/cli 4.5.11
OS: Ubuntu 20.04.2 LTS 64bit
Gnome version: 3.36.8
what am I missing?
Looks like you do have issues with taobao in particular. From this github thread, we may try to not use it anymore.
For that, you can go to your ~/.vuerc and set "useTaobaoRegistry": false.
yarn config get registry is giving me https://registry.yarnpkg.com.
I've got a bit of a weird situation where "ember s" reports "Missing yarn packages" followed by a list of missing packages (two of them) and then "Run 'yarn' to install missing dependencies".
However when I run 'yarn' I get the message "success Already up-to-date" .
Any ideas how to get out of this circle ?
There's something I did immediately before this started which I guess is the source of my problem
Getting rid of an Add-on
I had installed an Ember Add-on which had generated problems so I decided to get rid of it . To do that I did the following :
git push -f origin 913c2dee12b0363df0664c9c63e0443abe0adb57:foo-bar
git reset --hard 913c2dee12b0363df0664c9c63e0443abe0adb57
yarn
yarn install
yarn clean
yarn install
yarn
Where 913c2dee12b0363df0664c9c63e0443abe0adb57 was the last commit before the unwanted add-on was installed. I don't think there was anything wrong in doing that but now I'm wondering.
Output of running Ember Server
When I run 'ember s' I get this output ...
DEPRECATION: ember-cli-babel 5.x has been deprecated. Please upgrade to at least ember-cli-babel 6.6. Version 5.2.8 located: foobar -> ember-cli-build-date -> ember-cli-babel
Missing yarn packages:
Package: #bower_components/jquery
* Specified: jquery/jquery-dist#
* Installed: (not installed)
Package: #bower_components/jstree
* Specified: vakata/jstree#^3.3.5
* Installed: (not installed)
Run `yarn` to install missing dependencies.
Stack Trace and Error Report: /tmp/error.dump.33c6e8c0abc9fc8abd355dc080268f9c.log
An error occurred in the constructor for ember-cli-dependency-checker at /media/mint/dev/foobar/node_modules/ember-cli-dependency-checker
Warning about ember-cli versions
I don't think this is relevant but just for completeness
Running the 'yarn' results in the following appearing in the output text ...
warning foobar#0.0.0: "dependencies" has dependency "ember-cli" with range "~3.8.1" that collides with a dependency in "devDependencies" of the same name with version "3.8"
EDIT: OK I was able to resolve this with the help of the comment by dwenzel ...
rm -rf node_modules && yarn
Although that actually led into a different issue which I'm almost certain was unrelated but I'll just mention it here in case it's useful to those who come after.
The execution of yarn initially failed with the following error ...
35238 verbose stack Error: node-sass#4.5.3 postinstall: `node scripts/build.js`
35238 verbose stack Exit status 1
35238 verbose stack at EventEmitter.<anonymous> (/home/rshea/.nvm/versions/node/v10.15.3/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:301:16)
35238 verbose stack at EventEmitter.emit (events.js:189:13)
35238 verbose stack at ChildProcess.<anonymous> (/home/rshea/.nvm/versions/node/v10.15.3/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
35238 verbose stack at ChildProcess.emit (events.js:189:13)
35238 verbose stack at maybeClose (internal/child_process.js:970:16)
35238 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
35239 verbose pkgid node-sass#4.5.3
35240 verbose cwd /media/mintextra/dev/ddn-build-test-temp/foobar
35241 verbose Linux 3.13.0-169-generic
35242 verbose argv "/home/rshea/.nvm/versions/node/v10.15.3/bin/node" "/home/rshea/.nvm/versions/node/v10.15.3/bin/npm" "install"
35243 verbose node v10.15.3
35244 verbose npm v6.4.1
35245 error code ELIFECYCLE
35246 error errno 1
35247 error node-sass#4.5.3 postinstall: `node scripts/build.js`
35247 error Exit status 1
35248 error Failed at the node-sass#4.5.3 postinstall script.
35248 error This is probably not a problem with npm. There is likely additional logging output above.
35249 verbose exit [ 1, true ]
I was able to resolve that with ...
npm install node-sass#latest
npm install
... at which point ember s was able to run without errors.
It looks like you want to do yarn install --check-files to verify that the files have not been removed from node_modules. This avoids having to wipe out your node_modules file which can be time consuming.
https://classic.yarnpkg.com/en/docs/cli/install/#toc-yarn-install-check-files
https://github.com/yarnpkg/yarn/issues/2240
When yarn gets confused like this, you can usually fix things up by clearing out your node modules before installing:
rm -rf node_modules && yarn
The way I managed to get around this without deleting the entire node_modules directory was just to remove the module from topLevelPatterns within node_modules/.yarn-integrity.
Disclaimer: I don't know what the implications of this are but yarn's integrity was already questionable and it works so meh!?
You may also try to reinstall/download all packages with:
yarn install --force
I am getting the following error in Azure DevOps build the pipeline. This works perfectly fine in the local environment.
The error is thrown in ng e2e step. I am on Angular 7.1 version.
2018-12-23T11:09:23.7978210Z ##[section]Starting: Run e2e
2018-12-23T11:09:23.7982921Z ==============================================================================
2018-12-23T11:09:23.7983079Z Task : npm
2018-12-23T11:09:23.7983172Z Description : Install and publish npm packages, or run an npm command. Supports npmjs.com and authenticated registries like Package Management.
2018-12-23T11:09:23.7983263Z Version : 1.144.0
2018-12-23T11:09:23.7983316Z Author : Microsoft Corporation
2018-12-23T11:09:23.7983401Z Help : [More Information](https://go.microsoft.com/fwlink/?LinkID=613746)
2018-12-23T11:09:23.7983480Z ==============================================================================
2018-12-23T11:09:24.2946060Z SYSTEMVSSCONNECTION exists true
2018-12-23T11:09:24.3883866Z SYSTEMVSSCONNECTION exists true
2018-12-23T11:09:24.6106087Z [command]C:\Windows\system32\cmd.exe /D /S /C ""C:\Program Files\nodejs\npm.cmd" --version"
2018-12-23T11:09:25.3644361Z 6.4.1
2018-12-23T11:09:27.0143140Z [command]C:\Windows\system32\cmd.exe /D /S /C ""C:\Program Files\nodejs\npm.cmd" config list"
2018-12-23T11:09:27.8299297Z ; cli configs
2018-12-23T11:09:27.8299516Z metrics-registry = "https://registry.npmjs.org/"
2018-12-23T11:09:27.8299587Z scope = ""
2018-12-23T11:09:27.8299667Z user-agent = "npm/6.4.1 node/v8.12.0 win32 x64"
2018-12-23T11:09:27.8299713Z
2018-12-23T11:09:27.8299768Z ; environment configs
2018-12-23T11:09:27.8299845Z cache = "C:\\npm\\cache"
2018-12-23T11:09:27.8299903Z prefix = "C:\\npm\\prefix"
2018-12-23T11:09:27.8299985Z userconfig = "D:\\a\\1\\npm\\19427.npmrc"
2018-12-23T11:09:27.8300028Z
2018-12-23T11:09:27.8300099Z ; builtin config undefined
2018-12-23T11:09:27.8300137Z
2018-12-23T11:09:27.8300196Z ; node bin location = C:\Program Files\nodejs\node.exe
2018-12-23T11:09:27.8300282Z ; cwd = D:\a\1\s\client
2018-12-23T11:09:27.8300340Z ; HOME = C:\Users\VssAdministrator
2018-12-23T11:09:27.8300451Z ; "npm config ls -l" to show all defaults.
2018-12-23T11:09:27.8300495Z
2018-12-23T11:09:27.8300930Z [command]C:\Windows\system32\cmd.exe /D /S /C ""C:\Program Files\nodejs\npm.cmd" run e2e:ci"
2018-12-23T11:09:30.8886103Z events.js:183
2018-12-23T11:09:30.8886306Z throw er; // Unhandled 'error' event
2018-12-23T11:09:30.8929743Z ^
2018-12-23T11:09:30.8929831Z
2018-12-23T11:09:30.8929890Z Error: read ECONNRESET
2018-12-23T11:09:30.8929964Z at TLSWrap.onread (net.js:622:25)
2018-12-23T11:09:30.8930031Z npm ERR! code ELIFECYCLE
2018-12-23T11:09:30.8930094Z npm ERR! errno 1
2018-12-23T11:09:30.8930157Z npm ERR! icepp#0.0.1 e2e:ci: `ng e2e --configuration=ci`
2018-12-23T11:09:30.8930238Z npm ERR! Exit status 1
2018-12-23T11:09:30.8930294Z npm ERR!
2018-12-23T11:09:30.8930362Z npm ERR! Failed at the icepp#0.0.1 e2e:ci script.
2018-12-23T11:09:30.8930448Z npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2018-12-23T11:09:30.8930548Z
2018-12-23T11:09:30.8930611Z npm ERR! A complete log of this run can be found in:
2018-12-23T11:09:30.8930709Z npm ERR! C:\npm\cache\_logs\2018-12-23T11_09_30_852Z-debug.log
2018-12-23T11:09:30.8930759Z
2018-12-23T11:09:30.8930816Z > icepp#0.0.1 e2e:ci D:\a\1\s\client
2018-12-23T11:09:30.8930888Z > ng e2e --configuration=ci
2018-12-23T11:09:30.8930927Z
2018-12-23T11:09:30.8931013Z [11:09:30] I/file_manager - creating folder D:\a\1\s\client\node_modules\protractor\node_modules\webdriver-manager\selenium
2018-12-23T11:09:30.8931178Z [11:09:30] I/config_source - curl -oD:\a\1\s\client\node_modules\protractor\node_modules\webdriver-manager\selenium\chrome-response.xml https://chromedriver.storage.googleapis.com/
2018-12-23T11:09:30.9440180Z Found npm debug log, make sure the path matches with the one in npm's output: C:\npm\cache\_logs\2018-12-23T11_09_30_852Z-debug.log
2018-12-23T11:09:30.9440341Z 0 info it worked if it ends with ok
2018-12-23T11:09:30.9440416Z 1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
2018-12-23T11:09:30.9440540Z 1 verbose cli 'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
2018-12-23T11:09:30.9442090Z 1 verbose cli 'run',
2018-12-23T11:09:30.9442167Z 1 verbose cli 'e2e:ci' ]
2018-12-23T11:09:30.9442227Z 2 info using npm#6.4.1
2018-12-23T11:09:30.9442298Z 3 info using node#v8.12.0
2018-12-23T11:09:30.9442532Z 4 verbose run-script [ 'pree2e:ci', 'e2e:ci', 'poste2e:ci' ]
2018-12-23T11:09:30.9442602Z 5 info lifecycle icepp#0.0.1~pree2e:ci: icepp#0.0.1
2018-12-23T11:09:30.9442681Z 6 info lifecycle icepp#0.0.1~e2e:ci: icepp#0.0.1
2018-12-23T11:09:30.9442752Z 7 verbose lifecycle icepp#0.0.1~e2e:ci: unsafe-perm in lifecycle true
2018-12-23T11:09:30.9443270Z 8 verbose lifecycle icepp#0.0.1~e2e:ci: PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;D:\a\1\s\client\node_modules\.bin;C:\agents\2.144.0\externals\git\cmd;C:\tools\mingw64\bin;C:\Program Files\dotnet;C:\mysql-5.7.21-winx64\bin;C:\Program Files\Java\jdk1.8.0_192\bin;C:\npm\prefix;C:\hostedtoolcache\windows\Ruby\2.5.0\x64\bin;C:\Go1.11\bin;C:\Program Files\Git\bin;C:\Program Files\Git\usr\bin;C:\Program Files\Git\mingw64\bin;C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\wbin;C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python36_64\Scripts;C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python36_64;C:\Program Files\Microsoft MPI\Bin\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\ProgramData\Chocolatey\bin;C:\Program Files\Docker;C:\Program Files\dotnet\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\120\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\130\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\140\DTS\Binn\;C:\Program Files\Microsoft Service Fabric\bin\Fabric\Fabric.Code;C:\Program Files\Microsoft SDKs\Service Fabric\Tools\ServiceFabricLocalClusterManager;C:\Program Files\Git\cmd;C:\Program Files (x86)\Subversion\bin;C:\Program Files\nodejs\;C:\Program Files\CMake\bin;C:\Program Files\Mercurial;C:\Users\VssAdministrator\AppData\Local\Microsoft\WindowsApps
2018-12-23T11:09:30.9444142Z 9 verbose lifecycle icepp#0.0.1~e2e:ci: CWD: D:\a\1\s\client
2018-12-23T11:09:30.9444233Z 10 silly lifecycle icepp#0.0.1~e2e:ci: Args: [ '/d /s /c', 'ng e2e --configuration=ci' ]
2018-12-23T11:09:30.9444330Z 11 silly lifecycle icepp#0.0.1~e2e:ci: Returned: code: 1 signal: null
2018-12-23T11:09:30.9444416Z 12 info lifecycle icepp#0.0.1~e2e:ci: Failed to exec e2e:ci script
2018-12-23T11:09:30.9444491Z 13 verbose stack Error: icepp#0.0.1 e2e:ci: `ng e2e --configuration=ci`
2018-12-23T11:09:30.9444567Z 13 verbose stack Exit status 1
2018-12-23T11:09:30.9444648Z 13 verbose stack at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:301:16)
2018-12-23T11:09:30.9444737Z 13 verbose stack at emitTwo (events.js:126:13)
2018-12-23T11:09:30.9444816Z 13 verbose stack at EventEmitter.emit (events.js:214:7)
2018-12-23T11:09:30.9444920Z 13 verbose stack at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
2018-12-23T11:09:30.9444998Z 13 verbose stack at emitTwo (events.js:126:13)
2018-12-23T11:09:30.9445080Z 13 verbose stack at ChildProcess.emit (events.js:214:7)
2018-12-23T11:09:30.9445153Z 13 verbose stack at maybeClose (internal/child_process.js:915:16)
2018-12-23T11:09:30.9445248Z 13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
2018-12-23T11:09:30.9445316Z 14 verbose pkgid icepp#0.0.1
2018-12-23T11:09:30.9445388Z 15 verbose cwd D:\a\1\s\client
2018-12-23T11:09:30.9445445Z 16 verbose Windows_NT 10.0.14393
2018-12-23T11:09:30.9445539Z 17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "e2e:ci"
2018-12-23T11:09:30.9445621Z 18 verbose node v8.12.0
2018-12-23T11:09:30.9445685Z 19 verbose npm v6.4.1
2018-12-23T11:09:30.9446141Z 20 error code ELIFECYCLE
2018-12-23T11:09:30.9446212Z 21 error errno 1
2018-12-23T11:09:30.9446271Z 22 error icepp#0.0.1 e2e:ci: `ng e2e --configuration=ci`
2018-12-23T11:09:30.9446347Z 22 error Exit status 1
2018-12-23T11:09:30.9446404Z 23 error Failed at the icepp#0.0.1 e2e:ci script.
2018-12-23T11:09:30.9446483Z 23 error This is probably not a problem with npm. There is likely additional logging output above.
2018-12-23T11:09:30.9446568Z 24 verbose exit [ 1, true ]
2018-12-23T11:09:30.9446605Z
2018-12-23T11:09:30.9511523Z ##[error]Error: Npm failed with return code: 1
2018-12-23T11:09:30.9523513Z ##[section]Finishing: Run e2e
I am using Hosted VS2017 agent. I don't think I am missing any module because it works perfectly fine on local environment.
Build Pipeline
Running npm install and failed with error the following is from npm-debug.log file The same commands works yesterday. There's no change in package.json file.
15065 info install gulp-jsdoc#0.1.5
15066 info postinstall gulp-jsdoc#0.1.5
15067 verbose unlock done using /home/centos/.npm/_locks/gulp-jsdoc-a48e57f10f1c6755.lock for /data/jenkins/workspace/node_modules/gulp-jsdoc
15068 verbose stack Error: Invalid Package: expected taffydb but found taffydb-jsdoc
15068 verbose stack at /usr/lib/node_modules/npm/lib/cache/add-local-tarball.js:127:21
15068 verbose stack at /usr/lib/node_modules/npm/node_modules/read-package-json/read-json.js:356:5
15068 verbose stack at checkBinReferences_ (/usr/lib/node_modules/npm/node_modules/read-package-json/read-json.js:320:45)
15068 verbose stack at final (/usr/lib/node_modules/npm/node_modules/read-package-json/read-json.js:354:3)
15068 verbose stack at then (/usr/lib/node_modules/npm/node_modules/read-package-json/read-json.js:124:5)
15068 verbose stack at /usr/lib/node_modules/npm/node_modules/read-package-json/read-json.js:243:12
15068 verbose stack at /usr/lib/node_modules/npm/node_modules/graceful-fs/graceful-fs.js:78:16
15068 verbose stack at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:380:3)
15069 verbose cwd /data/jenkins/workspace/
15070 error Linux 3.10.0-327.18.2.el7.x86_64
15071 error argv "/usr/bin/node" "/usr/bin/npm" "install"
15072 error node v4.4.5
15073 error npm v2.15.5
15074 error Invalid Package: expected taffydb but found taffydb-jsdoc
15075 error If you need help, you may report this error at:
15075 error <https://github.com/npm/npm/issues>
15076 verbose exit [ 1, true ]
15077 verbose unbuild node_modules/jsdoc
15078 info preuninstall jsdoc#3.3.0-alpha5
15079 info uninstall jsdoc#3.3.0-alpha5
Thanks
G.S.
It would appear that this latest commit in the taffydb-jsdoc fork has broken it:
https://github.com/hegemonic/taffydb/commit/507d2d75fa16e1386f6d50abee1894b264d4458b
(https://www.npmjs.com/package/taffydb-jsdoc)
(Description updated)
The package has been renamed from taffydb to taffydb-jsdoc, so npm is finding a conflict between the expected and the declared package names. In our case and the OP's, hegemonic's fork of taffydb is being referenced by jsdoc, which is a node module required by gulp-jsdoc:
https://github.com/jsBoot/gulp-jsdoc/blob/v0.1.4/package.json#L39
https://github.com/jsdoc3/jsdoc/blob/v3.3.0-alpha5/package.json#L26
EDIT: The author of this fork has contacted me to say the issue has been resolved, as shown in this new commit (package name reverted):
https://github.com/hegemonic/taffydb/commit/e41b5e179e197bb85c5fb887b707672b1e5ca079
I can confirm that our npm install(s) are now working again.