Error on NPM install

[elitekode2]

Im getting the following error on NPM install on Ubuntu 18.. Can you please help?

`

[email protected] clean /home/blockchain/healthcare-payments-blockchain/packages/server rimraf dist client

src/controllers/account.controller.ts:8:36 - error TS2345: Argument of type 'string | Query | (string | Query)[]' is not assignable to parameter of type 'string'. Type 'Query' is not assignable to type 'string'.

8 let results = await getAll(user); ~~~~

src/controllers/chargeItem.controller.ts:8:36 - error TS2345: Argument of type 'string | Query | (string | Query)[]' is not assignable to parameter of type 'string'. Type 'Query' is not assignable to type 'string'.

8 let results = await getAll(user); ~~~~

src/controllers/claim.controller.ts:9:36 - error TS2345: Argument of type 'string | Query | (string | Query)[]' is not assignable to parameter of type 'string'. Type 'Query' is not assignable to type 'string'.

9 let results = await getAll(user); ~~~~

src/controllers/claimResponse.controller.ts:8:36 - error TS2345: Argument of type 'string | Query | (string | Query)[]' is not assignable to parameter of type 'string'. Type 'Query' is not assignable to type 'string'.

8 let results = await getAll(user); ~~~~

src/controllers/encounter.controller.ts:8:36 - error TS2345: Argument of type 'string | Query | (string | Query)[]' is not assignable to parameter of type 'string'. Type 'Query' is not assignable to type 'string'.

8 let results = await getAll(user); ~~~~

src/controllers/feeExtensions.controller.ts:21:24 - error TS2345: Argument of type 'string | Query | (string | Query)[]' is not assignable to parameter of type 'string'. Type 'Query' is not assignable to type 'string'.

21 await createConfig(user, orgId, config); ~~~~

src/controllers/feeExtensions.controller.ts:43:24 - error TS2345: Argument of type 'string | Query | (string | Query)[]' is not assignable to parameter of type 'string'. Type 'Query' is not assignable to type 'string'.

43 await updateConfig(user, orgId, fee, value); ~~~~

src/controllers/invoice.controller.ts:8:36 - error TS2345: Argument of type 'string | Query | (string | Query)[]' is not assignable to parameter of type 'string'. Type 'Query' is not assignable to type 'string'.

8 let results = await getAll(user); ~~~~

src/controllers/payment.controller.ts:9:36 - error TS2345: Argument of type 'string | Query | (string | Query)[]' is not assignable to parameter of type 'string'. Type 'Query' is not assignable to type 'string'.

9 await paymentMake(payment, user); ~~~~

src/controllers/procedure.controller.ts:8:36 - error TS2345: Argument of type 'string | Query | (string | Query)[]' is not assignable to parameter of type 'string'. Type 'Query' is not assignable to type 'string'.

8 let results = await getAll(user); ~~~~

npm ERR! code ELIFECYCLE npm ERR! errno 2 npm ERR! [email protected] build: npm run clean && tsc npm ERR! Exit status 2 npm ERR! npm ERR! Failed at the [email protected] build script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in: npm ERR! /home/blockchain/.npm/_logs/2020-04-15T07_02_56_152Z-debug.log lerna info lifecycle [email protected]~prepare: Failed to exec prepare script lerna ERR! lifecycle "prepare" errored in "server", exiting 2 npm ERR! code ELIFECYCLE npm ERR! errno 2 npm ERR! [email protected] lerna:install: lerna bootstrap npm ERR! Exit status 2 npm ERR! npm ERR! Failed at the [email protected] lerna:install script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in: npm ERR! /home/blockchain/.npm/_logs/2020-04-15T07_02_56_172Z-debug.log ERROR: "lerna:install" exited with 2. npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! [email protected] install: npm-run-all -s lerna:install npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the [email protected] install script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in: npm ERR! /home/blockchain/.npm/_logs/2020-04-15T07_02_56_209Z-debug.log`

[instameddevelopment]

Can you please provide information about your environment? Include the nodejs version used

[MicahMTurner]

I'm getting the same error on Ubuntu 18.04.4 running node version v8.11.4 and hurl version 1.1.4 Everything works fine until I go to run npm install in the /healthcare-payments-blockchain directory. Following this guide https://developers.instamed.com/healthcare-payments-blockchain/install-blockchain-on-linux/ Any insight is much appreciated.

[MicahMTurner]

It may be worth noting that I'm behind a proxy using environment variables to hold the proxy authentication.

[instameddevelopment]

Hi @MicahMTurner. Did you get any errors from the previous steps of the prerequisites?

[MicahMTurner]

@instameddevelopment No, I was able to install curl git docker.io docker-compose golang python as well as NPM and the Fabric docker instance without issue. npm install of instamed is the first part of the procedure where I get an error. Since reporting this issue I've tried breaking the instamed npm install into it's components to see at what step the install fails at. I've found that the, "hurl new" command also fails to work properly with the following error:

/bin/bash: line 25: /home/blockchain/hyperledger-fabric-network/fabric-binaries/1.4.0/bin/cryptogen: No such file or directory [hurley] - Found error while running script! (node:23861) UnhandledPromiseRejectionWarning: Error: Errors found in script, stopping execution ... (node:23861) 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: 2) (node:23861) [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.

Others have reported getting the same error as covered in this issue https://github.com/worldsibu/hurley/issues/147

[instameddevelopment]

Hi @MicahMTurner that error seems to indicate that the necessary tools from the Hyperledger repo were not successfully downloaded. To discard an error with directory permissions can you check the contents of /home/blockchain/hyperledger-fabric-network/fabric-binaries/1.4.0/bin/cryptogen?

The error you reference seems to be something different. As what the error indicates is that it cannot find the hurley tool. In your case, what's not found is the cryptogen (a tool from hyperledger used to handle cryptographic components).

[MicahMTurner]

@instameddevelopment in my env /home/blockchain/hyperledger-fabric-network/fabric-binaries/1.4.0/ is empty. In the root account in fabric-smaples/bin/ there is a cryptogen file. When i bash the Fabric bootstrap.sh I successfully pull the following docker images: Are there other necessary tools from the Hyperledger repo that are missing here? ===> List out hyperledger docker images hyperledger/fabric-tools 2.1 02b16ec21f30 7 weeks ago 522MB hyperledger/fabric-tools 2.1.1 02b16ec21f30 7 weeks ago 522MB hyperledger/fabric-tools latest 02b16ec21f30 7 weeks ago 522MB hyperledger/fabric-peer 2.1 89cd71f28010 7 weeks ago 56.5MB hyperledger/fabric-peer 2.1.1 89cd71f28010 7 weeks ago 56.5MB hyperledger/fabric-peer latest 89cd71f28010 7 weeks ago 56.5MB hyperledger/fabric-orderer 2.1 b89bce05c7db 7 weeks ago 39.4MB hyperledger/fabric-orderer 2.1.1 b89bce05c7db 7 weeks ago 39.4MB hyperledger/fabric-orderer latest b89bce05c7db 7 weeks ago 39.4MB hyperledger/fabric-ccenv 2.1 998724615c0d 7 weeks ago 554MB hyperledger/fabric-ccenv 2.1.1 998724615c0d 7 weeks ago 554MB hyperledger/fabric-ccenv latest 998724615c0d 7 weeks ago 554MB hyperledger/fabric-baseos 2.1 d67ba930d449 7 weeks ago 6.88MB hyperledger/fabric-baseos 2.1.1 d67ba930d449 7 weeks ago 6.88MB hyperledger/fabric-baseos latest d67ba930d449 7 weeks ago 6.88MB hyperledger/fabric-javaenv 2.1 b22ec67c6494 2 months ago 505MB hyperledger/fabric-javaenv 2.1.1 b22ec67c6494 2 months ago 505MB hyperledger/fabric-javaenv latest b22ec67c6494 2 months ago 505MB hyperledger/fabric-ca 1.4 743a758fae29 2 months ago 154MB hyperledger/fabric-ca 1.4.7 743a758fae29 2 months ago 154MB hyperledger/fabric-ca latest 743a758fae29 2 months ago 154MB hyperledger/fabric-nodeenv 2.1 9f6ae331087d 2 months ago 292MB hyperledger/fabric-nodeenv 2.1.1 9f6ae331087d 2 months ago 292MB hyperledger/fabric-nodeenv latest 9f6ae331087d 2 months ago 292MB hyperledger/fabric-zookeeper 0.4 21e55e9a2862 4 months ago 276MB hyperledger/fabric-zookeeper 0.4.20 21e55e9a2862 4 months ago 276MB hyperledger/fabric-zookeeper latest 21e55e9a2862 4 months ago 276MB hyperledger/fabric-kafka 0.4 28a93b376dbe 4 months ago 270MB hyperledger/fabric-kafka 0.4.20 28a93b376dbe 4 months ago 270MB hyperledger/fabric-kafka latest 28a93b376dbe 4 months ago 270MB hyperledger/fabric-couchdb 0.4 03ac1654afc5 4 months ago 261MB hyperledger/fabric-couchdb 0.4.20 03ac1654afc5 4 months ago 261MB hyperledger/fabric-couchdb latest 03ac1654afc5 4 months ago 261MB hyperledger/fabric-tools 1.4.0 0a44f4261a55 18 months ago 1.56GB hyperledger/fabric-orderer 1.4.0 54f372205580 18 months ago 150MB hyperledger/fabric-peer 1.4.0 304fac59b501 18 months ago 157MB hyperledger/fabric-ca 1.4.0 1a804ab74f58 18 months ago 244MB hyperledger/fabric-couchdb 0.4.14 f14f97292b4c 21 months ago 1.5GB

[MicahMTurner]

Sorry @instameddevelopment I posted the wrong git issue before. Apparently someone had solved that hurl new command issue with a different docker.io/docker-compose version. I wish they had posted which version worked. https://github.com/worldsibu/hurley/issues/83

[MicahMTurner]

My current docker --version output is: Docker version 19.03.6, build 369ce74a3c

[instameddevelopment]

Ok. However, if you managed to download the images then docker should not be an issue anymore.

The new error /home/blockchain/hyperledger-fabric-network/fabric-binaries/1.4.0/ is empty is another network issue.

There should be a group of scripts here /home/blockchain/hyperledger-fabric-network/ can you send me a list of what appears there?

[MicahMTurner]

@instameddevelopment Thank you so much for helping me with this. The contents of the /home/blockchain/hyperledger-fabric-network/ are: artifacts configtx.yaml fabric-binaries binaries.sh crypto-config.yaml generator.sh Where artifacts and fabric-binaries are directories. When I bash binaries.sh i get the following output: ===> List out hyperledger docker images hyperledger/fabric-tools 2.1 02b16ec21f30 7 weeks ago 522MB hyperledger/fabric-tools 2.1.1 02b16ec21f30 7 weeks ago 522MB hyperledger/fabric-peer 2.1 89cd71f28010 7 weeks ago 56.5MB hyperledger/fabric-peer 2.1.1 89cd71f28010 7 weeks ago 56.5MB hyperledger/fabric-orderer 2.1 b89bce05c7db 7 weeks ago 39.4MB hyperledger/fabric-orderer 2.1.1 b89bce05c7db 7 weeks ago 39.4MB hyperledger/fabric-ccenv 2.1 998724615c0d 7 weeks ago 554MB hyperledger/fabric-ccenv 2.1.1 998724615c0d 7 weeks ago 554MB hyperledger/fabric-ccenv latest 998724615c0d 7 weeks ago 554MB hyperledger/fabric-baseos 2.1 d67ba930d449 7 weeks ago 6.88MB hyperledger/fabric-baseos 2.1.1 d67ba930d449 7 weeks ago 6.88MB hyperledger/fabric-baseos latest d67ba930d449 7 weeks ago 6.88MB hyperledger/fabric-javaenv 2.1 b22ec67c6494 2 months ago 505MB hyperledger/fabric-javaenv 2.1.1 b22ec67c6494 2 months ago 505MB hyperledger/fabric-javaenv latest b22ec67c6494 2 months ago 505MB hyperledger/fabric-ca 1.4 743a758fae29 2 months ago 154MB hyperledger/fabric-ca 1.4.7 743a758fae29 2 months ago 154MB hyperledger/fabric-nodeenv 2.1 9f6ae331087d 3 months ago 292MB hyperledger/fabric-nodeenv 2.1.1 9f6ae331087d 3 months ago 292MB hyperledger/fabric-nodeenv latest 9f6ae331087d 3 months ago 292MB hyperledger/fabric-zookeeper 0.4 21e55e9a2862 4 months ago 276MB hyperledger/fabric-zookeeper 0.4.20 21e55e9a2862 4 months ago 276MB hyperledger/fabric-zookeeper latest 21e55e9a2862 4 months ago 276MB hyperledger/fabric-kafka 0.4 28a93b376dbe 4 months ago 270MB hyperledger/fabric-kafka 0.4.20 28a93b376dbe 4 months ago 270MB hyperledger/fabric-kafka latest 28a93b376dbe 4 months ago 270MB hyperledger/fabric-couchdb 0.4 03ac1654afc5 4 months ago 261MB hyperledger/fabric-couchdb 0.4.20 03ac1654afc5 4 months ago 261MB hyperledger/fabric-tools 1.4.0 0a44f4261a55 18 months ago 1.56GB hyperledger/fabric-tools latest 0a44f4261a55 18 months ago 1.56GB hyperledger/fabric-orderer 1.4.0 54f372205580 18 months ago 150MB hyperledger/fabric-orderer latest 54f372205580 18 months ago 150MB hyperledger/fabric-peer 1.4.0 304fac59b501 18 months ago 157MB hyperledger/fabric-peer latest 304fac59b501 18 months ago 157MB hyperledger/fabric-ca 1.4.0 1a804ab74f58 18 months ago 244MB hyperledger/fabric-ca latest 1a804ab74f58 18 months ago 244MB hyperledger/fabric-couchdb 0.4.14 f14f97292b4c 21 months ago 1.5GB hyperledger/fabric-couchdb latest f14f97292b4c 21 months ago 1.5GB

[instameddevelopment]

Can you run the binaries script? If there's a network issue, it should show it.

[MicahMTurner]

@instameddevelopment yes, when I bash the binaries.sh it shows this output:

Installing Hyperledger Fabric binaries Binaries exist already Checking IMAGES ===> Pulling fabric Images ==> FABRIC IMAGE: peer

1.4.0: Pulling from hyperledger/fabric-peer Digest: sha256:9707c97f787de1d4d6dd60994d6b8ea2e5cc28b0f42e6849df3fb41c64b41372 Status: Image is up to date for hyperledger/fabric-peer:1.4.0 docker.io/hyperledger/fabric-peer:1.4.0 ==> FABRIC IMAGE: orderer

1.4.0: Pulling from hyperledger/fabric-orderer Digest: sha256:644265186b4887c7d9dcb91895124ccead3c0125c2c4f9eadc421dc9555d7495 Status: Image is up to date for hyperledger/fabric-orderer:1.4.0 docker.io/hyperledger/fabric-orderer:1.4.0 ==> FABRIC IMAGE: tools

1.4.0: Pulling from hyperledger/fabric-tools Digest: sha256:aee256916d0cb938d8023fa32ed2745991d32cfe79018e360f1720707ebfbdb5 Status: Image is up to date for hyperledger/fabric-tools:1.4.0 docker.io/hyperledger/fabric-tools:1.4.0 ===> Pulling fabric ca Image ==> FABRIC CA IMAGE

1.4.0: Pulling from hyperledger/fabric-ca Digest: sha256:c1dce534d9e9202697e0aaad7c5521d958700fda0b05127dafb9333c22e15f74 Status: Image is up to date for hyperledger/fabric-ca:1.4.0 docker.io/hyperledger/fabric-ca:1.4.0 ===> Pulling thirdparty docker images ==> THIRDPARTY DOCKER IMAGE: couchdb

0.4.14: Pulling from hyperledger/fabric-couchdb Digest: sha256:021c7e4a5047432d892fbdf7d5220d3049ff4e8b436fd481bb08e41871f1aac7 Status: Image is up to date for hyperledger/fabric-couchdb:0.4.14 docker.io/hyperledger/fabric-couchdb:0.4.14

===> List out hyperledger docker images hyperledger/fabric-tools 2.1 02b16ec21f30 7 weeks ago 522MB hyperledger/fabric-tools 2.1.1 02b16ec21f30 7 weeks ago 522MB hyperledger/fabric-peer 2.1 89cd71f28010 7 weeks ago 56.5MB hyperledger/fabric-peer 2.1.1 89cd71f28010 7 weeks ago 56.5MB hyperledger/fabric-orderer 2.1 b89bce05c7db 7 weeks ago 39.4MB hyperledger/fabric-orderer 2.1.1 b89bce05c7db 7 weeks ago 39.4MB hyperledger/fabric-ccenv 2.1 998724615c0d 7 weeks ago 554MB hyperledger/fabric-ccenv 2.1.1 998724615c0d 7 weeks ago 554MB hyperledger/fabric-ccenv latest 998724615c0d 7 weeks ago 554MB hyperledger/fabric-baseos 2.1 d67ba930d449 7 weeks ago 6.88MB hyperledger/fabric-baseos 2.1.1 d67ba930d449 7 weeks ago 6.88MB hyperledger/fabric-baseos latest d67ba930d449 7 weeks ago 6.88MB hyperledger/fabric-javaenv 2.1 b22ec67c6494 2 months ago 505MB hyperledger/fabric-javaenv 2.1.1 b22ec67c6494 2 months ago 505MB hyperledger/fabric-javaenv latest b22ec67c6494 2 months ago 505MB hyperledger/fabric-ca 1.4 743a758fae29 2 months ago 154MB hyperledger/fabric-ca 1.4.7 743a758fae29 2 months ago 154MB hyperledger/fabric-nodeenv 2.1 9f6ae331087d 3 months ago 292MB hyperledger/fabric-nodeenv 2.1.1 9f6ae331087d 3 months ago 292MB hyperledger/fabric-nodeenv latest 9f6ae331087d 3 months ago 292MB hyperledger/fabric-zookeeper 0.4 21e55e9a2862 4 months ago 276MB hyperledger/fabric-zookeeper 0.4.20 21e55e9a2862 4 months ago 276MB hyperledger/fabric-zookeeper latest 21e55e9a2862 4 months ago 276MB hyperledger/fabric-kafka 0.4 28a93b376dbe 4 months ago 270MB hyperledger/fabric-kafka 0.4.20 28a93b376dbe 4 months ago 270MB hyperledger/fabric-kafka latest 28a93b376dbe 4 months ago 270MB hyperledger/fabric-couchdb 0.4 03ac1654afc5 4 months ago 261MB hyperledger/fabric-couchdb 0.4.20 03ac1654afc5 4 months ago 261MB hyperledger/fabric-tools 1.4.0 0a44f4261a55 18 months ago 1.56GB hyperledger/fabric-tools latest 0a44f4261a55 18 months ago 1.56GB hyperledger/fabric-orderer 1.4.0 54f372205580 18 months ago 150MB hyperledger/fabric-orderer latest 54f372205580 18 months ago 150MB hyperledger/fabric-peer 1.4.0 304fac59b501 18 months ago 157MB hyperledger/fabric-peer latest 304fac59b501 18 months ago 157MB hyperledger/fabric-ca 1.4.0 1a804ab74f58 18 months ago 244MB hyperledger/fabric-ca latest 1a804ab74f58 18 months ago 244MB hyperledger/fabric-couchdb 0.4.14 f14f97292b4c 21 months ago 1.5GB hyperledger/fabric-couchdb latest f14f97292b4c 21 months ago 1.5GB

[MicahMTurner]

Here's the complete output when I attempt npm install:

blockchain@ubuntufabric:~/healthcare-payments-blockchain$ npm install

[email protected] install /home/blockchain/healthcare-payments-blockchain npm-run-all -s lerna:install

[email protected] lerna:install /home/blockchain/healthcare-payments-blockchain lerna bootstrap

lerna notice cli v3.20.2 lerna info Bootstrapping 4 packages lerna WARN EHOIST_ROOT_VERSION The repository root depends on fabric-ca-client@~1.4.0, which differs from the more common fabric-ca-client@^1.4.0. lerna WARN EHOIST_PKG_VERSION "administration" package depends on fabric-ca-client@^1.4.0, which differs from the hoisted fabric-ca-client@~1.4.0. lerna WARN EHOIST_ROOT_VERSION The repository root depends on fabric-client@~1.4.0, which differs from the more common fabric-client@^1.4.0. lerna WARN EHOIST_PKG_VERSION "administration" package depends on fabric-client@^1.4.0, which differs from the hoisted fabric-client@~1.4.0. lerna WARN EHOIST_PKG_VERSION "administration" package depends on dotenv@^6.2.0, which differs from the hoisted dotenv@^6.0.0. lerna info Installing external dependencies lerna info hoist Installing hoisted dependencies into root lerna info hoist Pruning hoisted dependencies lerna info hoist Finished pruning hoisted dependencies lerna info hoist Finished bootstrapping root lerna info Symlinking packages and binaries lerna info lifecycle [email protected]~prepare: [email protected]

[email protected] prepare /home/blockchain/healthcare-payments-blockchain/packages/financial-cc npm run build

[email protected] build /home/blockchain/healthcare-payments-blockchain/packages/financial-cc npm run clean && tsc

[email protected] clean /home/blockchain/healthcare-payments-blockchain/packages/financial-cc rimraf dist client

lerna info lifecycle [email protected]~prepare: [email protected]

[email protected] prepare /home/blockchain/healthcare-payments-blockchain/packages/server npm run build

[email protected] build /home/blockchain/healthcare-payments-blockchain/packages/server npm run clean && tsc

[email protected] clean /home/blockchain/healthcare-payments-blockchain/packages/server rimraf dist client

src/controllers/account.controller.ts:8:36 - error TS2345: Argument of type 'string | string[] | ParsedQs | ParsedQs[]' is not assignable to parameter of type 'string'. Type 'string[]' is not assignable to type 'string'.

8 let results = await getAll(user); ~~~~

src/controllers/chargeItem.controller.ts:8:36 - error TS2345: Argument of type 'string | string[] | ParsedQs | ParsedQs[]' is not assignable to parameter of type 'string'. Type 'string[]' is not assignable to type 'string'.

8 let results = await getAll(user); ~~~~

src/controllers/claim.controller.ts:9:36 - error TS2345: Argument of type 'string | string[] | ParsedQs | ParsedQs[]' is not assignable to parameter of type 'string'. Type 'string[]' is not assignable to type 'string'.

9 let results = await getAll(user); ~~~~

src/controllers/claimResponse.controller.ts:8:36 - error TS2345: Argument of type 'string | string[] | ParsedQs | ParsedQs[]' is not assignable to parameter of type 'string'. Type 'string[]' is not assignable to type 'string'.

8 let results = await getAll(user); ~~~~

src/controllers/encounter.controller.ts:8:36 - error TS2345: Argument of type 'string | string[] | ParsedQs | ParsedQs[]' is not assignable to parameter of type 'string'. Type 'string[]' is not assignable to type 'string'.

8 let results = await getAll(user); ~~~~

src/controllers/feeExtensions.controller.ts:21:24 - error TS2345: Argument of type 'string | string[] | ParsedQs | ParsedQs[]' is not assignable to parameter of type 'string'. Type 'string[]' is not assignable to type 'string'.

21 await createConfig(user, orgId, config); ~~~~

src/controllers/feeExtensions.controller.ts:43:24 - error TS2345: Argument of type 'string | string[] | ParsedQs | ParsedQs[]' is not assignable to parameter of type 'string'. Type 'string[]' is not assignable to type 'string'.

43 await updateConfig(user, orgId, fee, value); ~~~~

src/controllers/invoice.controller.ts:8:36 - error TS2345: Argument of type 'string | string[] | ParsedQs | ParsedQs[]' is not assignable to parameter of type 'string'. Type 'string[]' is not assignable to type 'string'.

8 let results = await getAll(user); ~~~~

src/controllers/payment.controller.ts:9:36 - error TS2345: Argument of type 'string | string[] | ParsedQs | ParsedQs[]' is not assignable to parameter of type 'string'. Type 'string[]' is not assignable to type 'string'.

9 await paymentMake(payment, user); ~~~~

src/controllers/procedure.controller.ts:8:36 - error TS2345: Argument of type 'string | string[] | ParsedQs | ParsedQs[]' is not assignable to parameter of type 'string'. Type 'string[]' is not assignable to type 'string'.

8 let results = await getAll(user); ~~~~

npm ERR! code ELIFECYCLE npm ERR! errno 2 npm ERR! [email protected] build: npm run clean && tsc npm ERR! Exit status 2 npm ERR! npm ERR! Failed at the [email protected] build script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in: npm ERR! /home/blockchain/.npm/_logs/2020-07-21T17_39_56_324Z-debug.log lerna info lifecycle [email protected]~prepare: Failed to exec prepare script lerna ERR! lifecycle "prepare" errored in "server", exiting 2 npm ERR! code ELIFECYCLE npm ERR! errno 2 npm ERR! [email protected] lerna:install: lerna bootstrap npm ERR! Exit status 2 npm ERR! npm ERR! Failed at the [email protected] lerna:install script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in: npm ERR! /home/blockchain/.npm/_logs/2020-07-21T17_39_56_349Z-debug.log ERROR: "lerna:install" exited with 2. npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! [email protected] install: npm-run-all -s lerna:install npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the [email protected] install script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in: npm ERR! /home/blockchain/.npm/_logs/2020-07-21T17_39_56_418Z-debug.log

[instameddevelopment]

If something broke before (during installation) npm install won't work.

Is that the whole log when running the binaries script?

[MicahMTurner]

@instameddevelopment yes, that's the whole output when running the binaries script. When I test 'npm init' by following this example, npm functions as expected. https://threejs.org/docs/#manual/en/buildTools/Testing-with-NPM

[TheMadHatage]

Anyone figure this out yet?

[bajiang1]

two years anyone fix it？help me daddys