I followed the instructions to install the hyperledger tools on Ubuntu 18.04. Due to a permission problem I had to change the node_modules directory.
I can run the tools, except composer-cli (composer-cli: command not found).
Installation log:
$ npm install -g composer-cli#0.20
...
WARN engine fabric-client#1.2.1: wanted: {"node":"^8.9.0","npm":"^5.5.1"} (current: {"node":"8.10.0","npm":"3.5.2"})
/home/asset-tracker/.npm-global/bin/composer -> /home/asset-tracker/.npm-global/lib/node_modules/composer-cli/cli.js
/home/asset-tracker/.npm-global/lib
└── composer-cli#0.20.4
npm WARN optional Skipping failed optional dependency /composer-cli/chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents#1.2.4
Well, as seen in the log snippet. I think you should try to upgrade the version of npm.
hyperledger-composer supports Ubuntu Linux 14.04 / 16.04 LTS (both 64-bit). Installing to 18.04 might facing unexpected error. installing prereqs
Related
I installed composer on AWS ubuntu instance with this command:
npm i -g #composer-cli#0.19
On running this command for checking the installation: composer --help
I got this error
composer command not found
What version of npm are you using? Composer only officially supports npm v5.x and node v8.9.x. In particular, make sure you are not running npm v6 or any higher versions of node, eg node v9 or node v10.
If you see this Link for the installation of the development environment the command for composer installation is:
npm install -g composer-cli#0.19
but you are using
npm i -g #composer-cli#0.19
follow the instructions provided in above link, it will work perfectly fine.
composer-cli v0.19.2 was successfully installed still on running this error occurs.
Development only script for Hyperledger Fabric control
Running 'createPeerAdminCard.sh'
FABRIC_VERSION is unset, assuming hlfv11
FABRIC_START_TIMEOUT is unset, assuming 15 (seconds)
No version of composer-cli has been detected, you need to install composer-cli at v0.19 or higher
The problem is that if you install composer using root or sudo then it is not available to non-root users.
The pre-reqs doc for Composer warns not to use root or sudo, but the warning is actually missing in the install doc itself.
I would recommend uninstalling composer-cli (and playground, rest-server etc) with a command like sudo npm uninstall -g composer-cli then re-install without using sudo. If you have permission problems with npm install there are some notes in the composer knowledge wiki.
I've problem when installing react app with npm.
I also have downgrade my version of npm to version 3, but still error. And especially my internet connection is very good.
Thanks for your answer!
Try following solution
Install yarn npm install -g yarn
Disable antivirus
Enable npm registry on firewall
I am installing the CLI Tools for a local Hyperledger Composer dev environment on a MacBook Pro (MacOS 10.13.2) and have deprecation / package name change messages come up in the output from NPM. To do the install I am following the instructions from this location:
https://hyperledger.github.io/composer/installing/development-tools.html
My question is do I need to take action based on these messages (see below), or can I just continue? Please forgive the basic question, but am a total newb at this level of work on a Mac - am doing it for a Hyperledger course on Coursera.org.
This is the command that I run: npm install -g composer-cli
...and here are the first few lines of output:
npm WARN deprecated fs-promise#1.0.0: Use mz or fs-extra^3.0 with Promise Support
npm WARN deprecated crypto#0.0.3: This package is no longer supported. It's now a built-in Node module. If you've depended on crypto, you should switch to the one that's built-in.
npm WARN deprecated jade#1.11.0: Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN deprecated transformers#2.1.0: Deprecated, use jstransformer
npm WARN deprecated nodemailer#2.7.2: All versions below 4.0.1 of Nodemailer are deprecated. See https://nodemailer.com/status/
then a little further down I get this:
gyp WARN download NVM_NODEJS_ORG_MIRROR is deprecated and will be removed in node-gyp v4, please use NODEJS_ORG_MIRROR
Update (2018-01-11)
Am continuing following Joe Clay's reply below and now just run this command: npm install -g composer-playground
...and get the following warnings at the end of the output from NPM:
npm WARN ngx-clipboard#8.0.4 requires a peer of #angular/core#>=4.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN ngx-clipboard#8.0.4 requires a peer of #angular/common#>=4.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN ngx-clipboard#8.0.4 requires a peer of #angular/platform-browser#>=4.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN ngx-clipboard#8.0.4 requires a peer of core-js#>=2.4.1 but none is installed. You must install peer dependencies yourself.
npm WARN #ng-bootstrap/ng-bootstrap#1.0.0-beta.2 requires a peer of #angular/core#^4.0.3 but none is installed. You must install peer dependencies yourself.
npm WARN #ng-bootstrap/ng-bootstrap#1.0.0-beta.2 requires a peer of #angular/common#^4.0.3 but none is installed. You must install peer dependencies yourself.
npm WARN #ng-bootstrap/ng-bootstrap#1.0.0-beta.2 requires a peer of #angular/forms#^4.0.3 but none is installed. You must install peer dependencies yourself.
npm WARN ngx-window-token#0.0.2 requires a peer of #angular/core#>=2.4.1 but none is installed. You must install peer dependencies yourself.
npm WARN ngx-window-token#0.0.2 requires a peer of #angular/common#>=2.4.1 but none is installed. You must install peer dependencies yourself.
npm WARN ngx-window-token#0.0.2 requires a peer of #angular/platform-browser#>=2.4.1 but none is installed. You must install peer dependencies yourself.
npm WARN ngx-window-token#0.0.2 requires a peer of core-js#>=2.4.1 but none is installed. You must install peer dependencies yourself.
Will continue for now and see if these warnings affect the final dev env't. Am a bit disappointed with the IBM crowd for giving code like this to students :(
Thanks muchly in advance for your help!
cheers, Lawrence
Endorsing Joe Clay's response, you can ignore those messages as he has articulated. peerDependencies is defined in package.json (referring to the Angular messages, which Playground depends on).
Hyperledger consists of a number of members (not just IBM please note) - see more here -> https://www.hyperledger.org/members that contribute code to projects such as Hyperledger Compoer (one such incubation project)
I'm trying to install docpad and following the guide on: http://docpad.org/docs/install
When I issue the command:
npm install -g docpad#6.63
I get the following npm error:
npm ERR! Error: No compatible version found: taskgroup#'~3.3.7n'
npm ERR! Valid install targets:
npm ERR! ["2.0.0","3.0.0","3.1.0","3.1.1","3.1.2","3.2.0","3.2.2","3.2.3","3.2.4","3.3.0","3.3.1","3.3.2","3.3.3","3.3.4","3.3.5","3.3.6","3.3.7","3.3.8"]
My node version: v0.10.15
My npm version: 1.2.18
I'm running Kubuntu 13.10 with all updates.
I checked if there is an issue reported for this on github, there isn't. Should I report this as an issue or am I doing something wrong?
Same problem here (Kubuntu 13.10).
I sugggest to go back to a previous version of docpad for the moment. On Ubunto/Debian there is another pitfall: some node modules depend on the nodejs executable to be available under node, so you need the additional package nodejs-legacy.
This worked for me:
sudo apt-get install nodejs-legacy
npm install docpad#6.55.6
Bug on DocPad's behalf, that n shouldn't have been there. Now fixed in v6.63.5. Thanks for the report!