nut-tree/nut.js

Not Installing on MAc OS

namangoel993 opened this issue · 10 comments

namangoel993 commented

Not Found - GET https://registry.npmjs.org/@nut-tree%2fnut-js - Not found
npm ERR! 404
npm ERR! 404 '@nut-tree/nut-js@^3.1.1' is not in this registry.
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

HydAu commented

also 4.2.0 does not seem to be in the registry

aodekirk88 commented

Confirmed, cannot install via NPM as of writing. Was working last night 4-29-24 ~8PM CDT

s1hofmann commented

This is correct and has been explained here: https://nutjs.dev/blog/i-give-up

Prebuilt packages are no longer publicly available.

Best regards

Simon

  • 👎2
  • 😕1
thegafo commented

Pretty hostile, but I understand. We'll just have to fork it and publish a new NPM package.

I appreciate your open source work while it lasted. Best wishes.

  • 😕1
parikshit-dp commented

@thegafo please keep us updated on the forked version, if you do.

  • 👍2
davidarroyo1234 commented

Pretty hostile, but I understand. We'll just have to fork it and publish a new NPM package.

I appreciate your open source work while it lasted. Best wishes.

I can understand that he don't want to contribute to future versions, but remove the old ones is quite wrong IMO.

  • 👍2
mnn commented

I was recommended this project by Perplexity as a FOSS library for simulating keyboard input, I wanted to simply send a keystroke from my toy project. Unreleasing from NPM in this fashion is a very aggressive move and will burn bridges with any developer even remotely interested in open-source. I will rather try a decade old alternative, or if that (most likely) fails, I'll just use a platform specific hack than trying to make some foss-hostile project running and incur same pain on my potential users.

  • 😕1
thegafo commented

@mnn we are in the exact same boat. I was simply using this package for simulating keyboard input as well, and have had to fall back to old, bloated alternatives like robot.js.

Totally agree taking it off NPM was a hostile, aggressive move that will definitely burn bridges. I'm in the process of forking everything to a different project so we can at least keep the existing functionality. I will keep you posted.

s1hofmann commented

I'll just use a platform specific hack than trying to make some foss-hostile project running and incur same pain on my potential users.

Isn’t it ironic to call nut.js FOSS hostile, in an issue opened in the still open, still Apache-2.0 licensed repo that is the unmodified source of truth for the unpublished packages?

I get it, you’re upset because I removed my public packages and caused some disturbance in your projects, that’s your right.

But let me tell you one more time:

  • I notified open source projects like Electron early on about the upcoming changes [1] I can only do that for projects that use nut.js I know of 🤷‍♂️
  • I linked the blog post in the very top of the readme so people would see it
  • I explicitly kept the repo open
  • I explicitly did not change its license
  • As I wrote in my post, I’ll still update the repo, but with a delay

If the fact that you have to build something from sources keeps you from using it, what’s the point of open source?

I decided to go this way to establish a way to keep maintaining this project in a sustainable way.
I dedicated a tremendous amount of my time and money to it over the last five and a half years and I would be happy to continue doing this without fully burning out or being treated like shit.

If you consider this project now open source hostile because of this, I’m more than happy to burn any bridge I’ll encounter.

I’ll close this issue now, since there is nothing left to add.

[1] https://discord.com/channels/745037351163527189/745037351725826080/1228311338418438214

thegafo commented

🤡