Closed moritonal closed 2 years ago
npm fund does very very little, if anything.
I can't remember the last time I ran the command and I'd ask you the same question (or if you're even supporting nodemon).
So I'd rather find suggestions on how to silence or fix this error that happens in powershell (I'm not a Windows user so you'll need to help or wait for someone who is willing to).
Damm, I'm glad you've managed to commercialise your success, but your response of "if you're even supporting nodemon" comes across pretty rough when it seems "support" means pay you to update a sponsor list?
The way I see it:
nodemon
, which asks for money to pay a monthly retainer to help you manage the PRs of other contributors (who aren't paid?).No worries, I've forked and can just use that, just thought I'd try help. The issue is valid and luckily the project is healthily supported so you can fix it on your time.
This has also been a problem for years #2007, #1663, #1478, #1695.
Glad you "fixed" it for yourself.
I originally wrote a long answer to your original longer comment, but it's not worth posting. You think what you want to think and ignore longevity of this project and the 12 years I've been maintaining it.
Anyone coming along to this, there's a solution here: https://github.com/remy/nodemon/issues/1663#issuecomment-882045518
npm i -g nodemon
When trying to install
nodemon
on my Windows machine, I hit a weird problem I've seen elsewhere, the open-collective post-install hack fails.Expected behaviour
I'd hope it'd install without crashing
Actual behaviour
It crashes brining the whole
npm i
process to a halt.Steps to reproduce
npm i -g nodemon
, but on my slightly odd Windows pseudo-powershell setup. I could go into the particulars, but the honest question is shouldnodemon
require apost-install
script? Especially given the project already supportsnpm fund
?