Repository navigation
chore(deps): update npm (major) - #2103
renovate[bot] wants to merge 1 commit into
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6711d269c9
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| "react-is": "^19.2.8", | ||
| "styled-components": "^5.3.11", | ||
| "typescript": "^5.9.3" | ||
| "typescript": "^7.0.2" |
There was a problem hiding this comment.
Changing the published peer dependency to ^7.0.2 makes npm peer resolution reject consumers that still use TypeScript 5, including the custom-UI setups documented in docs/custom_ui_extensions/context/custom_project_init.md and custom_test_ui_command.md, which specify TypeScript ^5.8.2. Because the package remains on version 6.6.0 and can be published with only a prerelease bump, existing 6.x consumers can encounter ERESOLVE during installation without opting into a major framework release; retain or widen the TypeScript peer range unless dropping TypeScript 5 is released as a breaking change.
Useful? React with 👍 / 👎.
6711d26 to
f558fe6
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f558fe6e84
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| "glob": "^13.0.6", | ||
| "immutability-helper": "^3.1.1", | ||
| "js-yaml": "^4.3.2", | ||
| "js-yaml": "^5.4.1", |
There was a problem hiding this comment.
ui/src/util/script.ts still uses import yaml from 'js-yaml' and calls yaml.load, but js-yaml v5 reorganized its API around flat named exports rather than the v4 CommonJS default namespace. Both UI builds traverse this module, and vite.lib.config.ts bundles non-peer dependencies, so TypeScript/Rollup cannot resolve that default export and the build stops before producing assets; switch the call site to the named load export or retain js-yaml v4.
Useful? React with 👍 / 👎.
| "jsdom": "^30.0.1", | ||
| "msw": "^2.15.0", | ||
| "msw-storybook-addon": "^2.0.7", | ||
| "msw-storybook-addon": "^3.0.0", |
There was a problem hiding this comment.
ui/.storybook/preview.tsx still uses the v2 preview-side initialize/mswLoader setup, while ui/.storybook/main.ts does not register msw-storybook-addon. Version 3 switched to the new addon architecture and requires that configuration to be migrated, so the Storybook build and visual-test workflow will fail on the obsolete integration instead of starting the mock worker; update the Storybook configuration as part of this bump or keep v2.
Useful? React with 👍 / 👎.
621c31e to
94e8dc7
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 94e8dc74e8
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| "stylelint": "^14.16.1", | ||
| "ts-node": "^10.9.2", | ||
| "typescript": "^5.9.3", | ||
| "typescript": "^7.0.2", |
There was a problem hiding this comment.
When yarn build:lib runs—also during prepublishOnly—vite.lib.config.ts invokes vite-plugin-dts, whose unplugin-dts/@volar/typescript pipeline consumes the JavaScript TypeScript compiler API. The TypeScript 7 native package selected here provides the native compiler rather than that compatible API, so declaration generation fails before dist/lib can be published. This is separate from the peer-range issue already reported: the direct development dependency itself must remain on a compiler-API-compatible TypeScript release until the declaration tooling is migrated.
Useful? React with 👍 / 👎.
| "vite": "^8.2.2", | ||
| "vite-plugin-checker": "^0.14.5", | ||
| "vitest": "^4.1.11", | ||
| "vitest": "^5.0.0", |
There was a problem hiding this comment.
Vitest 5 now rejects hoistable APIs outside the top-level scope, but EntityModal.test.tsx still calls vi.mock('uuid', ...) inside the spyOnWindowOpen helper at line 443. When yarn run test transforms that file, the nested hoistable mock causes the test file to fail instead of running; move this mock to module scope or use a non-hoisted mocking approach before taking this upgrade.
AGENTS.md reference: AGENTS.md:L20-L25
Useful? React with 👍 / 👎.
| "styled-components": "^5.3.11", | ||
| "uuid": "^14.0.2", | ||
| "vite": "^7.3.6", | ||
| "vite": "^8.2.2", |
There was a problem hiding this comment.
The generated add-on still relies on the custom chunk layout in ui/cli/vite.config_ucc-gen-ui.ts and lazy page imports in ui/src/pages/UccInit.tsx, while Vite 8 switches the production build to Rolldown and changes the emitted preload-helper/chunk output. This repository's earlier vetted dependency work explicitly kept Vite 8 reverted because that preload helper breaks the Splunk runtime, and this change adds no corresponding bundler or module-preload migration; consequently an add-on can build successfully but fail to load its lazy UI chunks in Splunk.
AGENTS.md reference: AGENTS.md:L7-L9
Useful? React with 👍 / 👎.
92de526 to
f3723ef
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f3723ef4f2
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| postcss@^8.4.19, postcss@^8.4.40, postcss@^8.5.26, postcss@^8.5.28: | ||
| version "8.5.26" |
There was a problem hiding this comment.
When CI or a developer performs the frozen install and then runs the UI build, this lock entry resolves Vite 8's new postcss@^8.5.28 request to 8.5.26; the Vite entry at lines 14350–14357 explicitly requires at least 8.5.28. The build therefore runs with an unsupported PostCSS version because the existing postcss resolution was not advanced with Vite, so raise or remove that resolution and regenerate the lockfile before enabling Vite 8.
AGENTS.md reference: AGENTS.md:L16-L18
Useful? React with 👍 / 👎.
e2636cb to
331b709
Compare
76e47c8 to
e527411
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: e52741151a
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| }, | ||
| "resolutions": { | ||
| "nanoid": "3.3.18", | ||
| "nanoid": "6.0.1", |
There was a problem hiding this comment.
The global resolution forces Nanoid 6 even though the locked PostCSS 8.5.26 declares nanoid ^3.3.17 (ui/yarn.lock:12052-12057). PostCSS's CommonJS entry loads nanoid/non-secure with require, while Nanoid 6 is ESM-only; loading PostCSS through Vite's CSS pipeline therefore throws ERR_REQUIRE_ESM before the UI build can complete. Retain the v3 resolution for this transitive dependency, or upgrade PostCSS to a release compatible with Nanoid 6.
Useful? React with 👍 / 👎.
93816c9 to
0ff1a4e
Compare
08a0a06 to
85d3b80
Compare
|
Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits. |
71d7b0e to
0452c23
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 0452c239a2
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| "@rollup/plugin-commonjs": "^29.0.3", | ||
| "@splunk/babel-preset": "^4.0.0", | ||
| "@splunk/eslint-config": "^5.1.0", | ||
| "@splunk/eslint-config": "^6.0.0", |
There was a problem hiding this comment.
Version 6 of @splunk/eslint-config targets the flat-config ESLint toolchain, but this project still runs ESLint 8.57 with ui/.eslintrc.cjs extending the legacy @splunk/eslint-config/browser-prettier entry. Consequently the yarn run lint step in .github/workflows/build-ui.yml:16-17 cannot load a compatible configuration; migrate the complete ESLint stack and config file together, or retain the 5.x preset.
AGENTS.md reference: AGENTS.md:L50-L50
Useful? React with 👍 / 👎.
| "stylelint": "^14.16.1", | ||
| "ts-node": "^10.9.2", | ||
| "typescript": "^5.9.3", | ||
| "typescript": "^7.0.2", |
There was a problem hiding this comment.
baseUrl before enabling TypeScript 7
When either Vite build invokes vite-plugin-checker, it reads ui/tsconfig.app.json, which still sets baseUrl and relies on it for the @/* path mapping. TypeScript 7 no longer supports baseUrl and reports it as a hard configuration error, so the native checker fails even independently of the already-reported declaration-tooling incompatibility. Remove baseUrl and make the mapping explicitly relative (for example, "./src/*"), or retain the earlier TypeScript release.
AGENTS.md reference: AGENTS.md:L18-L18
Useful? React with 👍 / 👎.
0452c23 to
d416541
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d416541157
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| "jsdom": "^30.0.1", | ||
| "msw": "^2.15.0", | ||
| "msw-storybook-addon": "^2.0.7", | ||
| "msw": "^3.0.3", |
There was a problem hiding this comment.
With msw@3, the msw/native entry point was removed and the package now emits lib/node/index.js, but ui/.storybook/main.ts:41-45 still calls require.resolve for lib/native/index.mjs and lib/node/index.mjs. When viteFinal runs in both the docs and visual Storybook workflows, resolution of the first nonexistent file throws MODULE_NOT_FOUND, so yarn build-storybook cannot start; remove these obsolete aliases or update them to supported v3 exports.
Useful? React with 👍 / 👎.
9620e5d to
03b1e5b
Compare
03b1e5b to
6933587
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6933587ff6
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| "@testing-library/react": "^15.0.7", | ||
| "@vitejs/plugin-react": "^4.7.0", | ||
| "@vitest/coverage-istanbul": "^4.1.11", | ||
| "@vitejs/plugin-react": "^6.1.2", |
There was a problem hiding this comment.
When any UI build loads the Vite configuration, this installs @vitejs/plugin-react 6 alongside the still-pinned vite@^7.3.6 at line 64. Plugin React 6 explicitly dropped Vite 7 support, declares vite@^8.0.0 as its peer, and uses Rolldown-specific APIs, so npm rejects this dependency graph and Yarn leaves the build using an incompatible plugin/bundler pair. Retain plugin-react 5 until the project can migrate to Vite 8, or upgrade both together.
Useful? React with 👍 / 👎.
0da3ea8 to
e89c8f0
Compare
b90091b to
f548e36
Compare
f548e36 to
21953e3
Compare
Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
^7.29.7→^8.1.0^7.29.7→^8.0.7^7.29.7→^8.0.1^7.29.7→^8.0.6^7.29.7→^8.0.7^7.29.7→^8.0.1^5.1.0→^6.0.0^3.4.0→^4.2.0^18.3.7→^19.3.0^4.7.0→^6.2.1^4.1.12→^5.1.0^8.0.4→^9.0.0^3.1.8→^4.2.3^3.0.7→^4.2.1^4.3.2→^5.5.0^30.0.1→^31.0.0^2.15.0→^3.0.4^2.0.7→^3.0.33.3.18→6.0.2^5.9.3→^7.0.2^7.3.7→^8.3.6^4.1.12→^5.1.0Release Notes
babel/babel (@babel/core)
v8.1.0Compare Source
🚀 New Feature
babel-helper-module-transforms,babel-helper-transform-fixture-test-runner,babel-helpers,babel-plugin-proposal-bytes-modules,babel-plugin-proposal-filtered-namespaces,babel-plugin-proposal-import-wasm-source,babel-plugin-proposal-text-modules,babel-plugin-transform-dynamic-import,babel-plugin-transform-json-modules,babel-runtime-corejs3,babel-runtime,babel-standalonebabel-generator,babel-helper-import-to-platform-api,babel-helper-module-transforms,babel-parser,babel-plugin-transform-export-namespace-from,babel-plugin-transform-json-modules,babel-plugin-transform-modules-amd,babel-plugin-transform-modules-commonjs,babel-plugin-transform-modules-systemjs,babel-plugin-transform-modules-umd,babel-traverse,babel-typesbabel/no-emptyeslint rule (@JLHwung)babel-helper-import-to-platform-api,babel-helper-transform-fixture-test-runner,babel-helpers,babel-plugin-proposal-bytes-modules,babel-plugin-proposal-import-wasm-source,babel-plugin-proposal-text-modules,babel-plugin-transform-json-modules,babel-runtime-corejs3,babel-runtimetype: bytesandtype: textimports (@nicolo-ribaudo)babel-generator,babel-parser,babel-traverse,babel-typesbabel-generator,babel-parser,babel-typesbabel-generator,babel-helper-module-transforms,babel-parser,babel-plugin-transform-export-namespace-from,babel-plugin-transform-modules-amd,babel-plugin-transform-modules-commonjs,babel-plugin-transform-modules-systemjs,babel-plugin-transform-modules-umd,babel-typesexport defer(@nicolo-ribaudo)babel-cli,babel-core,babel-generator,babel-helper-transform-fixture-test-runnerbabel-corebabel-core,babel-plugin-transform-classesnoUninitializedThisassumption (@nicolo-ribaudo)noClassPrototypeAssignandnoConstructorPrimitiveReturn(@nicolo-ribaudo)🐛 Bug Fix
babel-parseryieldbeforeinin an Annex B for-in init (@JLHwung)isUnparsedContextual(@JLHwung)babel-helper-skip-transparent-expression-wrappers,babel-plugin-transform-optional-chaining🔬 Output optimization
babel-helpers,babel-runtime-corejs3importDeferProxysize (@JLHwung)v8.0.10Compare Source
🐛 Bug Fix
babel-parserimport defer {}(@JLHwung)startNodeAt(@JLHwung)babel-plugin-transform-block-scopingbabel-generatorminified: trueoutput for new expression (@JLHwung)babel-plugin-transform-optional-chaining,babel-traverseScope#pushshould not push iife param after rest element (@JLHwung)babel-helper-create-class-features-plugin,babel-plugin-proposal-decoratorsbabel-typesObjectPatternproperties (@JLHwung)babel-plugin-transform-classes🏠 Internal
babel-build-external-helpers,babel-core,babel-helpers,babel-plugin-transform-async-generator-functions,babel-plugin-transform-class-properties,babel-plugin-transform-modules-commonjs,babel-plugin-transform-modules-systemjs,babel-plugin-transform-regenerator,babel-runtime-corejs3,babel-runtime🏃♀️ Performance
babel-traverse🔬 Output optimization
babel-helpers,babel-runtime-corejs3v8.0.9Compare Source
v8.0.9 (2026-10-23)
This release contains no changes. It is needed only to update the repo (which is based on
@babel/core's last release) in Node.js's CITGM.v8.0.7Compare Source
🐛 Bug Fix
babel-helper-create-regexp-features-plugin,babel-plugin-transform-dotall-regex,babel-plugin-transform-unicode-sets-regex,babel-preset-envbabel-plugin-transform-for-offor awaitintransform-for-of(@brunoborta)babel-helpers,babel-plugin-transform-async-generator-functions,babel-runtime-corejs3asyncIteratorhelper forwarding.throw()to.return()(@brunoborta)babel-parserbabel-helpers,babel-plugin-transform-class-properties,babel-plugin-transform-modules-systemjs,babel-runtime-corejs3@@toPrimitiveusage in toPrimitive helper (@nicolo-ribaudo)babel-plugin-transform-block-scopingbabel-helper-create-class-features-plugin,babel-plugin-transform-private-property-in-object#x inon static private fields before initialization (@hoobnn)babel-traverseNodePath#evaluate(@CINC0S)path.evaluate(@wulu007)babel-core🏠 Internal
babel-helpers,babel-plugin-transform-modules-commonjs,babel-runtime-corejs3interopRequireWildcardhelper (@nicolo-ribaudo)v8.0.6Compare Source
👓 Spec Compliance
babel-helper-validator-identifier,babel-parser🐛 Bug Fix
babel-parserbabel-helper-string-parser,babel-parser🏠 Internal
babel-code-frame,babel-core,babel-generator,babel-helper-create-class-features-plugin,babel-helper-module-transforms,babel-parser,babel-plugin-bugfix-safari-rest-destructuring-rhs-array,babel-plugin-proposal-destructuring-private,babel-plugin-proposal-discard-binding,babel-plugin-transform-regenerator,babel-plugin-transform-typescript,babel-preset-env,babel-traverse,babel-typesbabel-parserbabel-corebabel-build-external-helpers,babel-cli,babel-code-frame,babel-core,babel-generator,babel-helper-compilation-targets,babel-helper-create-class-features-plugin,babel-helper-globals,babel-helper-string-parser,babel-helper-transform-fixture-test-runner,babel-helper-validator-identifier,babel-node,babel-parser,babel-plugin-transform-async-generator-functions,babel-plugin-transform-runtime,babel-register,babel-runtime-corejs3,babel-traverse🏃♀️ Performance
babel-helper-compilation-targets,babel-helper-transform-fixture-test-runnerlru-cachewithflru(@nicolo-ribaudo)v8.0.5Compare Source
👓 Spec Compliance
babel-parser🐛 Bug Fix
babel-parserbabel-plugin-transform-destructuringbabel-plugin-transform-typescriptenuminto anamespace(@nicolo-ribaudo)babel-nodebabel-plugin-bugfix-safari-rest-destructuring-rhs-arraybabel-traversegetAll{Prev,Next}Siblings(@JLHwung)babel-plugin-transform-block-scopingbabel-generatorbabel-registerbabel-cli,babel-helper-transform-fixture-test-runner,babel-registerbabel-standalone@babel/standalone(@liuxingbaoyu)📝 Documentation
🏠 Internal
babel-cli,babel-core,babel-helper-compilation-targets,babel-helper-create-class-features-plugin,babel-helper-create-regexp-features-plugin,babel-helper-fixtures,babel-preset-envsemverwithverkit(@sxzz)babel-nodebabel-types🏃♀️ Performance
babel-parser@babel/parser(@liuxingbaoyu)v8.0.1Compare Source
🐛 Bug Fix
babel-parserimport defer {}(@JLHwung)startNodeAt(@JLHwung)babel-plugin-transform-block-scopingbabel-generatorminified: trueoutput for new expression (@JLHwung)babel-plugin-transform-optional-chaining,babel-traverseScope#pushshould not push iife param after rest element (@JLHwung)babel-helper-create-class-features-plugin,babel-plugin-proposal-decoratorsbabel-typesObjectPatternproperties (@JLHwung)babel-plugin-transform-classes🏠 Internal
babel-build-external-helpers,babel-core,babel-helpers,babel-plugin-transform-async-generator-functions,babel-plugin-transform-class-properties,babel-plugin-transform-modules-commonjs,babel-plugin-transform-modules-systemjs,babel-plugin-transform-regenerator,babel-runtime-corejs3,babel-runtime🏃♀️ Performance
babel-traverse🔬 Output optimization
babel-helpers,babel-runtime-corejs3v8.0.0Compare Source
👓 Spec Compliance
babel-core💥 Breaking Change
babel-cli,babel-node,babel-plugin-proposal-decorators,babel-plugin-transform-classes,babel-plugin-transform-function-name,babel-plugin-transform-modules-commonjs,babel-plugin-transform-object-rest-spread,babel-plugin-transform-parameters,babel-plugin-transform-react-constant-elements,babel-plugin-transform-regenerator,babel-preset-env,babel-registermodules: auto(@nicolo-ribaudo)babel-plugin-transform-runtime,babel-runtime-corejs3,babel-runtime@babe/runtime-corejs3(@liuxingbaoyu)babel-parserlocations: "packed"(@liuxingbaoyu)🐛 Bug Fix
babel-generatorbabel-plugin-transform-modules-systemjs📝 Documentation
🏠 Internal
🏃♀️ Performance
babel-corev7.29.13Compare Source
v7.29.13 (2026-11-04)
🐛 Bug Fix
babel-generator,babel-parserbabel-parseryieldbeforeinin an Annex B for-in init (@babel-bot)isUnparsedContextual(@babel-bot)babel-generatorjsescnumber radix to non-integer literals (@babel-bot)ofbinding of a using declaration in for-of head (@babel-bot)minified: trueoutput for new expression (@babel-bot)babel-plugin-transform-block-scopingbabel-helper-module-transforms,babel-plugin-transform-modules-commonjsbabel-helper-skip-transparent-expression-wrappers,babel-plugin-transform-optional-chainingbabel-plugin-proposal-partial-applicationbabel-registerbabel-helper-create-class-features-plugin,babel-plugin-transform-private-property-in-object#x inon static private fields before initialization (@babel-bot)babel-traversebabel-helper-create-class-features-plugin,babel-plugin-proposal-decoratorsbabel-corebabel-plugin-bugfix-safari-rest-destructuring-rhs-arraybabel-plugin-transform-destructuringbabel-helpers,babel-plugin-transform-async-generator-functions,babel-runtime-corejs3asyncIteratorhelper forwarding.throw()to.return()(@babel-bot)babel-plugin-transform-for-offor awaitintransform-for-of(@babel-bot)babel-helper-string-parser,babel-parserCommitters: 1
vitejs/vite-plugin-react (@vitejs/plugin-react)
v6.2.1Compare Source
Fix
refreshIncludeandrefreshExcludeoptions not working (#1543)Fix mistake from #1516
v6.2.0Compare Source
Add
refreshIncludeandrefreshExcludeoptions (#1516)Add
refreshIncludeandrefreshExcludeoptions to skip fast refresh for certain files that won't run in the browser.Expand
oxc-transform-reactpeer dependency range (#1540)The peer dependency version range for
oxc-transform-reactwas expanded from^0.152.0to>=0.152.0 <0.157.0.Expand
@rolldown/plugin-babelpeer dependency range (#1541)The peer dependency version range for
@rolldown/plugin-babelwas expanded from^0.1.7 || ^0.2.0to^0.1.7 || ^0.2.0 || ^0.3.0.v6.1.2Compare Source
Fix HMR for compound components (#1484)
Adding or removing a component from a compound component was not handled, creating stale updates. Doing this now triggers hmr invalidate on the file and propagates the invalidation to importers.
Fix
compiler.logDiagnosticsoption not working (#1483)With
oxc-transform-react>= 0.148, thelogDiagnosticswas not working. This version fixes it and requiresoxc-transform-react>= 0.152 as a peer dependency if you are using thecompileroption.compiler.logDiagnosticsoption is now deprecated and should be swapped for the builtincompiler.reportDiagnostics.Disable refresh for non-jsx with compiler enabled (fix #1478) ([#1485](https://r
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, 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.