zalmoxisus / remotedev Goto Github PK

This package uses very obsolete version of socketcluster-client which is incompatible with new socketcluster-server. There is a problem with protocol version.
Will this package be updated any soon?

With fable-compiler/fable-elmish/#18 adding a basic support for time-traveling debugging, I think I'll see reports of serialization problems from people trying to use it. The issue is F# adds certain features to the plain JS objects that don't survive the state roundtrip.
I'm mitigating the issue to a degree with an internal/provisional Fable features, but it would be really nice to just be able to do my own serialization.
Thank you!

I have a dependency that uses remotedev to connect to the redux store.

https://github.com/mobxjs/mobx-state-tree/blob/1b8614a454c9af2acbf06cb7a8d470c95a1d0e96/packages/mst-middlewares/src/redux.ts#L56

In the web everything is fine and that connects to the chrome extension, however in an electron app that installs the redux extensions using electron-devtools-installer, the electron redux tab says

No store found. Most likely you did not allow access to file URLs. See details.

Am I doing something wrong or does remotedev just not support this use case?

The readme shows extractState with a callback function, however, the implementation for that seems to be missing: https://github.com/zalmoxisus/remotedev/blob/master/src/devTools.js#L9

Hi, first of all, thanks for this handy module! I've managed to get it working with Ionic 2 and @ngrx/store (via @ngrx/store-devtools) for on-device remote debugging via a custom wrapper, and the inspector is working nicely!

The only minor issue I'm running into with remotedev is the way unsubscribe() is handled in the connect() function. It mistakenly assumes that the instanceId is an array index instead of the configured value in the connect options. Therefore, it never actually unsubscribes anything when it's called. (I see your chrome extension code handles this fine and just needs to be ported over here.)

Coincidentally, there's also a complementary bug that kind of neutralizes the problem in @ngrx/store-devtools, where they're calling unsubscribe() immediately upon subscription in their Observable wrapper instead of returning a lambda to call it (I'll be creating an issue over there soon as well). So this bug is temporarily allowing update actions to still be received by ngrx even though it's being called immediately after subscribe() lol. Unfortunately, it doesn't actually handle them correctly for time travel to work, but that's another issue to hopefully be resolved soon on their end.

Hey, can you please check http://remotedev.io/ domain.
It looks like it's expired or hacked.

Question from a Redux middleware Newby so forgive me if this is a stupid question.

I am using remotedev with Mobx-State-Tree and getting this warning:
window.devToolsExtension is deprecated in favor of window.__REDUX_DEVTOOLS_EXTENSION__, and will be removed in next version of Redux

Can I solve this somehow?

Hi, as I mentioned in the previous issue #4 I just created, I created a custom proxy for using remotedev with @ngrx/store via @ngrx/store-devtools.

I'm not a React/Redux expert and am unsure of what the expected format is, but I noticed that changes.state is a JSON string instead of an object in the subscribe callback. Currently, in my attempt to get time-travel debugging working, I'm calling changes.state = JSON.parse(changes.state) in my wrapper before passing it to the ngrx store devtools. Is this a bug in remotedev, or should the store devtools be parsing it on their end?

Thanks in advance!

I'm trying to figure out why the Chrome app always sends back a string of JSON (return value from extractState) whereas the remote.io/local web app returns a decoded plain JS object.

I can see in the message from the remotedev server (running locally) that the state is JSON but has been re-encoded as a JSON string when using the Chrome app. When using remotedev.io/local I can see that it's a JSON object.

I can't try it out in the Chrome Tool (RemoteDev DevTools) because that doesn't display correctly and claims all states are equal.

All this testing was done with the same server (npm remotedev-server), same program connecting to the server, but with different viewing applications.

Upgrade examples to latest version of Remotedev