Open progers-de opened 1 month ago
This version of the cli is getting a bit stale and I've been working on it in my fork https://github.com/beauraines/rtm-cli
rtm whoami
does it return your auth token? The login command should have writtten some user
and user.client
information in ~/.rtm.json
@progers-de I've edited my comment because I sent it too soon!
Thanks for your reply!
- Are you running this from the repo or from the npm package?
I was downloading an executable directly. I just tried pulling the latest windows exe and got the same results.
However, I did just install the tool from npm
and everything works as expected. (!!) So, thanks for that question :)
- if you run
rtm whoami
does it return your auth token?
With the exe, when I tested whether logout
would work, I could no longer log back in via login
(not my smartest move), so I couldn't test whoami
. (As you'd expect, the npm version works fine.)
I used this app many times a day. Very sad to see it doesn't work anymore.
I tried the fork at https://github.com/beauraines/rtm-cli. It installs but does not work. There is a syntax error :( I suck at javascript and really hate node :) so I can't debug.
@hlslaughter I've been publishing my fork to NPM you can install it from https://www.npmjs.com/package/@beauraines/rtm-cli I use my version on a daily basis
If that doesn't help, what error are you getting?
Worse comes to worse, open an issue there and I'll check it out https://github.com/beauraines/rtm-cli/issues
Thank you. I would love to see this project continue. I'm a backend developer who spends most of his time on the Linux CLI. This tool saves me a lot of back and forth.
I hate working with anything js, but I'm happy to help debug. I'll post what I did and the results. It's reporting a syntax error and exiting, but I can't understand error output from node (even though I deal regularly with error messages from the rest of the lamp stack :)
@beauraines I was submitting a ticket to your project and realized that node upgrades major versions several times a day. I tried updating everything as best I could given the horrific lack of accurate documentation for the node things. I finally got at least node/npm/npx/n etc... updated. I had to add NODE_NO_WARNINGS=1
to my ENV to shut up deprecation warnings, and it now works fine.
Thanks!
Cool. I'm glad it's working!
Every command I try with
rtm
(except I thinklogout
?) produces a "cannot access API server" error, which makes this tool unusable:I've noticed this on all my Windows machines; they're all running Windows 11 Pro.