Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
'opencollective' is not recognized as an internal or external command, operable program or batch file.
See original GitHub issueI think it’s awesome to be opting in to opencollective, but while installing level, I ran into things that weren’t very user-friendly.
First, I had to install it under an administrator powershell (or command prompt I suppose would work). I don’t recall ever having to do that on a project-level installation for node. Once I’d done that, I got the error that opencollective wasn’t recognized as a program. So I had to npm i -g opencollective just to be able to be told “thanks for using level! please donate!”
It seems a little counterintuitive to require a global installation of a module just to request donations after the package is installed - otherwise the package just doesn’t install because it fails on postinstall.
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Install npm i -g opencollective. Then install npm install --save opencollective-postinstall
its work for me
@ralphtheninja is right, npm isn’t tryint to install this tool locally for you, it will install it into
./node_modules/.bin/and call it from there.You see, this is the particular file that npm complains about not being able to rename:
D:\home\devel\enmap-level\node_modules\wrappy\package.json.We can’t help debug npm setups here unfortunately, please create an issue at https://github.com/npm/npm.