Update @types/react-dom 18.2.15 → 19.2.3 (major) #519
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.
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ @types/react-dom (18.2.15 → 19.2.3) · Repo
Sorry, we couldn't find anything useful about this release.
✳️ @types/react (19.1.9 → 19.2.6) · Repo
Sorry, we couldn't find anything useful about this release.
Commits
See the full diff on Github. The new version differs by 23 commits:
v3.2.3Remove Npm lock files from tests and fixturesFix security flawsResolve syntaxes with comma separator and prevent reoccurring data types by skipping functionsRename Release It configRelease 3.2.2Add Release It scriptIgnore comma in CSS syntax for nowv3.2.1Revert type module and rename .js -> .mjs insteadPatch missing shorthands for border-[inline|block]-* properties (#188)v3.2.0Fix update scriptUpdate type tests and drop compatibility with v2Update summariesBump MDN dataAdopt to @mdn/browser-compat-dataBump Npm packagesv3.1.3Bump MDNUpdate package locksMerge pull request #178 from frenic/fallback-readonlyAdd readonly for fallback valuesDepfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands