Skip to content

Instantly share code, notes, and snippets.

@crandmck

crandmck/gist:442703c0535c65d82fd1

Last active August 29, 2015 14:25
Show Gist options
  • Save crandmck/442703c0535c65d82fd1 to your computer and use it in GitHub Desktop.
Save crandmck/442703c0535c65d82fd1 to your computer and use it in GitHub Desktop.
Download ZIP
strong-mesh-models install problems
Raw
gistfile1.txt
$ npm cache clear
$ npm i -g strong-mesh-models --registry http://ci.strongloop.com:4873
/usr/local/bin/sl-meshctl -> /usr/local/lib/node_modules/strong-mesh-models/bin/sl-meshctl.js
/usr/local/bin/sl-meshadm -> /usr/local/lib/node_modules/strong-mesh-models/bin/sl-meshadm.js
npm WARN unmet dependency /usr/local/lib/node_modules/bower/node_modules/tar-fs/node_modules/tar-stream/node_modules/bl requires readable-stream@'~1.0.26' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/bower/node_modules/tar-fs/node_modules/tar-stream/node_modules/readable-stream,
npm WARN unmet dependency which is version 1.0.33-1
npm WARN unmet dependency /usr/local/lib/node_modules/loopback-sdk-angular-cli/node_modules/express/node_modules/connect/node_modules/multiparty/node_modules/stream-counter requires readable-stream@'~1.1.8' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/loopback-sdk-angular-cli/node_modules/express/node_modules/connect/node_modules/multiparty/node_modules/readable-stream,
npm WARN unmet dependency which is version 1.1.13-1
npm WARN unmet dependency /usr/local/lib/node_modules/npm/node_modules/npmconf requires semver@'2' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/npm/node_modules/semver,
npm WARN unmet dependency which is version 4.3.6
npm WARN unmet dependency /usr/local/lib/node_modules/npm/node_modules/npmconf requires uid-number@'0.0.5' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/npm/node_modules/uid-number,
npm WARN unmet dependency which is version 0.0.6
npm WARN unmet dependency /usr/local/lib/node_modules/npm/node_modules/read-package-json/node_modules/normalize-package-data requires semver@'2 || 3' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/npm/node_modules/semver,
npm WARN unmet dependency which is version 4.3.6
strong-mesh-models@7.0.0 /usr/local/lib/node_modules/strong-mesh-models
├── user-home@1.1.1
├── sprintf@0.1.5
├── strong-url-defaults@1.2.1
├── posix-getopt@1.1.0
├── text-table@0.2.0
├── async@0.9.2
├── debug@2.2.0 (ms@0.7.1)
├── osenv@0.1.3 (os-tmpdir@1.0.1, os-homedir@1.0.0)
├── serve-favicon@2.3.0 (fresh@0.3.0, etag@1.7.0, ms@0.7.1, parseurl@1.3.0)
├── compression@1.5.1 (bytes@2.1.0, vary@1.0.1, on-headers@1.0.0, compressible@2.0.4, accepts@1.2.11)
├── errorhandler@1.4.1 (escape-html@1.0.2, accepts@1.2.11)
├── concat-stream@1.5.0 (inherits@2.0.1, typedarray@0.0.6, readable-stream@2.0.2)
├── loopback-boot@2.8.11 (commondir@0.0.1, toposort@0.2.10, semver@4.3.6)
├── strong-tunnel@1.1.9 (ssh2@0.4.10)
├── request@2.58.0 (caseless@0.10.0, aws-sign2@0.5.0, forever-agent@0.6.1, stringstream@0.0.4, tunnel-agent@0.4.1, oauth-sign@0.8.0, isstream@0.1.2, extend@2.0.1, json-stringify-safe@5.0.1, node-uuid@1.4.3, qs@3.1.0, combined-stream@1.0.5, mime-types@2.0.14, bl@0.9.4, form-data@1.0.0-rc1, http-signature@0.11.0, tough-cookie@2.0.0, hawk@2.3.1, har-validator@1.8.0)
├── strong-npm-ls@1.0.8 (topiary@1.1.1, read-installed@3.1.5)
├── http-auth@2.2.8 (node-uuid@1.4.1, htpasswd@2.2.0)
├── loopback-datasource-juggler@2.33.8 (depd@1.0.1, inflection@1.7.1, node-uuid@1.4.3, qs@3.1.0, async@1.0.0, traverse@0.6.6, loopback-connector@2.2.4)
├── lodash@3.10.0
├── loopback-explorer@1.8.6 (debug@1.0.4, cors@2.7.1, lodash@2.4.2, express@3.21.1, strong-swagger-ui@20.0.8)
└── loopback@2.19.2 (sl-blip@1.0.0, uid2@0.0.3, nodemailer-stub-transport@0.1.5, stable@0.1.5, canonical-json@0.0.4, depd@1.0.1, inflection@1.7.1, loopback-phase@1.2.2, loopback-connector-remote@1.0.7, bcryptjs@2.2.0, ejs@2.3.3, underscore.string@3.1.1, continuation-local-storage@3.1.4, body-parser@1.13.2, express@4.13.1, nodemailer@1.4.0, strong-remoting@2.20.1)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment