-
-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not Installing on MAc OS #587
Comments
also 4.2.0 does not seem to be in the registry |
Confirmed, cannot install via NPM as of writing. Was working last night 4-29-24 ~8PM CDT |
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 |
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. |
@thegafo please keep us updated on the forked version, if you do. |
I can understand that he don't want to contribute to future versions, but remove the old ones is quite wrong IMO. |
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. |
@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 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. |
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:
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. 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 |
🤡 |
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.
The text was updated successfully, but these errors were encountered: