This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
⚠️⚠️⚠️⚠️⚠️⚠️
master is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on master.
⚠️⚠️⚠️⚠️⚠️⚠️
Releases
@rrweb/all@2.0.0-alpha.15
Major Changes
#14972606a2a Thanks @Juice10! - Distributed files have new filenames, paths and extensions. Important: If you reference distributed files or types directly, you might have to update your paths/filenames. E.g. you import from rrweb/typings/... or rrdom/es. However you run import rrweb from 'rrweb' you won't notice a difference with this change. If you include rrweb files directly in a script tag, you might have to update that path to include a the .umd.cjs files instead. All .js files now use ES modules which can be used in modern browsers, node.js and bundlers that support ES modules. All npm packages now also ship .cjs and .umd.cjs files. The .umd.cjs files are CommonJS modules that bundle all files together to make it easy to ship one file to browser environments (similar to the previous .js files). The .cjs files are CommonJS modules that can be used in older Node.js environments. Types should be better defined in package.json and if you need specific types they might be exported from new packages (for example PlayerMachineState and SpeedMachineState are now exported from @rrweb/replay). Check the package.json's main and exports field for the available files.
#14972606a2a Thanks @Juice10! - Remove the rrweb-all.js, rrweb-record.js, and rrweb-replay.js files from rrweb package. Now you can use @rrweb/all, @rrweb/record, and @rrweb/replay packages instead. Check out the README of each package for more information or check out PR #1033 to see the changes.
#14972606a2a Thanks @Juice10! - Split plugins out of rrweb and move them into their own packages: @rrweb/packer, @rrweb/rrweb-plugin-canvas-webrtc-record, @rrweb/rrweb-plugin-canvas-webrtc-replay, @rrweb/rrweb-plugin-sequential-id-record, @rrweb/rrweb-plugin-sequential-id-replay, @rrweb/rrweb-plugin-console-record, @rrweb/rrweb-plugin-console-replay. Check out the README of each package for more information or check out https://github.com/rrweb-io/rrweb/pull/1033 to see the changes.
#14972606a2a Thanks @Juice10! - Distributed files have new filenames, paths and extensions. Important: If you reference distributed files or types directly, you might have to update your paths/filenames. E.g. you import from rrweb/typings/... or rrdom/es. However you run import rrweb from 'rrweb' you won't notice a difference with this change. If you include rrweb files directly in a script tag, you might have to update that path to include a the .umd.cjs files instead. All .js files now use ES modules which can be used in modern browsers, node.js and bundlers that support ES modules. All npm packages now also ship .cjs and .umd.cjs files. The .umd.cjs files are CommonJS modules that bundle all files together to make it easy to ship one file to browser environments (similar to the previous .js files). The .cjs files are CommonJS modules that can be used in older Node.js environments. Types should be better defined in package.json and if you need specific types they might be exported from new packages (for example PlayerMachineState and SpeedMachineState are now exported from @rrweb/replay). Check the package.json's main and exports field for the available files.
#14972606a2a Thanks @Juice10! - Split plugins out of rrweb and move them into their own packages: @rrweb/packer, @rrweb/rrweb-plugin-canvas-webrtc-record, @rrweb/rrweb-plugin-canvas-webrtc-replay, @rrweb/rrweb-plugin-sequential-id-record, @rrweb/rrweb-plugin-sequential-id-replay, @rrweb/rrweb-plugin-console-record, @rrweb/rrweb-plugin-console-replay. Check out the README of each package for more information or check out https://github.com/rrweb-io/rrweb/pull/1033 to see the changes.
#14972606a2a Thanks @Juice10! - Distributed files have new filenames, paths and extensions. Important: If you reference distributed files or types directly, you might have to update your paths/filenames. E.g. you import from rrweb/typings/... or rrdom/es. However you run import rrweb from 'rrweb' you won't notice a difference with this change. If you include rrweb files directly in a script tag, you might have to update that path to include a the .umd.cjs files instead. All .js files now use ES modules which can be used in modern browsers, node.js and bundlers that support ES modules. All npm packages now also ship .cjs and .umd.cjs files. The .umd.cjs files are CommonJS modules that bundle all files together to make it easy to ship one file to browser environments (similar to the previous .js files). The .cjs files are CommonJS modules that can be used in older Node.js environments. Types should be better defined in package.json and if you need specific types they might be exported from new packages (for example PlayerMachineState and SpeedMachineState are now exported from @rrweb/replay). Check the package.json's main and exports field for the available files.
#14972606a2a Thanks @Juice10! - Split plugins out of rrweb and move them into their own packages: @rrweb/packer, @rrweb/rrweb-plugin-canvas-webrtc-record, @rrweb/rrweb-plugin-canvas-webrtc-replay, @rrweb/rrweb-plugin-sequential-id-record, @rrweb/rrweb-plugin-sequential-id-replay, @rrweb/rrweb-plugin-console-record, @rrweb/rrweb-plugin-console-replay. Check out the README of each package for more information or check out https://github.com/rrweb-io/rrweb/pull/1033 to see the changes.
#14972606a2a Thanks @Juice10! - Distributed files have new filenames, paths and extensions. Important: If you reference distributed files or types directly, you might have to update your paths/filenames. E.g. you import from rrweb/typings/... or rrdom/es. However you run import rrweb from 'rrweb' you won't notice a difference with this change. If you include rrweb files directly in a script tag, you might have to update that path to include a the .umd.cjs files instead. All .js files now use ES modules which can be used in modern browsers, node.js and bundlers that support ES modules. All npm packages now also ship .cjs and .umd.cjs files. The .umd.cjs files are CommonJS modules that bundle all files together to make it easy to ship one file to browser environments (similar to the previous .js files). The .cjs files are CommonJS modules that can be used in older Node.js environments. Types should be better defined in package.json and if you need specific types they might be exported from new packages (for example PlayerMachineState and SpeedMachineState are now exported from @rrweb/replay). Check the package.json's main and exports field for the available files.
Patch Changes
#10337261c43 Thanks @Juice10! - Export ReplayPlugin from rrweb directly. Previously we had to do import type { ReplayPlugin } from 'rrweb/dist/types'; now we can do import type { ReplayPlugin } from 'rrweb';
#14972606a2a Thanks @Juice10! - Split plugins out of rrweb and move them into their own packages: @rrweb/packer, @rrweb/rrweb-plugin-canvas-webrtc-record, @rrweb/rrweb-plugin-canvas-webrtc-replay, @rrweb/rrweb-plugin-sequential-id-record, @rrweb/rrweb-plugin-sequential-id-replay, @rrweb/rrweb-plugin-console-record, @rrweb/rrweb-plugin-console-replay. Check out the README of each package for more information or check out https://github.com/rrweb-io/rrweb/pull/1033 to see the changes.
#14972606a2a Thanks @Juice10! - Distributed files have new filenames, paths and extensions. Important: If you reference distributed files or types directly, you might have to update your paths/filenames. E.g. you import from rrweb/typings/... or rrdom/es. However you run import rrweb from 'rrweb' you won't notice a difference with this change. If you include rrweb files directly in a script tag, you might have to update that path to include a the .umd.cjs files instead. All .js files now use ES modules which can be used in modern browsers, node.js and bundlers that support ES modules. All npm packages now also ship .cjs and .umd.cjs files. The .umd.cjs files are CommonJS modules that bundle all files together to make it easy to ship one file to browser environments (similar to the previous .js files). The .cjs files are CommonJS modules that can be used in older Node.js environments. Types should be better defined in package.json and if you need specific types they might be exported from new packages (for example PlayerMachineState and SpeedMachineState are now exported from @rrweb/replay). Check the package.json's main and exports field for the available files.
#14972606a2a Thanks @Juice10! - Split plugins out of rrweb and move them into their own packages: @rrweb/packer, @rrweb/rrweb-plugin-canvas-webrtc-record, @rrweb/rrweb-plugin-canvas-webrtc-replay, @rrweb/rrweb-plugin-sequential-id-record, @rrweb/rrweb-plugin-sequential-id-replay, @rrweb/rrweb-plugin-console-record, @rrweb/rrweb-plugin-console-replay. Check out the README of each package for more information or check out https://github.com/rrweb-io/rrweb/pull/1033 to see the changes.
#14972606a2a Thanks @Juice10! - Distributed files have new filenames, paths and extensions. Important: If you reference distributed files or types directly, you might have to update your paths/filenames. E.g. you import from rrweb/typings/... or rrdom/es. However you run import rrweb from 'rrweb' you won't notice a difference with this change. If you include rrweb files directly in a script tag, you might have to update that path to include a the .umd.cjs files instead. All .js files now use ES modules which can be used in modern browsers, node.js and bundlers that support ES modules. All npm packages now also ship .cjs and .umd.cjs files. The .umd.cjs files are CommonJS modules that bundle all files together to make it easy to ship one file to browser environments (similar to the previous .js files). The .cjs files are CommonJS modules that can be used in older Node.js environments. Types should be better defined in package.json and if you need specific types they might be exported from new packages (for example PlayerMachineState and SpeedMachineState are now exported from @rrweb/replay). Check the package.json's main and exports field for the available files.
Patch Changes
#10337261c43 Thanks @Juice10! - Export ReplayPlugin from rrweb directly. Previously we had to do import type { ReplayPlugin } from 'rrweb/dist/types'; now we can do import type { ReplayPlugin } from 'rrweb';
#14972606a2a Thanks @Juice10! - Split plugins out of rrweb and move them into their own packages: @rrweb/packer, @rrweb/rrweb-plugin-canvas-webrtc-record, @rrweb/rrweb-plugin-canvas-webrtc-replay, @rrweb/rrweb-plugin-sequential-id-record, @rrweb/rrweb-plugin-sequential-id-replay, @rrweb/rrweb-plugin-console-record, @rrweb/rrweb-plugin-console-replay. Check out the README of each package for more information or check out https://github.com/rrweb-io/rrweb/pull/1033 to see the changes.
#14972606a2a Thanks @Juice10! - Distributed files have new filenames, paths and extensions. Important: If you reference distributed files or types directly, you might have to update your paths/filenames. E.g. you import from rrweb/typings/... or rrdom/es. However you run import rrweb from 'rrweb' you won't notice a difference with this change. If you include rrweb files directly in a script tag, you might have to update that path to include a the .umd.cjs files instead. All .js files now use ES modules which can be used in modern browsers, node.js and bundlers that support ES modules. All npm packages now also ship .cjs and .umd.cjs files. The .umd.cjs files are CommonJS modules that bundle all files together to make it easy to ship one file to browser environments (similar to the previous .js files). The .cjs files are CommonJS modules that can be used in older Node.js environments. Types should be better defined in package.json and if you need specific types they might be exported from new packages (for example PlayerMachineState and SpeedMachineState are now exported from @rrweb/replay). Check the package.json's main and exports field for the available files.
#14972606a2a Thanks @Juice10! - Split plugins out of rrweb and move them into their own packages: @rrweb/packer, @rrweb/rrweb-plugin-canvas-webrtc-record, @rrweb/rrweb-plugin-canvas-webrtc-replay, @rrweb/rrweb-plugin-sequential-id-record, @rrweb/rrweb-plugin-sequential-id-replay, @rrweb/rrweb-plugin-console-record, @rrweb/rrweb-plugin-console-replay. Check out the README of each package for more information or check out https://github.com/rrweb-io/rrweb/pull/1033 to see the changes.
#14972606a2a Thanks @Juice10! - Distributed files have new filenames, paths and extensions. Important: If you reference distributed files or types directly, you might have to update your paths/filenames. E.g. you import from rrweb/typings/... or rrdom/es. However you run import rrweb from 'rrweb' you won't notice a difference with this change. If you include rrweb files directly in a script tag, you might have to update that path to include a the .umd.cjs files instead. All .js files now use ES modules which can be used in modern browsers, node.js and bundlers that support ES modules. All npm packages now also ship .cjs and .umd.cjs files. The .umd.cjs files are CommonJS modules that bundle all files together to make it easy to ship one file to browser environments (similar to the previous .js files). The .cjs files are CommonJS modules that can be used in older Node.js environments. Types should be better defined in package.json and if you need specific types they might be exported from new packages (for example PlayerMachineState and SpeedMachineState are now exported from @rrweb/replay). Check the package.json's main and exports field for the available files.
Patch Changes
#10337261c43 Thanks @Juice10! - Export ReplayPlugin from rrweb directly. Previously we had to do import type { ReplayPlugin } from 'rrweb/dist/types'; now we can do import type { ReplayPlugin } from 'rrweb';
#14972606a2a Thanks @Juice10! - Distributed files have new filenames, paths and extensions. Important: If you reference distributed files or types directly, you might have to update your paths/filenames. E.g. you import from rrweb/typings/... or rrdom/es. However you run import rrweb from 'rrweb' you won't notice a difference with this change. If you include rrweb files directly in a script tag, you might have to update that path to include a the .umd.cjs files instead. All .js files now use ES modules which can be used in modern browsers, node.js and bundlers that support ES modules. All npm packages now also ship .cjs and .umd.cjs files. The .umd.cjs files are CommonJS modules that bundle all files together to make it easy to ship one file to browser environments (similar to the previous .js files). The .cjs files are CommonJS modules that can be used in older Node.js environments. Types should be better defined in package.json and if you need specific types they might be exported from new packages (for example PlayerMachineState and SpeedMachineState are now exported from @rrweb/replay). Check the package.json's main and exports field for the available files.
#14972606a2a Thanks @Juice10! - Remove the rrweb-all.js, rrweb-record.js, and rrweb-replay.js files from rrweb package. Now you can use @rrweb/all, @rrweb/record, and @rrweb/replay packages instead. Check out the README of each package for more information or check out PR #1033 to see the changes.
#14972606a2a Thanks @Juice10! - Distributed files have new filenames, paths and extensions. Important: If you reference distributed files or types directly, you might have to update your paths/filenames. E.g. you import from rrweb/typings/... or rrdom/es. However you run import rrweb from 'rrweb' you won't notice a difference with this change. If you include rrweb files directly in a script tag, you might have to update that path to include a the .umd.cjs files instead. All .js files now use ES modules which can be used in modern browsers, node.js and bundlers that support ES modules. All npm packages now also ship .cjs and .umd.cjs files. The .umd.cjs files are CommonJS modules that bundle all files together to make it easy to ship one file to browser environments (similar to the previous .js files). The .cjs files are CommonJS modules that can be used in older Node.js environments. Types should be better defined in package.json and if you need specific types they might be exported from new packages (for example PlayerMachineState and SpeedMachineState are now exported from @rrweb/replay). Check the package.json's main and exports field for the available files.
#14972606a2a Thanks @Juice10! - Remove the rrweb-all.js, rrweb-record.js, and rrweb-replay.js files from rrweb package. Now you can use @rrweb/all, @rrweb/record, and @rrweb/replay packages instead. Check out the README of each package for more information or check out PR #1033 to see the changes.
#14972606a2a Thanks @Juice10! - Distributed files have new filenames, paths and extensions. Important: If you reference distributed files or types directly, you might have to update your paths/filenames. E.g. you import from rrweb/typings/... or rrdom/es. However you run import rrweb from 'rrweb' you won't notice a difference with this change. If you include rrweb files directly in a script tag, you might have to update that path to include a the .umd.cjs files instead. All .js files now use ES modules which can be used in modern browsers, node.js and bundlers that support ES modules. All npm packages now also ship .cjs and .umd.cjs files. The .umd.cjs files are CommonJS modules that bundle all files together to make it easy to ship one file to browser environments (similar to the previous .js files). The .cjs files are CommonJS modules that can be used in older Node.js environments. Types should be better defined in package.json and if you need specific types they might be exported from new packages (for example PlayerMachineState and SpeedMachineState are now exported from @rrweb/replay). Check the package.json's main and exports field for the available files.
#14972606a2a Thanks @Juice10! - Distributed files have new filenames, paths and extensions. Important: If you reference distributed files or types directly, you might have to update your paths/filenames. E.g. you import from rrweb/typings/... or rrdom/es. However you run import rrweb from 'rrweb' you won't notice a difference with this change. If you include rrweb files directly in a script tag, you might have to update that path to include a the .umd.cjs files instead. All .js files now use ES modules which can be used in modern browsers, node.js and bundlers that support ES modules. All npm packages now also ship .cjs and .umd.cjs files. The .umd.cjs files are CommonJS modules that bundle all files together to make it easy to ship one file to browser environments (similar to the previous .js files). The .cjs files are CommonJS modules that can be used in older Node.js environments. Types should be better defined in package.json and if you need specific types they might be exported from new packages (for example PlayerMachineState and SpeedMachineState are now exported from @rrweb/replay). Check the package.json's main and exports field for the available files.
#14972606a2a Thanks @Juice10! - Split plugins out of rrweb and move them into their own packages: @rrweb/packer, @rrweb/rrweb-plugin-canvas-webrtc-record, @rrweb/rrweb-plugin-canvas-webrtc-replay, @rrweb/rrweb-plugin-sequential-id-record, @rrweb/rrweb-plugin-sequential-id-replay, @rrweb/rrweb-plugin-console-record, @rrweb/rrweb-plugin-console-replay. Check out the README of each package for more information or check out https://github.com/rrweb-io/rrweb/pull/1033 to see the changes.
#14972606a2a Thanks @Juice10! - Distributed files have new filenames, paths and extensions. Important: If you reference distributed files or types directly, you might have to update your paths/filenames. E.g. you import from rrweb/typings/... or rrdom/es. However you run import rrweb from 'rrweb' you won't notice a difference with this change. If you include rrweb files directly in a script tag, you might have to update that path to include a the .umd.cjs files instead. All .js files now use ES modules which can be used in modern browsers, node.js and bundlers that support ES modules. All npm packages now also ship .cjs and .umd.cjs files. The .umd.cjs files are CommonJS modules that bundle all files together to make it easy to ship one file to browser environments (similar to the previous .js files). The .cjs files are CommonJS modules that can be used in older Node.js environments. Types should be better defined in package.json and if you need specific types they might be exported from new packages (for example PlayerMachineState and SpeedMachineState are now exported from @rrweb/replay). Check the package.json's main and exports field for the available files.
#14972606a2a Thanks @Juice10! - Remove the rrweb-all.js, rrweb-record.js, and rrweb-replay.js files from rrweb package. Now you can use @rrweb/all, @rrweb/record, and @rrweb/replay packages instead. Check out the README of each package for more information or check out PR #1033 to see the changes.
Patch Changes
#10337261c43 Thanks @Juice10! - Export ReplayPlugin from rrweb directly. Previously we had to do import type { ReplayPlugin } from 'rrweb/dist/types'; now we can do import type { ReplayPlugin } from 'rrweb';
#14684014305 Thanks @eoghanmurray! - inlineImages: during snapshot avoid adding an event listener for inlining of same-origin images (async listener mutates the snapshot which can be problematic)
#1489609b7fa Thanks @JonasBa! - Optimize performance of isParentRemoved by converting it to an iterative procedure
#149382f6fec Thanks @eoghanmurray! - Replay: Replace negative lookbehind in regexes from css parser as it causes issues with Safari 16
#14972606a2a Thanks @Juice10! - Distributed files have new filenames, paths and extensions. Important: If you reference distributed files or types directly, you might have to update your paths/filenames. E.g. you import from rrweb/typings/... or rrdom/es. However you run import rrweb from 'rrweb' you won't notice a difference with this change. If you include rrweb files directly in a script tag, you might have to update that path to include a the .umd.cjs files instead. All .js files now use ES modules which can be used in modern browsers, node.js and bundlers that support ES modules. All npm packages now also ship .cjs and .umd.cjs files. The .umd.cjs files are CommonJS modules that bundle all files together to make it easy to ship one file to browser environments (similar to the previous .js files). The .cjs files are CommonJS modules that can be used in older Node.js environments. Types should be better defined in package.json and if you need specific types they might be exported from new packages (for example PlayerMachineState and SpeedMachineState are now exported from @rrweb/replay). Check the package.json's main and exports field for the available files.
#14972606a2a Thanks @Juice10! - Distributed files have new filenames, paths and extensions. Important: If you reference distributed files or types directly, you might have to update your paths/filenames. E.g. you import from rrweb/typings/... or rrdom/es. However you run import rrweb from 'rrweb' you won't notice a difference with this change. If you include rrweb files directly in a script tag, you might have to update that path to include a the .umd.cjs files instead. All .js files now use ES modules which can be used in modern browsers, node.js and bundlers that support ES modules. All npm packages now also ship .cjs and .umd.cjs files. The .umd.cjs files are CommonJS modules that bundle all files together to make it easy to ship one file to browser environments (similar to the previous .js files). The .cjs files are CommonJS modules that can be used in older Node.js environments. Types should be better defined in package.json and if you need specific types they might be exported from new packages (for example PlayerMachineState and SpeedMachineState are now exported from @rrweb/replay). Check the package.json's main and exports field for the available files.
Patch Changes
#14684014305 Thanks @eoghanmurray! - inlineImages: during snapshot avoid adding an event listener for inlining of same-origin images (async listener mutates the snapshot which can be problematic)
#149382f6fec Thanks @eoghanmurray! - Replay: Replace negative lookbehind in regexes from css parser as it causes issues with Safari 16
#1482f3cf092 Thanks @AlfieJones! - (when recordCanvas: true): ensure we use doc.createElement instead of document.createElement to allow use in non-browser e.g. jsdom environments
tag; enabled when the 'all' value is used for slimDOM
@rrweb/types@2.0.0-alpha.15
Major Changes
#14972606a2a Thanks @Juice10! - Distributed files have new filenames, paths and extensions. Important: If you reference distributed files or types directly, you might have to update your paths/filenames. E.g. you import from rrweb/typings/... or rrdom/es. However you run import rrweb from 'rrweb' you won't notice a difference with this change. If you include rrweb files directly in a script tag, you might have to update that path to include a the .umd.cjs files instead. All .js files now use ES modules which can be used in modern browsers, node.js and bundlers that support ES modules. All npm packages now also ship .cjs and .umd.cjs files. The .umd.cjs files are CommonJS modules that bundle all files together to make it easy to ship one file to browser environments (similar to the previous .js files). The .cjs files are CommonJS modules that can be used in older Node.js environments. Types should be better defined in package.json and if you need specific types they might be exported from new packages (for example PlayerMachineState and SpeedMachineState are now exported from @rrweb/replay). Check the package.json's main and exports field for the available files.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
⚠️⚠️⚠️⚠️⚠️⚠️
master
is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exit
onmaster
.⚠️⚠️⚠️⚠️⚠️⚠️
Releases
@rrweb/all@2.0.0-alpha.15
Major Changes
#1497
2606a2a
Thanks @Juice10! - Distributed files have new filenames, paths and extensions. Important: If you reference distributed files or types directly, you might have to update your paths/filenames. E.g. you import fromrrweb/typings/...
orrrdom/es
. However you runimport rrweb from 'rrweb'
you won't notice a difference with this change. If you include rrweb files directly in a script tag, you might have to update that path to include a the.umd.cjs
files instead. All.js
files now use ES modules which can be used in modern browsers, node.js and bundlers that support ES modules. All npm packages now also ship.cjs
and.umd.cjs
files. The.umd.cjs
files are CommonJS modules that bundle all files together to make it easy to ship one file to browser environments (similar to the previous.js
files). The.cjs
files are CommonJS modules that can be used in older Node.js environments. Types should be better defined inpackage.json
and if you need specific types they might be exported from new packages (for examplePlayerMachineState
andSpeedMachineState
are now exported from@rrweb/replay
). Check thepackage.json
'smain
andexports
field for the available files.#1497
2606a2a
Thanks @Juice10! - Remove the rrweb-all.js, rrweb-record.js, and rrweb-replay.js files fromrrweb
package. Now you can use@rrweb/all
,@rrweb/record
, and@rrweb/replay
packages instead. Check out the README of each package for more information or check out PR #1033 to see the changes.Patch Changes
7261c43
,4014305
,609b7fa
,82f6fec
,2606a2a
,2606a2a
,5c27b76
,d38893f
,d7cf8dd
,2606a2a
,e08706a
]:@rrweb/packer@2.0.0-alpha.15
Major Changes
#1497
2606a2a
Thanks @Juice10! - Split plugins out of rrweb and move them into their own packages: @rrweb/packer, @rrweb/rrweb-plugin-canvas-webrtc-record, @rrweb/rrweb-plugin-canvas-webrtc-replay, @rrweb/rrweb-plugin-sequential-id-record, @rrweb/rrweb-plugin-sequential-id-replay, @rrweb/rrweb-plugin-console-record, @rrweb/rrweb-plugin-console-replay. Check out the README of each package for more information or check out https://github.com/rrweb-io/rrweb/pull/1033 to see the changes.#1497
2606a2a
Thanks @Juice10! - Distributed files have new filenames, paths and extensions. Important: If you reference distributed files or types directly, you might have to update your paths/filenames. E.g. you import fromrrweb/typings/...
orrrdom/es
. However you runimport rrweb from 'rrweb'
you won't notice a difference with this change. If you include rrweb files directly in a script tag, you might have to update that path to include a the.umd.cjs
files instead. All.js
files now use ES modules which can be used in modern browsers, node.js and bundlers that support ES modules. All npm packages now also ship.cjs
and.umd.cjs
files. The.umd.cjs
files are CommonJS modules that bundle all files together to make it easy to ship one file to browser environments (similar to the previous.js
files). The.cjs
files are CommonJS modules that can be used in older Node.js environments. Types should be better defined inpackage.json
and if you need specific types they might be exported from new packages (for examplePlayerMachineState
andSpeedMachineState
are now exported from@rrweb/replay
). Check thepackage.json
'smain
andexports
field for the available files.Patch Changes
2606a2a
]:@rrweb/rrweb-plugin-canvas-webrtc-record@2.0.0-alpha.15
Major Changes
#1497
2606a2a
Thanks @Juice10! - Split plugins out of rrweb and move them into their own packages: @rrweb/packer, @rrweb/rrweb-plugin-canvas-webrtc-record, @rrweb/rrweb-plugin-canvas-webrtc-replay, @rrweb/rrweb-plugin-sequential-id-record, @rrweb/rrweb-plugin-sequential-id-replay, @rrweb/rrweb-plugin-console-record, @rrweb/rrweb-plugin-console-replay. Check out the README of each package for more information or check out https://github.com/rrweb-io/rrweb/pull/1033 to see the changes.#1497
2606a2a
Thanks @Juice10! - Distributed files have new filenames, paths and extensions. Important: If you reference distributed files or types directly, you might have to update your paths/filenames. E.g. you import fromrrweb/typings/...
orrrdom/es
. However you runimport rrweb from 'rrweb'
you won't notice a difference with this change. If you include rrweb files directly in a script tag, you might have to update that path to include a the.umd.cjs
files instead. All.js
files now use ES modules which can be used in modern browsers, node.js and bundlers that support ES modules. All npm packages now also ship.cjs
and.umd.cjs
files. The.umd.cjs
files are CommonJS modules that bundle all files together to make it easy to ship one file to browser environments (similar to the previous.js
files). The.cjs
files are CommonJS modules that can be used in older Node.js environments. Types should be better defined inpackage.json
and if you need specific types they might be exported from new packages (for examplePlayerMachineState
andSpeedMachineState
are now exported from@rrweb/replay
). Check thepackage.json
'smain
andexports
field for the available files.Patch Changes
7261c43
,4014305
,609b7fa
,82f6fec
,2606a2a
,2606a2a
,5c27b76
,d38893f
,d7cf8dd
,2606a2a
,e08706a
]:@rrweb/rrweb-plugin-canvas-webrtc-replay@2.0.0-alpha.15
Major Changes
#1497
2606a2a
Thanks @Juice10! - Split plugins out of rrweb and move them into their own packages: @rrweb/packer, @rrweb/rrweb-plugin-canvas-webrtc-record, @rrweb/rrweb-plugin-canvas-webrtc-replay, @rrweb/rrweb-plugin-sequential-id-record, @rrweb/rrweb-plugin-sequential-id-replay, @rrweb/rrweb-plugin-console-record, @rrweb/rrweb-plugin-console-replay. Check out the README of each package for more information or check out https://github.com/rrweb-io/rrweb/pull/1033 to see the changes.#1497
2606a2a
Thanks @Juice10! - Distributed files have new filenames, paths and extensions. Important: If you reference distributed files or types directly, you might have to update your paths/filenames. E.g. you import fromrrweb/typings/...
orrrdom/es
. However you runimport rrweb from 'rrweb'
you won't notice a difference with this change. If you include rrweb files directly in a script tag, you might have to update that path to include a the.umd.cjs
files instead. All.js
files now use ES modules which can be used in modern browsers, node.js and bundlers that support ES modules. All npm packages now also ship.cjs
and.umd.cjs
files. The.umd.cjs
files are CommonJS modules that bundle all files together to make it easy to ship one file to browser environments (similar to the previous.js
files). The.cjs
files are CommonJS modules that can be used in older Node.js environments. Types should be better defined inpackage.json
and if you need specific types they might be exported from new packages (for examplePlayerMachineState
andSpeedMachineState
are now exported from@rrweb/replay
). Check thepackage.json
'smain
andexports
field for the available files.Patch Changes
#1033
7261c43
Thanks @Juice10! - ExportReplayPlugin
from rrweb directly. Previously we had to doimport type { ReplayPlugin } from 'rrweb/dist/types';
now we can doimport type { ReplayPlugin } from 'rrweb';
Updated dependencies [
7261c43
,4014305
,609b7fa
,82f6fec
,2606a2a
,2606a2a
,5c27b76
,d38893f
,d7cf8dd
,2606a2a
,e08706a
]:@rrweb/rrweb-plugin-console-record@2.0.0-alpha.15
Major Changes
#1497
2606a2a
Thanks @Juice10! - Split plugins out of rrweb and move them into their own packages: @rrweb/packer, @rrweb/rrweb-plugin-canvas-webrtc-record, @rrweb/rrweb-plugin-canvas-webrtc-replay, @rrweb/rrweb-plugin-sequential-id-record, @rrweb/rrweb-plugin-sequential-id-replay, @rrweb/rrweb-plugin-console-record, @rrweb/rrweb-plugin-console-replay. Check out the README of each package for more information or check out https://github.com/rrweb-io/rrweb/pull/1033 to see the changes.#1497
2606a2a
Thanks @Juice10! - Distributed files have new filenames, paths and extensions. Important: If you reference distributed files or types directly, you might have to update your paths/filenames. E.g. you import fromrrweb/typings/...
orrrdom/es
. However you runimport rrweb from 'rrweb'
you won't notice a difference with this change. If you include rrweb files directly in a script tag, you might have to update that path to include a the.umd.cjs
files instead. All.js
files now use ES modules which can be used in modern browsers, node.js and bundlers that support ES modules. All npm packages now also ship.cjs
and.umd.cjs
files. The.umd.cjs
files are CommonJS modules that bundle all files together to make it easy to ship one file to browser environments (similar to the previous.js
files). The.cjs
files are CommonJS modules that can be used in older Node.js environments. Types should be better defined inpackage.json
and if you need specific types they might be exported from new packages (for examplePlayerMachineState
andSpeedMachineState
are now exported from@rrweb/replay
). Check thepackage.json
'smain
andexports
field for the available files.Patch Changes
7261c43
,4014305
,609b7fa
,82f6fec
,2606a2a
,2606a2a
,5c27b76
,d38893f
,d7cf8dd
,2606a2a
,e08706a
]:@rrweb/rrweb-plugin-console-replay@2.0.0-alpha.15
Major Changes
#1497
2606a2a
Thanks @Juice10! - Split plugins out of rrweb and move them into their own packages: @rrweb/packer, @rrweb/rrweb-plugin-canvas-webrtc-record, @rrweb/rrweb-plugin-canvas-webrtc-replay, @rrweb/rrweb-plugin-sequential-id-record, @rrweb/rrweb-plugin-sequential-id-replay, @rrweb/rrweb-plugin-console-record, @rrweb/rrweb-plugin-console-replay. Check out the README of each package for more information or check out https://github.com/rrweb-io/rrweb/pull/1033 to see the changes.#1497
2606a2a
Thanks @Juice10! - Distributed files have new filenames, paths and extensions. Important: If you reference distributed files or types directly, you might have to update your paths/filenames. E.g. you import fromrrweb/typings/...
orrrdom/es
. However you runimport rrweb from 'rrweb'
you won't notice a difference with this change. If you include rrweb files directly in a script tag, you might have to update that path to include a the.umd.cjs
files instead. All.js
files now use ES modules which can be used in modern browsers, node.js and bundlers that support ES modules. All npm packages now also ship.cjs
and.umd.cjs
files. The.umd.cjs
files are CommonJS modules that bundle all files together to make it easy to ship one file to browser environments (similar to the previous.js
files). The.cjs
files are CommonJS modules that can be used in older Node.js environments. Types should be better defined inpackage.json
and if you need specific types they might be exported from new packages (for examplePlayerMachineState
andSpeedMachineState
are now exported from@rrweb/replay
). Check thepackage.json
'smain
andexports
field for the available files.Patch Changes
#1033
7261c43
Thanks @Juice10! - ExportReplayPlugin
from rrweb directly. Previously we had to doimport type { ReplayPlugin } from 'rrweb/dist/types';
now we can doimport type { ReplayPlugin } from 'rrweb';
Updated dependencies [
7261c43
,4014305
,609b7fa
,82f6fec
,2606a2a
,2606a2a
,5c27b76
,d38893f
,d7cf8dd
,2606a2a
,e08706a
]:@rrweb/rrweb-plugin-sequential-id-record@2.0.0-alpha.15
Major Changes
#1497
2606a2a
Thanks @Juice10! - Split plugins out of rrweb and move them into their own packages: @rrweb/packer, @rrweb/rrweb-plugin-canvas-webrtc-record, @rrweb/rrweb-plugin-canvas-webrtc-replay, @rrweb/rrweb-plugin-sequential-id-record, @rrweb/rrweb-plugin-sequential-id-replay, @rrweb/rrweb-plugin-console-record, @rrweb/rrweb-plugin-console-replay. Check out the README of each package for more information or check out https://github.com/rrweb-io/rrweb/pull/1033 to see the changes.#1497
2606a2a
Thanks @Juice10! - Distributed files have new filenames, paths and extensions. Important: If you reference distributed files or types directly, you might have to update your paths/filenames. E.g. you import fromrrweb/typings/...
orrrdom/es
. However you runimport rrweb from 'rrweb'
you won't notice a difference with this change. If you include rrweb files directly in a script tag, you might have to update that path to include a the.umd.cjs
files instead. All.js
files now use ES modules which can be used in modern browsers, node.js and bundlers that support ES modules. All npm packages now also ship.cjs
and.umd.cjs
files. The.umd.cjs
files are CommonJS modules that bundle all files together to make it easy to ship one file to browser environments (similar to the previous.js
files). The.cjs
files are CommonJS modules that can be used in older Node.js environments. Types should be better defined inpackage.json
and if you need specific types they might be exported from new packages (for examplePlayerMachineState
andSpeedMachineState
are now exported from@rrweb/replay
). Check thepackage.json
'smain
andexports
field for the available files.Patch Changes
7261c43
,4014305
,609b7fa
,82f6fec
,2606a2a
,2606a2a
,5c27b76
,d38893f
,d7cf8dd
,2606a2a
,e08706a
]:@rrweb/rrweb-plugin-sequential-id-replay@2.0.0-alpha.15
Major Changes
#1497
2606a2a
Thanks @Juice10! - Split plugins out of rrweb and move them into their own packages: @rrweb/packer, @rrweb/rrweb-plugin-canvas-webrtc-record, @rrweb/rrweb-plugin-canvas-webrtc-replay, @rrweb/rrweb-plugin-sequential-id-record, @rrweb/rrweb-plugin-sequential-id-replay, @rrweb/rrweb-plugin-console-record, @rrweb/rrweb-plugin-console-replay. Check out the README of each package for more information or check out https://github.com/rrweb-io/rrweb/pull/1033 to see the changes.#1497
2606a2a
Thanks @Juice10! - Distributed files have new filenames, paths and extensions. Important: If you reference distributed files or types directly, you might have to update your paths/filenames. E.g. you import fromrrweb/typings/...
orrrdom/es
. However you runimport rrweb from 'rrweb'
you won't notice a difference with this change. If you include rrweb files directly in a script tag, you might have to update that path to include a the.umd.cjs
files instead. All.js
files now use ES modules which can be used in modern browsers, node.js and bundlers that support ES modules. All npm packages now also ship.cjs
and.umd.cjs
files. The.umd.cjs
files are CommonJS modules that bundle all files together to make it easy to ship one file to browser environments (similar to the previous.js
files). The.cjs
files are CommonJS modules that can be used in older Node.js environments. Types should be better defined inpackage.json
and if you need specific types they might be exported from new packages (for examplePlayerMachineState
andSpeedMachineState
are now exported from@rrweb/replay
). Check thepackage.json
'smain
andexports
field for the available files.Patch Changes
#1033
7261c43
Thanks @Juice10! - ExportReplayPlugin
from rrweb directly. Previously we had to doimport type { ReplayPlugin } from 'rrweb/dist/types';
now we can doimport type { ReplayPlugin } from 'rrweb';
Updated dependencies [
7261c43
,4014305
,609b7fa
,82f6fec
,2606a2a
,2606a2a
,5c27b76
,d38893f
,d7cf8dd
,2606a2a
,e08706a
]:@rrweb/record@2.0.0-alpha.15
Major Changes
#1497
2606a2a
Thanks @Juice10! - Distributed files have new filenames, paths and extensions. Important: If you reference distributed files or types directly, you might have to update your paths/filenames. E.g. you import fromrrweb/typings/...
orrrdom/es
. However you runimport rrweb from 'rrweb'
you won't notice a difference with this change. If you include rrweb files directly in a script tag, you might have to update that path to include a the.umd.cjs
files instead. All.js
files now use ES modules which can be used in modern browsers, node.js and bundlers that support ES modules. All npm packages now also ship.cjs
and.umd.cjs
files. The.umd.cjs
files are CommonJS modules that bundle all files together to make it easy to ship one file to browser environments (similar to the previous.js
files). The.cjs
files are CommonJS modules that can be used in older Node.js environments. Types should be better defined inpackage.json
and if you need specific types they might be exported from new packages (for examplePlayerMachineState
andSpeedMachineState
are now exported from@rrweb/replay
). Check thepackage.json
'smain
andexports
field for the available files.#1497
2606a2a
Thanks @Juice10! - Remove the rrweb-all.js, rrweb-record.js, and rrweb-replay.js files fromrrweb
package. Now you can use@rrweb/all
,@rrweb/record
, and@rrweb/replay
packages instead. Check out the README of each package for more information or check out PR #1033 to see the changes.Patch Changes
7261c43
,4014305
,609b7fa
,82f6fec
,2606a2a
,2606a2a
,5c27b76
,d38893f
,d7cf8dd
,2606a2a
,e08706a
]:@rrweb/replay@2.0.0-alpha.15
Major Changes
#1497
2606a2a
Thanks @Juice10! - Distributed files have new filenames, paths and extensions. Important: If you reference distributed files or types directly, you might have to update your paths/filenames. E.g. you import fromrrweb/typings/...
orrrdom/es
. However you runimport rrweb from 'rrweb'
you won't notice a difference with this change. If you include rrweb files directly in a script tag, you might have to update that path to include a the.umd.cjs
files instead. All.js
files now use ES modules which can be used in modern browsers, node.js and bundlers that support ES modules. All npm packages now also ship.cjs
and.umd.cjs
files. The.umd.cjs
files are CommonJS modules that bundle all files together to make it easy to ship one file to browser environments (similar to the previous.js
files). The.cjs
files are CommonJS modules that can be used in older Node.js environments. Types should be better defined inpackage.json
and if you need specific types they might be exported from new packages (for examplePlayerMachineState
andSpeedMachineState
are now exported from@rrweb/replay
). Check thepackage.json
'smain
andexports
field for the available files.#1497
2606a2a
Thanks @Juice10! - Remove the rrweb-all.js, rrweb-record.js, and rrweb-replay.js files fromrrweb
package. Now you can use@rrweb/all
,@rrweb/record
, and@rrweb/replay
packages instead. Check out the README of each package for more information or check out PR #1033 to see the changes.Patch Changes
7261c43
,4014305
,609b7fa
,82f6fec
,2606a2a
,2606a2a
,5c27b76
,d38893f
,d7cf8dd
,2606a2a
,e08706a
]:rrdom@2.0.0-alpha.15
Major Changes
2606a2a
Thanks @Juice10! - Distributed files have new filenames, paths and extensions. Important: If you reference distributed files or types directly, you might have to update your paths/filenames. E.g. you import fromrrweb/typings/...
orrrdom/es
. However you runimport rrweb from 'rrweb'
you won't notice a difference with this change. If you include rrweb files directly in a script tag, you might have to update that path to include a the.umd.cjs
files instead. All.js
files now use ES modules which can be used in modern browsers, node.js and bundlers that support ES modules. All npm packages now also ship.cjs
and.umd.cjs
files. The.umd.cjs
files are CommonJS modules that bundle all files together to make it easy to ship one file to browser environments (similar to the previous.js
files). The.cjs
files are CommonJS modules that can be used in older Node.js environments. Types should be better defined inpackage.json
and if you need specific types they might be exported from new packages (for examplePlayerMachineState
andSpeedMachineState
are now exported from@rrweb/replay
). Check thepackage.json
'smain
andexports
field for the available files.Patch Changes
4014305
,82f6fec
,2606a2a
,f3cf092
,e08706a
]:rrdom-nodejs@2.0.0-alpha.15
Major Changes
2606a2a
Thanks @Juice10! - Distributed files have new filenames, paths and extensions. Important: If you reference distributed files or types directly, you might have to update your paths/filenames. E.g. you import fromrrweb/typings/...
orrrdom/es
. However you runimport rrweb from 'rrweb'
you won't notice a difference with this change. If you include rrweb files directly in a script tag, you might have to update that path to include a the.umd.cjs
files instead. All.js
files now use ES modules which can be used in modern browsers, node.js and bundlers that support ES modules. All npm packages now also ship.cjs
and.umd.cjs
files. The.umd.cjs
files are CommonJS modules that bundle all files together to make it easy to ship one file to browser environments (similar to the previous.js
files). The.cjs
files are CommonJS modules that can be used in older Node.js environments. Types should be better defined inpackage.json
and if you need specific types they might be exported from new packages (for examplePlayerMachineState
andSpeedMachineState
are now exported from@rrweb/replay
). Check thepackage.json
'smain
andexports
field for the available files.Patch Changes
4014305
,82f6fec
,2606a2a
,f3cf092
,e08706a
]:rrweb@2.0.0-alpha.15
Major Changes
#1497
2606a2a
Thanks @Juice10! - Split plugins out of rrweb and move them into their own packages: @rrweb/packer, @rrweb/rrweb-plugin-canvas-webrtc-record, @rrweb/rrweb-plugin-canvas-webrtc-replay, @rrweb/rrweb-plugin-sequential-id-record, @rrweb/rrweb-plugin-sequential-id-replay, @rrweb/rrweb-plugin-console-record, @rrweb/rrweb-plugin-console-replay. Check out the README of each package for more information or check out https://github.com/rrweb-io/rrweb/pull/1033 to see the changes.#1497
2606a2a
Thanks @Juice10! - Distributed files have new filenames, paths and extensions. Important: If you reference distributed files or types directly, you might have to update your paths/filenames. E.g. you import fromrrweb/typings/...
orrrdom/es
. However you runimport rrweb from 'rrweb'
you won't notice a difference with this change. If you include rrweb files directly in a script tag, you might have to update that path to include a the.umd.cjs
files instead. All.js
files now use ES modules which can be used in modern browsers, node.js and bundlers that support ES modules. All npm packages now also ship.cjs
and.umd.cjs
files. The.umd.cjs
files are CommonJS modules that bundle all files together to make it easy to ship one file to browser environments (similar to the previous.js
files). The.cjs
files are CommonJS modules that can be used in older Node.js environments. Types should be better defined inpackage.json
and if you need specific types they might be exported from new packages (for examplePlayerMachineState
andSpeedMachineState
are now exported from@rrweb/replay
). Check thepackage.json
'smain
andexports
field for the available files.#1497
2606a2a
Thanks @Juice10! - Remove the rrweb-all.js, rrweb-record.js, and rrweb-replay.js files fromrrweb
package. Now you can use@rrweb/all
,@rrweb/record
, and@rrweb/replay
packages instead. Check out the README of each package for more information or check out PR #1033 to see the changes.Patch Changes
#1033
7261c43
Thanks @Juice10! - ExportReplayPlugin
from rrweb directly. Previously we had to doimport type { ReplayPlugin } from 'rrweb/dist/types';
now we can doimport type { ReplayPlugin } from 'rrweb';
#1468
4014305
Thanks @eoghanmurray! - inlineImages: during snapshot avoid adding an event listener for inlining of same-origin images (async listener mutates the snapshot which can be problematic)#1489
609b7fa
Thanks @JonasBa! - Optimize performance of isParentRemoved by converting it to an iterative procedure#1493
82f6fec
Thanks @eoghanmurray! - Replay: Replace negative lookbehind in regexes from css parser as it causes issues with Safari 16#1353
5c27b76
Thanks @YunFeng0817! - Fix: some nested cross-origin iframes can't be recorded#1328
d38893f
Thanks @eoghanmurray! - Refactor to preclude the need for a continuous raf loop running in the background which is related to shadowDom#1295
d7cf8dd
Thanks @colingm! - Return early for child same origin frames#760
e08706a
Thanks @eoghanmurray! - Add slimDOM option to block animation onUpdated dependencies [
4014305
,82f6fec
,2606a2a
,f3cf092
,e08706a
]:rrweb-player@2.0.0-alpha.15
Major Changes
2606a2a
Thanks @Juice10! - Distributed files have new filenames, paths and extensions. Important: If you reference distributed files or types directly, you might have to update your paths/filenames. E.g. you import fromrrweb/typings/...
orrrdom/es
. However you runimport rrweb from 'rrweb'
you won't notice a difference with this change. If you include rrweb files directly in a script tag, you might have to update that path to include a the.umd.cjs
files instead. All.js
files now use ES modules which can be used in modern browsers, node.js and bundlers that support ES modules. All npm packages now also ship.cjs
and.umd.cjs
files. The.umd.cjs
files are CommonJS modules that bundle all files together to make it easy to ship one file to browser environments (similar to the previous.js
files). The.cjs
files are CommonJS modules that can be used in older Node.js environments. Types should be better defined inpackage.json
and if you need specific types they might be exported from new packages (for examplePlayerMachineState
andSpeedMachineState
are now exported from@rrweb/replay
). Check thepackage.json
'smain
andexports
field for the available files.Patch Changes
2606a2a
,2606a2a
,2606a2a
]:rrweb-snapshot@2.0.0-alpha.15
Major Changes
2606a2a
Thanks @Juice10! - Distributed files have new filenames, paths and extensions. Important: If you reference distributed files or types directly, you might have to update your paths/filenames. E.g. you import fromrrweb/typings/...
orrrdom/es
. However you runimport rrweb from 'rrweb'
you won't notice a difference with this change. If you include rrweb files directly in a script tag, you might have to update that path to include a the.umd.cjs
files instead. All.js
files now use ES modules which can be used in modern browsers, node.js and bundlers that support ES modules. All npm packages now also ship.cjs
and.umd.cjs
files. The.umd.cjs
files are CommonJS modules that bundle all files together to make it easy to ship one file to browser environments (similar to the previous.js
files). The.cjs
files are CommonJS modules that can be used in older Node.js environments. Types should be better defined inpackage.json
and if you need specific types they might be exported from new packages (for examplePlayerMachineState
andSpeedMachineState
are now exported from@rrweb/replay
). Check thepackage.json
'smain
andexports
field for the available files.Patch Changes
#1468
4014305
Thanks @eoghanmurray! - inlineImages: during snapshot avoid adding an event listener for inlining of same-origin images (async listener mutates the snapshot which can be problematic)#1493
82f6fec
Thanks @eoghanmurray! - Replay: Replace negative lookbehind in regexes from css parser as it causes issues with Safari 16#1482
f3cf092
Thanks @AlfieJones! - (whenrecordCanvas: true
): ensure we use doc.createElement instead of document.createElement to allow use in non-browser e.g. jsdom environments#760
e08706a
Thanks @eoghanmurray! - Add slimDOM option to block animation on@rrweb/types@2.0.0-alpha.15
Major Changes
2606a2a
Thanks @Juice10! - Distributed files have new filenames, paths and extensions. Important: If you reference distributed files or types directly, you might have to update your paths/filenames. E.g. you import fromrrweb/typings/...
orrrdom/es
. However you runimport rrweb from 'rrweb'
you won't notice a difference with this change. If you include rrweb files directly in a script tag, you might have to update that path to include a the.umd.cjs
files instead. All.js
files now use ES modules which can be used in modern browsers, node.js and bundlers that support ES modules. All npm packages now also ship.cjs
and.umd.cjs
files. The.umd.cjs
files are CommonJS modules that bundle all files together to make it easy to ship one file to browser environments (similar to the previous.js
files). The.cjs
files are CommonJS modules that can be used in older Node.js environments. Types should be better defined inpackage.json
and if you need specific types they might be exported from new packages (for examplePlayerMachineState
andSpeedMachineState
are now exported from@rrweb/replay
). Check thepackage.json
'smain
andexports
field for the available files.Patch Changes
4014305
,82f6fec
,2606a2a
,f3cf092
,e08706a
]:rrvideo@2.0.0-alpha.15
Patch Changes
2606a2a
]:@rrweb/web-extension@2.0.0-alpha.15
Patch Changes
7261c43
,4014305
,609b7fa
,82f6fec
,2606a2a
,2606a2a
,5c27b76
,d38893f
,d7cf8dd
,2606a2a
,e08706a
]: