[Juice10]

Snyk has created this PR to fix 1 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

• packages/core/package.json

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

⚠️ Warning

Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Memory Allocation with Excessive Size Value SNYK-JS-FFLATE-22392372	828

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[Juice10]

This upgrade moves rrweb from a 2.0.0 alpha release to the final, stable 2.0.0 version. While this is a positive stabilization, several significant changes were made during the alpha lifecycle that are now finalized.

Key Changes in 2.0.0:

• New Package Structure: The primary rrweb package is now deprecated and split into scoped packages like @rrweb/record and @rrweb/replay. New projects should use these directly. While the rrweb package is kept for backward compatibility, its usage is discouraged.
• Module and Distribution Files: Distributed files have new filenames, paths, and extensions (e.g., .umd.cjs). If you were directly referencing files via <script> tags or had deep imports, these paths will need to be updated. Standard import rrweb from 'rrweb' should not be affected.
• Plugins: Plugins have been split into their own packages (e.g., @rrweb/rrweb-plugin-console-record).
• Security Fix: The final release includes a security fix in rrweb-snapshot that was introduced after the alpha versions.

Recommendation:

This is a move from an unstable pre-release to a stable version. Given the package structure changes and deprecation of the main rrweb package, the risk is medium. Developers should verify their implementation, especially if using plugins or direct file includes. It is highly recommended to migrate to the new scoped packages (@rrweb/record, @rrweb/replay) for future compatibility.

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 183026e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[chatgpt-codex-connector]

Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
🔒 Security Review	✅ Completed 2026-11-11T04:06:05.761047Z	183026e	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.