Redux-devtools-extension: Chrome extension broke today.. blank page

[born2net]

see here:

[nickw444]

Also having the same issue. Won't load on the sample github.io pages either.

[born2net]

Is there a way to lock out updates?
I really would rather stay with a stable version and not be "pushed" updates

[nickw444]

I just checked out 2.1.0, and built the extension and installed as a unpacked extension for now.

[born2net]

ok tx.. I'll wait for the fix

[yarcub]

@zalmoxisus: What do you think on having some sort of different channels (stable vs "canary") for the extension? Maybe publish the _canary_ one as unlisted so that anyone searching through the chrome web store doesn't install a not stable version.

That way we could have feedback, from people who actively follow this project and opt-in for it, if there was some breaking changes. 💭

[wnewby]

... broken here too. Built and running 2.10

[nickw444]

Saving a the time of others who may need to build this. Here is a zip of the unpacked build of 2.10

extension.zip

[j-]

Also experiencing this problem (v2.2.0.2). Console has the following error (possibly related to #147):

[pcanterini]

Looks like a typo in App.js

localStorage.getItem('monitor' + monitorPosition])
------------------------------------------------^

But I've also had some issues with the remotedev-app package when trying to build this version of the redux-devtools-extension. For one it's failing linting on prepublish

[johnkueh]

Same here - breaking ...

[andrewmclagan]

ouch 4 hours later... found this issue :-(

[jasan-s]

@nickw444 the build only work in external window not in the chrome dev panel. is that chrome thing for unpacked extentions?

[xyc]

+1

[tedscape]

+1

[zalmoxisus]

Sorry about that.

@tomchentw fixed it in #151 also added ESLint prebuilt tasks to avoid such cases.

2.2.0.3 is published on Chrome Store and should be available in about an hour.

[zalmoxisus]

@born2net,

Is there a way to lock out updates?

Yes, you can clone this repository and build it.

@yarcub,

@zalmoxisus: What do you think on having some sort of different channels (stable vs "canary") for the extension? Maybe publish the canary one as unlisted so that anyone searching through the chrome web store doesn't install a not stable version.
That way we could have feedback, from people who actively follow this project and opt-in for it, if there was some breaking changes. 💭

Extensions from Chrome store are autoupdated by Chrome automatically. There's a way to make a new release available only for a randomly selected amount of people, to get the feedback, which should help in such cases. Though much better would be to have good tests here, so I wouldn't have to check manually every PR.

[andrewmclagan]

@zalmoxisus again thanks for all your work