Asking for donations via terminal is a thing? Programmer thing 😎

Next up -

# npm install x
Run npm donate x to Donate $2.99 to continue

# npm donate x
Thank for purchasing your 7 day trial
Run npm donate x -- personal
To enable personal edition for $12.99 / month or
Run npm donate x --commercial
To enable commercial edition for $199.99 per month

Ad-ridden CLI utilities?
Is that what's next?

Yeah, I'm totally going to snap and become a serial killer someday. No exaggeration.

I have seen this, too.

But as someone who hates ADs i find that ok.

Such tools remove the need for you to go onto their git page and see the donation request there. So it's only fair to add that.

I doubt that everybody will (ab)use this. But I could be proven wrong there.

Of course, having setting to disable the message to reduce clutter would be nice (didn't check if it already does).

Edit: I'm also not a js/node dev.

@C0D4 Then reinventing the wheel will become the smartest thing to do

Just don't use that crap.

There is this npm alternative launched by former npm CTO called "Entropic" (https://github.com/entropic-dev/...)

Oh no, how dare these people discreetly ask for a complelely optional, small amount of financial support for the many hours of work that they've put into the software you're using for your own project (possibly for financial gain).

Those greedy arseholes.

Eric Raymond would cry tears of blood if he saw this.

@kwilliams Cluttering my npm output log that's important for debugging with a wall of advertisements and slowing down the install process because they add a postinstall script just for that is definitely an asshole move.

If this becomes mad adridden, I will srsly consider forking npm and removing all the shit.

If this becomes mad adridden, I will srsly consider forking npm and removing all the shit.

@PrivateGER This is one message, and that's an assumed slippery slope. Packages can and will filter their dependencies, such that those who don't save enough effort compared to the CLI junk they produce will get less and less dependants. This will set a balance where only those packages can afford to ask for donations which are actually important. This is actually a very healthy self-regulating process, and it has the potential to solve the massive financing issues of npm.

@aggelalex How exactly would you fork an archive?

@Lor-inc Nope, just fork npm to remove all the idiotic "fund" functionality.

@Lor-inc It's not a slippery slope, it's already happening. My current project gets multiple custom message from core.js every time I run npm install because the author wants a job and thinks it's totally a nice idea to spam everybody's logs with his dumb postinstall script to spread his message everywhere.

@Root , pretty much, https://google.com/amp/s/...

Fucking Amp. Need to turn that shit off.

https://zdnet.com/article/...

@PrivateGER The fact that, despite this, core.js is still a dependency in many projects means that other package authors either don't want to replace it or don't care about the logs being clean. I think the latter is unlikely, but the former leads us to the conclusion that core.js saves a lot of work for package authors. Now, if someone saves so much work for so many people, maybe he shouldn't have to look for a job. Maye we as a society, as fellow developers, as people who fucking make money off of his work should share crumbs of our profit with him so he doesn't have to look for a full time job, beside supporting one of the most referenced packages on NPM. What do you think?

@aggelalex How? These are logging commands in post install. Would you block post-install hooks? Because that would disable a tad bit more than just ads.

@Lor-inc silence them?

I really agree with @Lor-inc here. Noone forces you to use anyones packages. But if you do, you Profit. For RREE. So it's only fair the author can ask for money, a job etc. Because they worked for you to profit.

Bernie, is that you?

@aggelalex You can't tell them apart from informative logs.

IMHO, there's no problem at all when open-source package creators & maintainers ask for funding, but there's a time & place. Perhaps it could be more suitably placed in the npm web client (think GitHub Sponsors), not the CLI.

And if you're using npm with Node.js, you're in luck because Deno v1 just came out. It adopts the Go approach, where there's no centralized package manager.

@Lor-inc you could just look for fund, coffee etc.

@eval Sounds doable, but it's an awful lot of work just to ensure that open source libraries don't get funding.

Well, you see,

50+ packages are looking for funding
run `npm fund` for details

Basically Nuxt.js dependencies