-
Notifications
You must be signed in to change notification settings - Fork 1
fix(deps): update external major (major) #2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate-major-external-major
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch and validate page speed.
Commits
|
a46c829 to
bcaea9b
Compare
bcaea9b to
5c2c072
Compare
5c2c072 to
c9ecc51
Compare
c9ecc51 to
d4bfda2
Compare
d4bfda2 to
ce5aae9
Compare
3997f49 to
85e715f
Compare
85e715f to
b217049
Compare
b217049 to
413bd00
Compare
413bd00 to
6cc2915
Compare
6cc2915 to
bc3c7ce
Compare
0ad1adc to
11ebf1f
Compare
11ebf1f to
3ad4936
Compare
3ad4936 to
939a6ee
Compare
939a6ee to
b85a18a
Compare
ae5aedc to
f4308df
Compare
f4308df to
f8d9811
Compare
f8d9811 to
03b88ed
Compare
03b88ed to
c0bdafb
Compare
c0bdafb to
ebd39ad
Compare
ebd39ad to
76566c0
Compare
76566c0 to
01a452e
Compare
01a452e to
49c249c
Compare
49c249c to
4576402
Compare
4576402 to
105b668
Compare
105b668 to
df95024
Compare
df95024 to
ced200a
Compare
ced200a to
2fe0914
Compare
2fe0914 to
0bddfe2
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR contains the following updates:
^18.0.24->^19.0.019.2.7(+1)^18.0.8->^19.0.0^2.2.0->^5.0.0v3->v5v6v3->v64.3.6->6.2.1^20.0.3->^27.0.014->24^18.2.0->^19.0.0^18.2.0->^19.0.0^3.0.2->^6.0.06.1.2(+1)14.0.1->21.0.014.13.0->16.25.016.26.1(+1)25.0.0->39.0.1^3.2.3->^7.0.07.2.4(+1)^5.0.1->^6.0.02.5.0->4.48.04.51.0(+3)Release Notes
vitejs/vite-plugin-react (@vitejs/plugin-react)
v5.1.1Compare Source
Update code to support newer
rolldown-vite(#976)rolldown-vitewill removeoptimizeDeps.rollupOptionsin favor ofoptimizeDeps.rolldownOptionssoon. This plugin now usesoptimizeDeps.rolldownOptionsto support newerrolldown-vite. Please updaterolldown-viteto the latest version if you are using an older version.v5.1.0Compare Source
Add
@vitejs/plugin-react/preamblevirtual module for SSR HMR (#890)SSR applications can now initialize HMR runtime by importing
@vitejs/plugin-react/preambleat the top of their client entry instead of manually callingtransformIndexHtml. This simplifies SSR setup for applications that don't use thetransformIndexHtmlAPI.Fix raw Rolldown support for Rolldown 1.0.0-beta.44+ (#930)
Rolldown 1.0.0-beta.44+ removed the top-level
jsxoption in favor oftransform.jsx. This plugin now uses thetransform.jsxoption to support Rolldown 1.0.0-beta.44+.v5.0.4Compare Source
Perf: use native refresh wrapper plugin in rolldown-vite (#881)
v5.0.3Compare Source
HMR did not work for components imported with queries with rolldown-vite (#872)
Perf: simplify refresh wrapper generation (#835)
v5.0.2Compare Source
Skip transform hook completely in rolldown-vite in dev if possible (#783)
v5.0.1Compare Source
Set
optimizeDeps.rollupOptions.transform.jsxinstead ofoptimizeDeps.rollupOptions.jsxfor rolldown-vite (#735)optimizeDeps.rollupOptions.jsxis going to be deprecated in favor ofoptimizeDeps.rollupOptions.transform.jsx.Perf: skip
babel-plugin-react-compilerif code has no"use memo"when{ compilationMode: "annotation" }(#734)Respect tsconfig
jsxImportSource(#726)Fix
reactRefreshHostoption on rolldown-vite (#716)Fix
RefreshRuntimebeing injected twice for class components on rolldown-vite (#708)Skip
babel-plugin-react-compileron non client environment (689)v5.0.0Compare Source
v4.7.0Compare Source
Add HMR support for compound components (#518)
HMR now works for compound components like this:
Return
Plugin[]instead ofPluginOption[](#537)The return type has changed from
react(): PluginOption[]to more specialized typereact(): Plugin[]. This allows for type-safe manipulation of plugins, for example:v4.6.0Compare Source
Add raw Rolldown support
This plugin only worked with Vite. But now it can also be used with raw Rolldown. The main purpose for using this plugin with Rolldown is to use react compiler.
v4.5.2Compare Source
Suggest
@vitejs/plugin-react-oxcif rolldown-vite is detected #491Emit a log which recommends
@vitejs/plugin-react-oxcwhenrolldown-viteis detected to improve performance and use Oxc under the hood. The warning can be disabled by settingdisableOxcRecommendation: truein the plugin options.Use
optimizeDeps.rollupOptionsinstead ofoptimizeDeps.esbuildOptionsfor rolldown-vite #489This suppresses the warning about
optimizeDeps.esbuildOptionsbeing deprecated in rolldown-vite.Add Vite 7-beta to peerDependencies range #497
React plugins are compatible with Vite 7, this removes the warning when testing the beta.
v4.5.1Compare Source
Add explicit semicolon in preambleCode #485
This fixes an edge case when using HTML minifiers that strips line breaks aggressively.
v4.5.0Compare Source
Add
filterfor rolldown-vite #470Added
filterso that it is more performant when running this plugin with rolldown-powered version of Vite.Skip HMR for JSX files with hooks #480
This removes the HMR warning for hooks with JSX.
v4.4.1Compare Source
Fix type issue when using
moduleResolution: "node"in tsconfig #462v4.4.0Compare Source
Make compatible with rolldown-vite
This plugin is now compatible with rolldown-powered version of Vite.
Note that currently the
__sourceproperty value position might be incorrect. This will be fixed in the near future.v4.3.4Compare Source
Add Vite 6 to peerDependencies range
Vite 6 is highly backward compatible, not much to add!
Force Babel to output spec compliant import attributes #386
The default was an old spec (
with type: "json"). We now enforce spec compliant (with { type: "json" })v4.3.3Compare Source
React Compiler runtimeModule option removed
React Compiler was updated to accept a
targetoption andruntimeModulewas removed. vite-plugin-react will still detectruntimeModulefor backwards compatibility.When using a custom
runtimeModuleortarget !== '19', the plugin will not try to pre-optimizereact/compiler-runtimedependency.The react-compiler-runtime is now available on npm can be used instead of the local shim for people using the compiler with React < 19.
Here is the configuration to use the compiler with React 18 and correct source maps in development:
v4.3.2Compare Source
Ignore directive sourcemap error #369
v4.3.1Compare Source
Fix support for React Compiler with React 18
The previous version made this assumption that the compiler was only usable with React 19, but it's possible to use it with React 18 and a custom
runtimeModule: https://gist.github.com/poteto/37c076bf112a07ba39d0e5f0645fec43When using a custom
runtimeModule, the plugin will not try to pre-optimizereact/compiler-runtimedependency.Reminder: Vite expect code outside of
node_modulesto be ESM, so you will need to update the gist withimport React from 'react'.v4.3.0Compare Source
Fix support for React compiler
Don't set
retainLines: truewhen the React compiler is used. This creates whitespace issues and the compiler is modifying the JSX too much to get correct line numbers after that. If you want to use the React compiler and get back correct line numbers for tools like vite-plugin-react-click-to-component to work, you should update your config to something like:Support HMR for class components
This is a long overdue and should fix some issues people had with HMR when migrating from CRA.
v4.2.1Compare Source
Remove generic parameter on
Pluginto avoid type error with Rollup 4/Vite 5 andskipLibCheck: false.I expect very few people to currently use this feature, but if you are extending the React plugin via
apiobject, you can get back the typing of the hook by importingViteReactPluginApi:v4.2.0Compare Source
Update peer dependency range to target Vite 5
There were no breaking change that impacted this plugin, so any combination of React plugins and Vite core version will work.
Align jsx runtime for optimized dependencies
This will only affect people using internal libraries that contains untranspiled JSX. This change aligns the optimizer with the source code and avoid issues when the published source don't have
Reactin the scope.Reminder: While being partially supported in Vite, publishing TS & JSX outside of internal libraries is highly discouraged.
v4.1.1Compare Source
v4.1.0Compare Source
@types/babel__coresto dependencies (fix #211)@babel/core#212index.d.ctsfile so you don't get types errors when settingmoduleResolutiontonode16ornodenextin your tsconfig (we recommend usingbundlerwhich is more close to how Vite works)v4.0.4Compare Source
v4.0.3Compare Source
v4.0.2Compare Source
v4.0.1Compare Source
v4.0.0Compare Source
This major version include a revamp of options:
include/excludenow allow to completely override the files processed by the plugin (#122). This is more in line with other Rollup/Vite plugins and simplify the setup of enabling Fast Refresh for.mdxfiles. This can be done like this:These changes also allow to apply Babel plugins on files outside Vite root (expect in node_modules), which improve support for monorepo (fix #16).
With these changes, only the file extensions is used for filtering processed files and the query param fallback is removed.
fastRefreshis removed (#122). This should be correctly activated by plugin without configuration.jsxPureis removed. This is a niche use case that was just passing down the boolean to esbuild.jsxSideEffects. (#129)The support for React auto import whe using classic runtime is removed. This was prone to errors and added complexity for no good reason given the very wide support of automatic runtime nowadays. This migration path should be as simple as removing the runtime option from the config.
This release goes in hand with the upcoming Vite 4.3 release focusing on performances:
Other notable changes:
v3.1.0Compare Source
v3.0.1Compare Source
v3.0.0Compare Source
actions/checkout (actions/checkout)
v5Compare Source
v4Compare Source
url-helper.tsnow leverages well-known environment variables by @jww3 in #1941isGhesby @jww3 in #1946actions/setup-node (actions/setup-node)
v6Compare Source
v5Compare Source
v4Compare Source
chaijs/chai (chai)
v6.2.1Compare Source
What's Changed
New Contributors
Full Changelog: chaijs/chai@v6.2.0...v6.2.1
v6.2.0Compare Source
What's Changed
Full Changelog: chaijs/chai@v6.1.0...v6.2.0
v6.1.0Compare Source
What's Changed
Adds an event emitter for hooking into method/property creation in #1693
Full Changelog: chaijs/chai@v6.0.2...v6.1.0
v6.0.1Compare Source
What's Changed
Full Changelog: chaijs/chai@v6.0.0...v6.0.1
v6.0.0Compare Source
BREAKING CHANGES
Chai is now bundled into a single file. The
lib/*.jsfiles are no longer present, and so any code that imports those files directly will need to change. The only file that can be imported now is./index.js.What's Changed
Full Changelog: chaijs/chai@v5.3.2...v6.0.0
v5.3.3Compare Source
What's Changed
Full Changelog: chaijs/chai@v5.3.2...v5.3.3
v5.3.2Compare Source
Reverts the removal of the bundled version of chai in 5.3.1
What's Changed
Full Changelog: chaijs/chai@v5.3.1...v5.3.2
v5.3.1Compare Source
What's Changed
Full Changelog: chaijs/chai@v5.3.0...v5.3.1
v5.3.0Compare Source
What's Changed
mainto point at chai directly by @43081j in #1696Full Changelog: chaijs/chai@v5.2.2...v5.3.0
v5.2.2Compare Source
What's Changed
filesfor publishing by @43081j in #1695Full Changelog: chaijs/chai@v5.2.1...v5.2.2
v5.2.1Compare Source
What's Changed
Mostly internal changes but @SuperchupuDev realised the package.json
enginesfield was out of date, so it has been updated to reflect that v5.0.0 onwards only supports Node >=18.no-varrule and fix violations by @koddsson in #1675New Contributors
Full Changelog: chaijs/chai@v5.2.0...v5.2.1
v5.2.0Compare Source
What's Changed
chai-subsetand added assert-based negation to containSubset by @BreadInvasion in #1664New Contributors
Full Changelog: chaijs/chai@v5.1.2...v5.2.0
v5.1.2Compare Source
What's Changed
Full Changelog: chaijs/chai@v5.1.1...v5.1.2
v5.1.1Compare Source
What's Changed
toThrowby @43081j in #1609New Contributors
Full Changelog: chaijs/chai@v5.1.0...v5.1.1
v5.1.0Compare Source
What's Changed
iterableassertion by @koddsson in #1592New Contributors
Full Changelog: chaijs/chai@v5.0.3...v5.1.0
v5.0.3Compare Source
Fix bad v5.0.2 publish.
Full Changelog: chaijs/chai@v5.0.2...v5.0.3
v5.0.2Compare Source
What's Changed
bump-cliby @koddsson in #1559??for node compat (5.x) by @43081j in #1576loupeto latest version by @koddsson in #1579Full Changelog: chaijs/chai@v5.0.1...v5.0.2
v5.0.0Compare Source
BREAKING CHANGES
import {...} from 'chai'orimport('chai').require('chai')will cause failures in nodejs. If you're using ESM and seeing failures, it may be due to a bundler or transpiler which is incorrectly converting import statements into require calls.What's Changed
get-func-namedependency by [@koddsson](https://rConfiguration
📅 Schedule: Branch creation - "after 2pm on Monday" in timezone Europe/Zurich, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.