Skip to content
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

anyone have updated or working build instructions? #70

Closed
tamsky opened this issue Oct 12, 2018 · 4 comments
Closed

anyone have updated or working build instructions? #70

tamsky opened this issue Oct 12, 2018 · 4 comments

Comments

@tamsky
Copy link

tamsky commented Oct 12, 2018

I tried taking some time today to build this project on my local machine but came up rather empty.

I took the steps from the README and put them into a Dockerfile:

tamsky@730bc75

I expected that running the steps listed in the README would result in a working unpacked extension directory, that I can then point chrome at and the extension should work similar to the one in the chrome web store.

Currently gulp does not appear to even produce a required file: //public/js/events.js which is listed in //manifest.json
Chrome refuses to load the unpacked extension due to the missing manifest item.

If, out of curiousity, I uncomment a few currently commented out lines in the //gulpfile.js:
https://github.com/wakatime/chrome-wakatime/blob/6226b779225df99a5590ac4918e937e7823682c6/gulpfile.js#L51-L58

And rebuild using a similar Dockerfile... then gulp does produce the //public/js/events.js file, and the resulting extension does load unpacked in chrome.

But the extension doesn't function... it has show stopper errors like:
Uncaught TypeError: WakaTimeCore is not a constructor and
Uncaught TypeError: Cannot read property 'ReactDebugCurrentFrame' of undefined

Before going down any more debugging roads, can anyone tell me what I'm doing right, and what I'm doing wrong, and what I should be doing differently?

@tamsky
Copy link
Author

tamsky commented Oct 28, 2018

@VladimirMilenko I noticed you've recently pushed commits to a fork of this repo.

Do you have any advice on how to get a new build working?

@Eeems
Copy link
Contributor

Eeems commented Feb 20, 2019

See #75

@Eeems
Copy link
Contributor

Eeems commented Apr 17, 2019

@tamsky This should be resolved now. Could you confirm?

@alanhamlett
Copy link
Member

npm i && npm run build

or

npm i && npm run watch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants