Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Expose mirror
See original GitHub issuePR #407 changes the way accessing the mirror works. Using import { mirror } from 'rrweb' to access the mirror doesn’t work anymore. This breaks getMirror() on the rrweb player.
Proposed solution A:
Maybe we can expose the mirror by also adding a getMirror() method on the rrweb replayer to re-enable this behaviour.
Proposed solution B:
Alternatively we can make the mirror attribute public on the replayer instead of private:
https://github.com/rrweb-io/rrweb/blob/0f86a72705b998a9abf5b4aae5b01a4f3b679954/src/replay/index.ts#L124
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@Juice10 Thanks for the report.
I merge this PR because it’s a breaking change and will be released in v1.0.
For general usage, I think solution B is good enough. And I’m also thinking about adding some warning if someone is using
import { mirror } from 'rrweb', do you have any ideas about this?@Juice10 Please let me know whether the latest commit works.