You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> ~/ZeroToBlockchain/Chapter03$ npm install
>
> > [email protected] prepublish /home/hrishikesh/ZeroToBlockchain/Chapter03
> > mkdirp ./network/dist && composer archive create --sourceType dir --sourceName . -a ./network/dist/zerotoblockchain-network.bna
>
> sh: 1: composer: not found
>
> npm ERR! Linux 4.15.0-43-generic
> npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install"
> npm ERR! node v8.10.0
> npm ERR! npm v3.5.2
> npm ERR! file sh
> npm ERR! code ELIFECYCLE
> npm ERR! errno ENOENT
> npm ERR! syscall spawn
> npm ERR! [email protected] prepublish: `mkdirp ./network/dist && composer archive create --sourceType dir --sourceName . -a ./network/dist/zerotoblockchain-network.bna`
> npm ERR! spawn ENOENT
> npm ERR!
> npm ERR! Failed at the [email protected] prepublish script 'mkdirp ./network/dist && composer archive create --sourceType dir --sourceName . -a ./network/dist/zerotoblockchain-network.bna'.
> npm ERR! Make sure you have the latest version of node.js and npm installed.
> npm ERR! If you do, this is most likely a problem with the zerotoblockchain-network package,
> npm ERR! not with npm itself.
> npm ERR! Tell the author that this fails on your system:
> npm ERR! mkdirp ./network/dist && composer archive create --sourceType dir --sourceName . -a ./network/dist/zerotoblockchain-network.bna
> npm ERR! You can get information on how to open an issue for this project with:
> npm ERR! npm bugs zerotoblockchain-network
> npm ERR! Or if that isn't available, you can get their info via:
> npm ERR! npm owner ls zerotoblockchain-network
> npm ERR! There is likely additional logging output above.
>
> npm ERR! Please include the following file with any support request:
> npm ERR! /home/hrishikesh/ZeroToBlockchain/Chapter03/npm-debug.log
>
npm-debug.log file is attached
npm-debug.log
The text was updated successfully, but these errors were encountered: