joshlankford / wakatimecli Goto Github PK

Looks like .wakatimeKey is read from current dir not HOME DIR, which is less convenient as one might want to check wakatime stats anywhere.

As this page explain, it is generally a bad idea to not remove the ANSI Colors code if the output of the script is piped.
For example, it's hard to save the result of the command in a file for future use, or to pipe it to a pager.

Could you try to improve this?
cli-color has a function to remove ANSI codes from the text before it is printed.
It might not be to hard to detect if the output is piped or not (supports colors or not).
(For instance, I did it "manually" in Python, a few years ago.)

Thanks in advance 👍 !

Cool plugin. Could you consider allowing a user to access their position on the public leaderboards?

I had this commandline dashboard package installed, however it uses the wakatime command and shadows the official cli for logging. Since I am trying to develop a plug in, I would like to have this package uninstalled, however npm uninstall wakatimecli does not do the trick.

How about tracking time spent in terminal?

Many official WakaTime plugins read API key from $HOME/.wakatime.cfg, e.g. Intellij plugin and Vim plugin.

It would be awesome if WakaTimeCLI can read API key directly from the file (if it exists).

Still, awesome project. Thanks!

I test in OSX and Ubuntu, and do not run on Ubuntu.

All the time spent on ssh tunnel are not tracked

I liked that plugin and really helps but can you add some features like:

• last month => wakatime -month
• custom range like => wakatime -range 01-01-2015 01-02-2015
• run custom API calls like => wakatime -call "/api/v1/summary/daily params"

When I try to get wakatime weekly report in February 2nd, I got an error.
It's because the logic of date is (today - 6), so the result will be (-4)

var dd3 = dd-6;

Maybe need another library (e.g. datejs) to set the date.
So, it could be easier to get report in a week, two week, a month, 2 days, etc.

Hi,
I loved this extension a few years ago, and haven't used in a long time (I talk about it on my website, here).

I reinstalled it, and added the API through the (undocumented?) wakatime -api command, it worked.

But when try to get, for instance, wakatime -w weekly report, I encountered this error:

$ wakatime -w
error -  { Error: write EPROTO 139628127275904:error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure:s23_clnt.c:802:

    at _errnoException (util.js:1022:11)
    at WriteWrap.afterWrite [as oncomplete] (net.js:880:14) code: 'EPROTO', errno: 'EPROTO', syscall: 'write' }

Thanks in advance.

When I'm trying to get weekly tracked time and type wakatime -w, it returns me always null...

On Windows i was located in F: and then i ran wakatime -api my-api-key and I got this:

Error: ENOENT, open 'F:\Users\Mario\.wakafile'

When i changed my location to C: everything worked.

Maybe you can store .wakafile somewhere else to avoid this issue.