Open
Conversation
✅ Deploy Preview for oasisprotocol-playground ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
cb9020b to
00d4ae0
Compare
6299572 to
01bbd81
Compare
01bbd81 to
5e920c0
Compare
978139e to
7cbb12b
Compare
7cbb12b to
a2abe77
Compare
a2abe77 to
aead7e0
Compare
d95a260 to
41b73ec
Compare
41b73ec to
e6ecd4d
Compare
e6ecd4d to
7914fb6
Compare
7914fb6 to
920e49e
Compare
920e49e to
b61f03c
Compare
b61f03c to
f5ad800
Compare
f5ad800 to
146eae6
Compare
7dbb1cf to
73f9651
Compare
bc63286 to
82605c7
Compare
82605c7 to
96854f1
Compare
8876ac3 to
55c5c56
Compare
55c5c56 to
e7d103d
Compare
e7d103d to
430a80d
Compare
430a80d to
fd78302
Compare
fd78302 to
69bca08
Compare
69bca08 to
0163c0b
Compare
0163c0b to
de59de1
Compare
60019a3 to
b8fe2db
Compare
35a79f8 to
c67d9ef
Compare
c67d9ef to
3c60eed
Compare
3c60eed to
5dbb95b
Compare
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
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:
^11.11.1→^11.14.0^0.2.0→^0.2.6^18.2.15→^18.3.28^18.2.7→^18.3.7^4.0.3→^4.7.0^18.2.0→^18.3.1^2.9.1→^2.10.10^18.2.0→^18.3.1^9.0.1→^9.1.0^6.21.3→^6.30.3Release Notes
emotion-js/emotion (@emotion/react)
v11.14.0Compare Source
Minor Changes
a19d019Thanks @Andarist! - Source code has been migrated to TypeScript. From now on type declarations will be emitted based on that, instead of being hand-written.Patch Changes
e1bf17e]:v11.13.5Compare Source
Patch Changes
#3270
77d930dThanks @emmatown! - Fix inconsistent hashes using development vs production bundles/exportsconditions when using@emotion/babel-pluginwithsourceMap: true(the default). This is particularly visible when using Emotion with the Next.js Pages router where thedevelopmentcondition is used when bundling code but not when importing external code with Node.js.Updated dependencies [
77d930d]:v11.13.3Compare Source
Patch Changes
#3232
0ce3ed0Thanks @ENvironmentSet! - Distributecssprop attachment over props that are union typesUpdated dependencies []:
v11.13.0Compare Source
Minor Changes
#3198
d8ff8a5Thanks @Andarist! - Migrated away from relying onprocess.env.NODE_ENVchecks to differentiate between production and development builds.Development builds (and other environment-specific builds) can be used by using proper conditions (see here). Most modern bundlers/frameworks already preconfigure those for the user so no action has to be taken.
Default files should continue to work in all environments.
#3215
a9f6912Thanks @Andarist! - Addededge-lightandworkerdconditions topackage.jsonmanifest to better serve users using Vercel Edge and Cloudflare Workers.Patch Changes
d8ff8a5,a9f6912]:v11.12.0Compare Source
Patch Changes
#3206
d1994c4Thanks @DiegoAndai! - Improved compatibility with the upcoming@types/reactfor React 19 where the globalJSXnamespace doesn't exist anymore#3208
56109e7Thanks @Andarist! - Only forward definedrefs to improve compatibility with the upcoming React 19Updated dependencies [
9ca22c6,a1e881b,16d8a8c]:v11.11.4Compare Source
Patch Changes
5b82631dThanks @iegik! - Renamed an internalhasOwnPropertytohasOwn. This avoids problems in CommonJS environments when the consumer tries to prevent prototype pollution withObject.freeze(Object.prototype).v11.11.3Compare Source
Patch Changes
#3101
49c20b4fThanks @kyvong! - Fix Theme import for newer Typescript module resolution modesUpdated dependencies [
45c440fb]:FortAwesome/react-fontawesome (@fortawesome/react-fontawesome)
v0.2.6Compare Source
Fixed
processbefore readingprocess.env(#585)Full Changelog: FortAwesome/react-fontawesome@0.2.5...0.2.6
v0.2.5Compare Source
What's Changed
New Contributors
Full Changelog: FortAwesome/react-fontawesome@0.2.4...0.2.5
v0.2.3Compare Source
Changed
Font Awesome Pro+ icons are now available with an active Pro+ subscription.
Removed example directory and files
Deprecated
fa-fwpropAdded
Added
widthAutopropAdded
rotateBypropv0.2.2Compare Source
Fixed
v0.2.1Compare Source
Changed
vitejs/vite-plugin-react (@vitejs/plugin-react)
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.
facebook/react (react)
v18.3.1Compare Source
actfromreactf1338fv18.3.0Compare Source
This release is identical to 18.2 but adds warnings for deprecated APIs and other changes that are needed for React 19.
Read the React 19 Upgrade Guide for more info.
React
this.refsto support string ref codemod 909071findDOMNodeoutside StrictMode c3b283test-utilsmethods d4ea75defaultPropsfor function components #25699key#25697actfromtest-utilsd4ea75React DOM
unmountComponentAtNode8a015brenderToStaticNodeStream#28874react-bootstrap/react-bootstrap (react-bootstrap)
v2.10.10Compare Source
Bug Fixes
v2.10.9Compare Source
BREAKING CHANGES
2.10.9 (2025-01-30)
Bug Fixes
2.10.8 (2025-01-21)
Bug Fixes
2.10.7 (2024-12-15)
Bug Fixes
2.10.6 (2024-11-25)
Bug Fixes
2.10.5 (2024-09-26)
Bug Fixes
2.10.4 (2024-06-30)
Bug Fixes
2.10.3 (2024-06-19)
Bug Fixes
2.10.2 (2024-03-18)
Bug Fixes
2.10.1 (2024-02-10)
Bug Fixes
v2.10.8Compare Source
BREAKING CHANGES
2.10.9 (2025-01-30)
Bug Fixes
2.10.8 (2025-01-21)
Bug Fixes
2.10.7 (2024-12-15)
Bug Fixes
2.10.6 (2024-11-25)
Bug Fixes
2.10.5 (2024-09-26)
Bug Fixes
2.10.4 (2024-06-30)
Bug Fixes
2.10.3 (2024-06-19)
Bug Fixes
2.10.2 (2024-03-18)
Bug Fixes
2.10.1 (2024-02-10)
Bug Fixes
v2.10.7Compare Source
BREAKING CHANGES
2.10.9 (2025-01-30)
Bug Fixes
2.10.8 (2025-01-21)
Bug Fixes
2.10.7 (2024-12-15)
Bug Fixes
2.10.6 (2024-11-25)
Bug Fixes
2.10.5 (2024-09-26)
Bug Fixes
2.10.4 (2024-06-30)
Bug Fixes
2.10.3 (2024-06-19)
Bug Fixes
2.10.2 (2024-03-18)
Bug Fixes
2.10.1 (2024-02-10)
Bug Fixes
v2.10.6Compare Source
BREAKING CHANGES
2.10.9 (2025-01-30)
Bug Fixes
2.10.8 (2025-01-21)
Bug Fixes
2.10.7 (2024-12-15)
Bug Fixes
[2.10.6](https://redirect.gi
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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.