Receive reports from users and get them replicated right in the extension #20
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why to use
Using monitoring services (like Sentry, Rollbar, TrackJS), you could add your action history to the report along with other info, but the payload could be too big to include and we don't want to copy actions from the report manually to Redux DevTools extension.
By running
remotedev-server
on your server, you can get action history right in the extension just by clicking the link from a report.How to use
npm i -g remotedev-server@beta
(or include in your app).remotedev --hostname=localhost --port=8000
(or start with you app).http://localhost:8000
(instead oflocalhost
you could have an external host) your action history (tracked in a redux middleware):http://hostname/?remotedev_report=${id}
(wherehostname
can be your development or production domain).Yo can use
redux-remotedev
, which will handle 4-5 for you. Orremote-redux-devtools
withsendOn
and/orsendOnError
parameters. Alsoredux-trackjs-logger
sends reports along with trackjs logs (included the reproduction url).