0fb8a6bfa8 | ||
---|---|---|
.github | ||
.vscode | ||
docs | ||
packages | ||
.eslintrc.js | ||
.gitignore | ||
.markdownlint.yml | ||
.npmignore | ||
.prettierrc | ||
.release-it.json | ||
.travis.yml | ||
CHANGELOG.md | ||
LICENSE | ||
README.md | ||
README.zh_CN.md | ||
guide.md | ||
guide.zh_CN.md | ||
lerna.json | ||
package.json | ||
tsconfig.eslint.json | ||
tsconfig.json | ||
yarn.lock |
README.md
rrweb
The rrweb documentary (in Chinese, with English subtitles)
I have joined Github Sponsors and highly appreciate your sponsorship.
rrweb refers to 'record and replay the web', which is a tool for recording and replaying users' interactions on the web.
Guide
📚 Read the rrweb guide here. 📚
Project Structure
rrweb is mainly composed of 3 parts:
- rrweb-snapshot, including both snapshot and rebuilding features. The snapshot is used to convert the DOM and its state into a serializable data structure with a unique identifier; the rebuilding feature is to rebuild the snapshot into corresponding DOM.
- rrweb, including two functions, record and replay. The record function is used to record all the mutations in the DOM; the replay is to replay the recorded mutations one by one according to the corresponding timestamp.
- rrweb-player, is a player UI for rrweb, providing GUI-based functions like pause, fast-forward, drag and drop to play at any time.
Roadmap
- rrdom: an ad-hoc DOM for rrweb session data #419
- storage engine: do deduplication on a large number of rrweb sessions
- more end-to-end tests
- compact mutation data in common patterns
- provide plugins via the new plugin API, including:
- XHR plugin
- fetch plugin
- GraphQL plugin
- ...
Internal Design
Contribute Guide
Since we want the record and replay sides to share a strongly typed data structure, rrweb is developed with typescript which provides stronger type support.
- Fork this repository.
- Run
yarn install
in the root to install required dependencies for all sub-packages (note:npm install
is not recommended). - Run
yarn dev
in the root to get auto-building for all the sub-packages whenever you modify anything. - Navigate to one of the sub-packages (in the
packages
folder) where you'd like to make a change. - Patch the code and run
yarn test
to run the tests, make sure they pass before you commit anything. - Push the code and create a pull request.
Protip: You can run yarn test
in the root folder to run all the tests.
In addition to adding integration tests and unit tests, rrweb also provides a REPL testing tool.
Core Team Members
Yuyz0112 |
Mark-Fenng |
eoghanmurray |
Juice10 |