White popup. Add example?

[peteruithoven]

I've followed the instructions from the readme, but when I visit my project and open the extension it shows a white popup. Probably a javascript error. But I've never made a Chrome extension and I don't know how to debug it.
It would be great if there was a live example (todo?) website that I could visit to check if it was something in my project (not using window.devToolsExtension correctly).

[peteruithoven]

Following the instructions from #2 (comment) I build the dev folder and loaded that as extension and suddenly the location of the exention icon changes and it does show the debugger.
Extension from: build/extension:

Extension from dev:

This is while trying this on the same project.

[zalmoxisus]

Yes, in ./build/extension we have the previous released version, while after npm start you get the upcoming version, which will be released today ;)
I will add ./buld to the .gitignore to avoid the confusions.
The main differences are described in #1.

I guess v0.0.1 didn't work because you loaded the page before loading the extension, just refresh the tab and it will work. Anyway, the new implementation should avoid such issues by hiding/showing pageAction's icon.

So, the upcoming release from dev works well?

[peteruithoven]

Ah, thanks that clarifies that, sounds like a great improvement.

But the new (dev) version doesn't fully work I'm getting the following error in my console:

Uncaught DataCloneError: Failed to execute 'postMessage' on 'Window': An object could not be cloned.
  onChange @ page.bundle.js:30356
  (anonymous function) @ createStore.js:52
  dispatch @ createStore.js:50
  dispatch @ page.bundle.js:12277
  (anonymous function) @ bindActionCreators.js:12
  mouseMove @ group.js:374
  handleEvent @ group.js:104

The debugger only shows the @@init action.
Using Redux version 3.0.4. Are there other versions relevant?

(Again it would help to check this with a page that the debugger does work with)

[zalmoxisus]

We have the same issue in #5, but I cannot reproduce it. I just released 0.1.0. Could you please sync the git and try again with ./build/extension?

[zalmoxisus]

To test it, you may just use counter or mvc example from ./examples, just do npm i and npm start there. It should run on port 4001 and 4002.

[peteruithoven]

I'll check with that example. I'll report issues relating to that postMessage in #5.
If you think it's a good idea this issue could serve as a todo to make a example website.

[zalmoxisus]

Yes. That would be really useful, especially when we'll have the extension in Chrome WebStore.