Installation fails related to depency on inherits
See original GitHub issuesudo npm install --global somafm
...
npm` http 200 https://registry.npmjs.org/spdx-license-ids
npm http GET https://registry.npmjs.org/is-utf8
npm http 304 https://registry.npmjs.org/is-utf8
/bin/somafm -> /lib/node_modules/somafm/cli.js
npm WARN unmet dependency /lib/node_modules/block-stream requires inherits@'~2.0.0' but will load
npm WARN unmet dependency undefined,
npm WARN unmet dependency which is version undefined
npm WARN unmet dependency /lib/node_modules/fstream requires inherits@'~2.0.0' but will load
npm WARN unmet dependency undefined,
npm WARN unmet dependency which is version undefined
npm WARN unmet dependency /lib/node_modules/fstream-ignore requires inherits@'2' but will load
npm WARN unmet dependency undefined,
npm WARN unmet dependency which is version undefined
npm WARN unmet dependency /lib/node_modules/fstream-npm requires inherits@'2' but will load
npm WARN unmet dependency undefined,
npm WARN unmet dependency which is version undefined
npm WARN unmet dependency /lib/node_modules/glob requires inherits@'2' but will load
npm WARN unmet dependency undefined,
npm WARN unmet dependency which is version undefined
npm WARN unmet dependency /lib/node_modules/npmconf requires inherits@'~2.0.0' but will load
npm WARN unmet dependency undefined,
npm WARN unmet dependency which is version undefined
npm WARN unmet dependency /lib/node_modules/tar requires inherits@'2' but will load
npm WARN unmet dependency undefined,
npm WARN unmet dependency which is version undefined
somafm@1.2.0 /lib/node_modules/somafm
├── term-title@1.0.0
├── object-assign@4.1.0
├── trim@0.0.1
├── minimist@1.2.0
├── isbin@0.0.2 (async@0.1.22)
├── chalk@1.1.3 (escape-string-regexp@1.0.5, supports-color@2.0.0, ansi-styles@2.2.1, has-ansi@2.0.0, strip-ansi@3.0.1)
├── cli-truncate@0.2.1 (slice-ansi@0.0.4, string-width@1.0.2)
├── copy-paste@1.3.0 (sync-exec@0.6.2, iconv-lite@0.4.13)
├── got@5.6.0 (is-redirect@1.0.0, lowercase-keys@1.0.0, is-stream@1.1.0, is-plain-obj@1.1.0, unzip-response@1.0.1, timed-out@2.0.0, is-retry-allowed@1.1.0, node-status-codes@1.0.0, read-all-stream@3.1.0, duplexer2@0.1.4, url-parse-lax@1.0.0, create-error-class@3.0.2, pinkie-promise@2.0.1, parse-json@2.2.0, readable-stream@2.1.5)
└── dateformat@1.0.12 (get-stdin@4.0.1, meow@3.7.0)
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Using inherited property in dependency classifier causes build ...
The error is saying that ${swt.classifier} isn't being recognized from a ... C needs B and B's dependencies so the installed/deployed .pom of...
Read more >`npm install` fails on postinstall: Cannot find module 'inherits'
I think this has to do with install/postinstall scripts that rely on the dependencies being present. Node-sass has a similar issue ...
Read more >Code Fix: Adding the same view twice to a form causes ...
When you add a view to a form twice, it causes inherited rule dependency errors on the form which results in you not...
Read more >Application installation common error codes reference
When an application fails to install and the error source is Configuration Manager, typically, following the application troubleshooting ...
Read more >Maven – Optional Dependencies and Dependency Exclusions
If a user wants to use functionality related to an optional dependency, they have to redeclare that optional dependency in their own project....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hey thanks very much, that did the trick! I had no idea the distro version of node could be so far behind.
Much appreciate your tip about nvm and your one-liner. Now on to enjoying this tool for my favorite radio station!
You need at least Node.js v4.0.0 to use this module. (The installer should have given you a warning.)
For Node version management, I recommend
n
or nvm. On my systems, I use this one-liner to installn
locally to~/local/node
:Then, to install the latest version of Node, run:
and finally upgrade npm:
I hope that helps.