[Snyk] Upgrade lexical from 0.20.2 to 0.23.1 #1114
Closed
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.
Snyk has created this PR to upgrade lexical from 0.20.2 to 0.23.1.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 33 versions ahead of your current version.
The recommended version was released 21 days ago.
Release notes
Package name: lexical
Breaking Changes
The only breaking change in this release is minor (#7023) and should not affect any correct code. However, if you are counting the number of times your update listener is called during
editor.setRootElement(null)
then you will have to change that expectation.Highlights
Highlights since v0.23.0
Core Editor:
editor.setRootElement(null)
#7023Mark:
React:
What's Changed
New Contributors
Full Changelog: v0.23.0...v0.23.1
v0.23.1-nightly.20250109.0
v0.23.1-nightly.20250108.0
v0.23.1-nightly.20250107.0
v0.23.1-nightly.20250106.0
Breaking Changes
🆕 Feature: Add updateFromJSON and move more textFormat/textStyle to ElementNode
This change adds optional textFormat and textStyle properties to SerializedElementNode. If you have existing classes with those properties it could create a namespace clash that you will have to resolve one way or another.
TextNode and ElementNode subclasses should be updated to call the updateFromJSON(serializedNode) method from their static importJSON methods. If they don't, they won't support this new functionality, and will have to continue copy and pasting the super implementation of importJSON for correct behavior if the base class ever changes in the future.
You should consider dropping usage of the version field.
Highlights
Highlights since v0.22.0
Core Editor:
Playground:
Yjs:
What's Changed
New Contributors
Full Changelog: v0.22.0...v0.23.0
v0.22.1-nightly.20250103.0
v0.22.1-nightly.20250102.0
v0.22.1-nightly.20250101.0
v0.22.1-nightly.20241231.0
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information: