Whitelist of WakaTime Not Work

[Hephaest]

trafficstars

Currently, I set a host domain in order to record my Jupyter Notebook but I found it doesn't work at all.

Version 1.0.2

[llinfeng]

Instead of logging 0 minutes, the following setting logs more hours than the time I spent "actively" tinkering with Jupyter notebooks. I am also with Version 1.0.2.

[alanhamlett]

Can you try loading the extension from source code, using master branch of this repo?

[marcopollacci]

Can you try loading the extension from source code, using master branch of this repo?

Hi, there are any updated instruction to build project?

[llinfeng]

@marcopollacci Thank you for asking what was my initial response. I finally got motivated to give it a try after two weeks.

For now, well, just don't bother with building it quite yet. The extension in the master branch does not do much :) It has an empty option field. My notes for building the project are at the bottom, after the divider.

---

These are based on a similar note for Firefox, posted in issue #49, per this post.

# 1. clone this repo
# 2. cd to the folder
# 3. get `npm` ready: otherwise, I get `clap not found` error
npm install
# 4. build the extension locally
npm start
# Should things compile, finally, you can try to "load" the following directory via Developer mode
# Path: /chrome-wakatime/dist/chrome

Note the following:

1. These steps worked on a Linux Mint machine, but not on a WSL Pengwin instance. I installed npm through conda on both machines.
2. The Developer mode thing does not with Chrome from Google. I used Vivaldi instead. (Ref: https://superuser.com/a/768154)

[vujita]

Sorry, I'll add some notes to the readme later. That is instructions for the new build path.

The released version is just sourcing it from the repo folder

[marcopollacci]

I'll looking for the new instruction, thank you :)

[llinfeng]

@vujita Could you speak of the "OPTIONS GO HERE" in the screenshot, and when will it be fixed if it is a bug (or produced by an unpushed commit)?

[vujita]

The current production build is from assets, and builds to the repo level folder.

The future build from src and will go into dist, this is still in the works

[llinfeng]

I don't quite follow what you said. Could you detail the steps for "production build"? I have no idea how to deal with the two folders in assets/.

[vujita]

The published extension source code is in assets This will build the js/css to a git ignored public folder. Then you load the extension from the same folder as the repo, not dist

The next build will build into a dist folder, and will be sourced from there. I am in the middle of porting it over and want to leave what is currently released untouched

[llinfeng]

Sounds good (though, it still did not get me to try what @alanhamlett was suggesting in the first place).

Nevertheless, looking forward to a new release. Here is a running list of problems I have encountered:

1. With a whitelisted tab loaded in a tab, when I leave the browser window, the timer keeps counting the idle hours.
2. Need a pointer to "load the extension from source code".

[jvelezpo]

Solved on V3 👍