Update @vitejs/plugin-react: 1.0.9 → 1.3.2 (minor) #92

depfu · 2022-07-06T02:35:20Z

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ @vitejs/plugin-react (1.0.9 → 1.3.2) · Repo · Changelog

Release Notes

1.3.2 (from changelog)

fix(plugin-react): React is not defined when component name is lowercase (#6838) (bf40e5c), closes #6838

chore(deps): update all non-major dependencies (#7780) (eba9d05), closes #7780

chore(deps): update all non-major dependencies (#7949) (b877d30), closes #7949

1.3.1 (from changelog)

fix(deps): update all non-major dependencies (#7668) (485263c), closes #7668

chore: fix term cases (#7553) (c296130), closes #7553

chore(deps): update all non-major dependencies (#7603) (fc51a15), closes #7603

1.3.0 (from changelog)

feat(plugin-react): adding jsxPure option (#7088) (d451435), closes #7088

fix(deps): update all non-major dependencies (#6782) (e38be3e), closes #6782

fix(deps): update all non-major dependencies (#7392) (b63fc3b), closes #7392

chore: fix publish, build vite before plugin-react and plugin-vue (#6988) (620a9bd), closes #6988

chore(deps): update all non-major dependencies (#6905) (839665c), closes #6905

workflow: separate version bumping and publishing on release (#6879) (fe8ef39), closes #6879

1.2.0 (from changelog)

Features

plugin-react: ensure overrides array exists before api.reactBabel hooks are called (#6750) (104bdb5)

1.1.4 (from changelog)

Bug Fixes

plugin-react: check for import React statement in .js files (#6320) (bd9e97b), closes #6148 #6148

plugin-react: restore-jsx bug when component name is lowercase (#6110) (ce65c56)

Features

plugin-react: check for api.reactBabel on other plugins (#5454) (2ab41b3)

1.1.3 (from changelog)

Bug Fixes

plugin-react: only detect preamble in hmr context (#6096) (8735294)

1.1.2 (from changelog)

Bug Fixes

ignore babel config when running restore-jsx (#6047) (9c2843c)

Does any of this look wrong? Please let us know.

Depfu 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

@depfu rebase
Rebases against your default branch and redoes this update

@depfu recreate
Recreates this PR, overwriting any edits that you've made to it

@depfu merge
Merges this PR once your tests are passing and conflicts are resolved

@depfu close
Closes this PR and deletes the branch

@depfu reopen
Restores the branch and reopens this PR (if it's closed)

@depfu pause
Ignores all future updates for this dependency and closes this PR

@depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR

@depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)