chore(deps): update all non-major npm dependencies #192
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:
^7.24.5
->^7.24.7
^7.24.5
->^7.24.7
^7.24.5
->^7.24.7
^7.24.5
->^7.24.7
^7.24.1
->^7.24.7
^7.24.5
->^7.24.7
^7.24.5
->^7.24.7
^7.24.5
->^7.24.7
^7.20.5
->^7.20.6
^20.12.12
->^20.14.2
^18.3.2
->^18.3.3
^7.9.0
->^7.12.0
^7.9.0
->^7.12.0
^4.2.1
->^4.3.1
^5.0.4
->^5.0.5
^1.6.8
->^1.7.2
^12.0.0
->^12.1.0
^13.9.0
->^13.11.0
^3.2.0
->^3.3.0
^0.21.3
->^0.21.5
^9.2.0
->^9.4.0
^6.1.1
->^6.2.0
^7.34.1
->^7.34.2
^10.3.15
->^10.4.1
4.0.5
->4.0.7
^3.11.0
->^3.12.0
^3.2.5
->^3.3.1
^29.1.2
->^29.1.4
^2.6.2
->^2.6.3
^5.2.11
->^5.2.13
^2.0.19
->^2.0.21
~0.14.6
->~0.14.7
Release Notes
babel/babel (@babel/cli)
v7.24.7
Compare Source
🐛 Bug Fix
babel-node
babel-traverse
constantViolations
with destructuring (@liuxingbaoyu)babel-helper-transform-fixture-test-runner
,babel-plugin-proposal-explicit-resource-management
using
inswitch
correctly (@liuxingbaoyu)🏠 Internal
babel-helpers
,babel-runtime-corejs2
,babel-runtime-corejs3
,babel-runtime
v7.24.6
Compare Source
🐛 Bug Fix
babel-helper-create-class-features-plugin
,babel-plugin-transform-class-properties
babel-core
,babel-generator
,babel-plugin-transform-modules-commonjs
babel-helper-create-class-features-plugin
,babel-plugin-proposal-decorators
babel-helpers
,babel-plugin-proposal-decorators
,babel-runtime-corejs3
babel-parser
,babel-plugin-transform-typescript
cls.fn<C> = x
(@liuxingbaoyu)🏠 Internal
babel-core
,babel-helpers
,babel-plugin-transform-runtime
,babel-preset-env
,babel-runtime-corejs2
,babel-runtime-corejs3
,babel-runtime
babel-helpers
tsconfig.json
for@babel/helpers/src/helpers
(@nicolo-ribaudo)babel-cli
,babel-helpers
,babel-plugin-external-helpers
,babel-plugin-proposal-decorators
,babel-plugin-transform-class-properties
,babel-plugin-transform-modules-commonjs
,babel-plugin-transform-modules-systemjs
,babel-plugin-transform-runtime
,babel-preset-env
,babel-runtime-corejs2
,babel-runtime-corejs3
,babel-runtime
babel-parser
,babel-traverse
babel/babel (@babel/parser)
v7.24.7
Compare Source
v7.24.7 (2024-06-05)
🐛 Bug Fix
babel-node
babel-traverse
constantViolations
with destructuring (@liuxingbaoyu)babel-helper-transform-fixture-test-runner
,babel-plugin-proposal-explicit-resource-management
using
inswitch
correctly (@liuxingbaoyu)🏠 Internal
babel-helpers
,babel-runtime-corejs2
,babel-runtime-corejs3
,babel-runtime
Committers: 7
v7.24.6
Compare Source
v7.24.6 (2024-05-24)
Thanks @amjed-98, @blakewilson, @coelhucas, and @SukkaW for your first PRs!
🐛 Bug Fix
babel-helper-create-class-features-plugin
,babel-plugin-transform-class-properties
babel-core
,babel-generator
,babel-plugin-transform-modules-commonjs
babel-helper-create-class-features-plugin
,babel-plugin-proposal-decorators
babel-helpers
,babel-plugin-proposal-decorators
,babel-runtime-corejs3
babel-parser
,babel-plugin-transform-typescript
cls.fn<C> = x
(@liuxingbaoyu)🏠 Internal
babel-core
,babel-helpers
,babel-plugin-transform-runtime
,babel-preset-env
,babel-runtime-corejs2
,babel-runtime-corejs3
,babel-runtime
babel-helpers
tsconfig.json
for@babel/helpers/src/helpers
(@nicolo-ribaudo)babel-cli
,babel-helpers
,babel-plugin-external-helpers
,babel-plugin-proposal-decorators
,babel-plugin-transform-class-properties
,babel-plugin-transform-modules-commonjs
,babel-plugin-transform-modules-systemjs
,babel-plugin-transform-runtime
,babel-preset-env
,babel-runtime-corejs2
,babel-runtime-corejs3
,babel-runtime
babel-parser
,babel-traverse
Committers: 9
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v7.12.0
Compare Source
🚀 Features
eslint-plugin: [no-useless-template-literals] rename to
no-useless-template-expression
(deprecateno-useless-template-literals
)rule-tester: check for parsing errors in suggestion fixes
rule-tester: port
checkDuplicateTestCases
from ESLinteslint-plugin: [no-floating-promises] add option 'allowForKnownSafePromises'
🩹 Fixes
no-useless-template-expression -> no-unnecessary-template-expression
eslint-plugin: [no-unnecessary-type-assertion] combine template literal check with
const
variable checkeslint-plugin: [dot-notation] fix false positive when accessing private/protected property with optional chaining
eslint-plugin: [explicit-member-accessibility] refine report locations
eslint-plugin: [no-unnecessary-type-assertion] declares are always defined, so always check
declare
seslint-plugin: [prefer-literal-enum-member] allow using member it self on allowBitwiseExpressions
eslint-plugin: [return-await] clean up in-try-catch detection and make autofixes safe
eslint-plugin: [member-ordering] also TSMethodSignature can be get/set
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v7.11.0
Compare Source
🚀 Features
🩹 Fixes
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v7.10.0
Compare Source
🚀 Features
🩹 Fixes
❤️ Thank You
You can read about our versioning strategy and releases on our website.
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
v7.12.0
Compare Source
🩹 Fixes
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v7.11.0
Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v7.10.0
Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
vitejs/vite-plugin-react (@vitejs/plugin-react)
v4.3.1
Compare 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-runtime
dependency.Reminder: Vite expect code outside of
node_modules
to be ESM, so you will need to update the gist withimport React from 'react'
.v4.3.0
Compare Source
Fix support for React compiler
Don't set
retainLines: true
when 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.
vitejs/vite-plugin-vue (@vitejs/plugin-vue)
v5.0.5
__VUE_PROD_DEVTOOLS__
(#81) (277a3ab), closes #81axios/axios (axios)
v1.7.2
Compare Source
Bug Fixes
Contributors to this release
v1.7.1
Compare Source
Bug Fixes
Contributors to this release
v1.7.0
Compare Source
Features
Bug Fixes
Contributors to this release
tj/commander.js (commander)
v12.1.0
Compare Source
Added
cypress-io/cypress (cypress)
v13.11.0
Compare Source
Changelog: https://docs.cypress.io/guides/references/changelog#13-11-0
v13.10.0
Compare Source
Changelog: https://docs.cypress.io/guides/references/changelog#13-10-0
knowledgecode/date-and-time (date-and-time)
v3.3.0
Compare Source
evanw/esbuild (esbuild)
v0.21.5
Compare Source
Fix
Symbol.metadata
on classes without a class decorator (#3781)This release fixes a bug with esbuild's support for the decorator metadata proposal. Previously esbuild only added the
Symbol.metadata
property to decorated classes if there was a decorator on the class element itself. However, the proposal says that theSymbol.metadata
property should be present on all classes that have any decorators at all, not just those with a decorator on the class element itself.Allow unknown import attributes to be used with the
copy
loader (#3792)Import attributes (the
with
keyword onimport
statements) are allowed to alter how that path is loaded. For example, esbuild cannot assume that it knows how to load./bagel.js
as typebagel
:Because of that, bundling this code with esbuild is an error unless the file
./bagel.js
is external to the bundle (such as with--bundle --external:./bagel.js
).However, there is an additional case where it's ok for esbuild to allow this: if the file is loaded using the
copy
loader. That's because thecopy
loader behaves similarly to--external
in that the file is left external to the bundle. The difference is that thecopy
loader copies the file into the output folder and rewrites the import path while--external
doesn't. That means the following will now work with thecopy
loader (such as with--bundle --loader:.bagel=copy
):Support import attributes with glob-style imports (#3797)
This release adds support for import attributes (the
with
option) to glob-style imports (dynamic imports with certain string literal patterns as paths). These imports previously didn't support import attributes due to an oversight. So code like this will now work correctly:Previously this didn't work even though esbuild normally supports forcing the JSON loader using an import attribute. Attempting to do this used to result in the following error:
In addition, this change means plugins can now access the contents of
with
for glob-style imports.Support
${configDir}
intsconfig.json
files (#3782)This adds support for a new feature from the upcoming TypeScript 5.5 release. The character sequence
${configDir}
is now respected at the start ofbaseUrl
andpaths
values, which are used by esbuild during bundling to correctly map import paths to file system paths. This feature lets basetsconfig.json
files specified viaextends
refer to the directory of the top-leveltsconfig.json
file. Here is an example:You can read more in TypeScript's blog post about their upcoming 5.5 release. Note that this feature does not make use of template literals (you need to use
"${configDir}/dist/js/*"
not`${configDir}/dist/js/*`
). The syntax fortsconfig.json
is still just JSON with comments, and JSON syntax does not allow template literals. This feature only recognizes${configDir}
in strings for certain path-like properties, and only at the beginning of the string.Fix internal error with
--supported:object-accessors=false
(#3794)This release fixes a regression in 0.21.0 where some code that was added to esbuild's internal runtime library of helper functions for JavaScript decorators fails to parse when you configure esbuild with
--supported:object-accessors=false
. The reason is that esbuild introduced code that does{ get [name]() {} }
which uses both theobject-extensions
feature for the[name]
and theobject-accessors
feature for theget
, but esbuild was incorrectly only checking forobject-extensions
and not forobject-accessors
. Additional tests have been added to avoid this type of issue in the future. A workaround for this issue in earlier releases is to also add--supported:object-extensions=false
.v0.21.4
Compare Source
Update support for import assertions and import attributes in node (#3778)
Import assertions (the
assert
keyword) have been removed from node starting in v22.0.0. So esbuild will now strip them and generate a warning with--target=node22
or above:Import attributes (the
with
keyword) have been backported to node 18 starting in v18.20.0. So esbuild will no longer strip them with--target=node18.N
ifN
is 20 or greater.Fix
for await
transform when a label is presentThis release fixes a bug where the
for await
transform, which wraps the loop in atry
statement, previously failed to also move the loop's label into thetry
statement. This bug only affects code that uses both of these features in combination. Here's an example of some affected code:Do additional constant folding after cross-module enum inlining ([#3416](https://togithub.com/evanw/esbuild/issues/341
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 has been generated by Mend Renovate. View repository job log here.