Using the command in iTerm does the job but it timeouts so you will have to relaunch it till it's done
OS: macOS Monetary
Chip: Apple M1
Total Number of Cores: 8 (4 performance and 4 efficiency)
Memory: 16 GB
oops. an error occured: Error: read ETIMEDOUT
at module.exports.sendError (/opt/homebrew/lib/node_modules/github-unfollow-everyone/node_modules/github/api/v3.0.0/index.js:30:19)
at /opt/homebrew/lib/node_modules/github-unfollow-everyone/node_modules/github/api/v3.0.0/user.js:728:29
at callCallback (/opt/homebrew/lib/node_modules/github-unfollow-everyone/node_modules/github/index.js:743:17)
at ClientRequest.<anonymous> (/opt/homebrew/lib/node_modules/github-unfollow-everyone/node_modules/github/index.js:809:17)
at ClientRequest.emit (node:events:527:28)
at TLSSocket.socketErrorListener (node:_http_client:442:9)
at TLSSocket.emit (node:events:527:28)
at emitErrorNT (node:internal/streams/destroy:164:8)
at emitErrorCloseNT (node:internal/streams/destroy:129:3)
at processTicksAndRejections (node:internal/process/task_queues:83:21) {
defaultMessage: 'Internal Server Error',
code: '500'
}
When interfacing with the GitHub API any number of things could potentially go wrong. The server might be down. Authentication might fail. The user could experience an edge-case that I overlooked. In any case, the error handling could be better. Ideally, the resulted error argument will contain information about the specific error that caused the operation to fail.
Progress reporting
Similar to how bcrypt accepts a progress report callback, this module should do something similar and report when usernames are found and they said users are unfollowed.
Meaningful result argument
At the moment the resulted result argument is not useful. It would be good if it contained information about the operation such as how many users were unfollowed.
If you desire any of these let me know, and I will work on them ๐.