-
Notifications
You must be signed in to change notification settings - Fork 129
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
fix(deps): update npm - - package.json #883
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/manager
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.
Open
Conversation
This file contains 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
✅ Deploy Preview for endearing-brigadeiros-63f9d0 canceled.
|
Dependency ReviewThe following issues were found:
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #883 +/- ##
=======================================
Coverage 50.08% 50.08%
=======================================
Files 48 48
Lines 1711 1711
Branches 174 174
=======================================
Hits 857 857
Misses 834 834
Partials 20 20 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
ba76a32
to
380fdd8
Compare
2334742
to
22afbd1
Compare
08d1f5a
to
6deb3fa
Compare
9e8e20d
to
19f1ad6
Compare
6a81a36
to
7664a5b
Compare
caf53b2
to
aaa02a7
Compare
18c41af
to
69c5940
Compare
69c5940
to
131deb5
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:
^7.23.2
->^7.26.10
^7.22.9
->^7.27.0
^7.22.5
->^7.26.3
^19.0.0
->^19.8.0
^19.0.0
->^19.8.0
^0.18.20
->^0.25.2
^0.23.0
->^0.25.2
0.23.0
->0.25.2
0.23.0
->0.25.2
^4.11.0
->^4.12.4
^19.8.0
->^19.15.1
^4.0.2
->^4.1.1
^4.17.15
->^4.17.16
^22.13.5
->^22.14.0
^8.26.1
->^8.29.1
^8.26.1
->^8.29.1
^4.0.2
->^4.3.4
^1.6.0
->^1.8.4
^1.20.1
->^1.20.3
^4.2.0
->^4.5.0
^4.3.0
->^4.4.0
^9.0.0
->^9.1.2
^14.0.0
->^14.2.1
^3.4.33
->^3.4.51
^8.57.0
->^8.57.1
^10.0.1
->^10.1.1
^5.0.0
->^5.2.6
^7.21.5
->^7.37.5
^4.18.2
->^4.21.2
^2.0.0
->^2.1.1
^7.1.5
->^7.5.0
^1.17.1
->^1.18.1
^9.0.0
->^9.1.7
^1.27.1
->^1.30.1
^1.4.1
->^1.5.0
^6.0.0
->^6.0.3
^2.29.4
->^2.30.1
^5.0.0
->^5.9.2
^6.6.1
->^6.10.0
^17.0.0
->^17.1.0
^6.2.0
->^6.4.1
^1.0.4
->^1.4.0
^1.5.5
->^1.5.6
^3.0.0
->^3.5.3
^16.13.1
->^16.14.0
^16.13.1
->^16.14.0
6.28.2
->6.30.0
^3.25.0
->^3.27.0
^19.0.2
->^19.0.5
^5.7.3
->^5.8.3
^11.0.0
->^11.1.0
4.5.5
->4.5.12
Release Notes
babel/babel (@babel/core)
v7.26.10
Compare Source
👓 Spec Compliance
babel-parser
🐛 Bug Fix
babel-parser
,babel-template
babel-core
babel-parser
,babel-plugin-transform-typescript
babel-traverse
babel-generator
abstract override
(@liuxingbaoyu)babel-parser
babel-helpers
,babel-runtime
,babel-runtime-corejs2
,babel-runtime-corejs3
💅 Polish
babel-standalone
🏠 Internal
babel-parser
v7.26.9
Compare Source
🐛 Bug Fix
babel-types
TSPropertySignature.kind
(@liuxingbaoyu)babel-generator
,babel-types
🏠 Internal
babel-types
.ts
files with explicit reexports to solve name conflicts (@nicolo-ribaudo)babel-core
@types/gensync
in Babel 7 (@nicolo-ribaudo)v7.26.8
Compare Source
v7.26.8 (2025-02-08)
🏠 Internal
babel-preset-env
v7.26.7
Compare Source
🐛 Bug Fix
babel-helpers
,babel-preset-env
,babel-runtime-corejs3
babel-plugin-transform-typeof-symbol
typeof
in arrow functions (@liuxingbaoyu)babel-parser
ranges
option in estree method value (@JLHwung)babel-core
babel-plugin-transform-typescript
babel-plugin-transform-typescript
,babel-traverse
,babel-types
import x = y.z
(@liuxingbaoyu)conventional-changelog/commitlint (@commitlint/cli)
v19.8.0
Compare Source
Performance Improvements
node:
prefix to bypass require.cache call for builtins (#4302) (0cd8f41)19.7.1 (2025-02-02)
Note: Version bump only for package @commitlint/cli
19.6.1 (2024-12-15)
Note: Version bump only for package @commitlint/cli
v19.7.1
Compare Source
Note: Version bump only for package @commitlint/cli
conventional-changelog/commitlint (@commitlint/config-conventional)
v19.8.0
Compare Source
Performance Improvements
node:
prefix to bypass require.cache call for builtins (#4302) (0cd8f41)19.7.1 (2025-02-02)
Note: Version bump only for package @commitlint/config-conventional
v19.7.1
Compare Source
Note: Version bump only for package @commitlint/config-conventional
evanw/esbuild (@esbuild/darwin-arm64)
v0.25.2
Compare Source
Support flags in regular expressions for the API (#4121)
The JavaScript plugin API for esbuild takes JavaScript regular expression objects for the
filter
option. Internally these are translated into Go regular expressions. However, this translation previously ignored theflags
property of the regular expression. With this release, esbuild will now translate JavaScript regular expression flags into Go regular expression flags. Specifically the JavaScript regular expression/\.[jt]sx?$/i
is turned into the Go regular expression`(?i)\.[jt]sx?$`
internally inside of esbuild's API. This should make it possible to use JavaScript regular expressions with thei
flag. Note that JavaScript and Go don't support all of the same regular expression features, so this mapping is only approximate.Fix node-specific annotations for string literal export names (#4100)
When node instantiates a CommonJS module, it scans the AST to look for names to expose via ESM named exports. This is a heuristic that looks for certain patterns such as
exports.NAME = ...
ormodule.exports = { ... }
. This behavior is used by esbuild to "annotate" CommonJS code that was converted from ESM with the original ESM export names. For example, when converting the fileexport let foo, bar
from ESM to CommonJS, esbuild appends this to the end of the file:However, this feature previously didn't work correctly for export names that are not valid identifiers, which can be constructed using string literal export names. The generated code contained a syntax error. That problem is fixed in this release:
Basic support for index source maps (#3439, #4109)
The source map specification has an optional mode called index source maps that makes it easier for tools to create an aggregate JavaScript file by concatenating many smaller JavaScript files with source maps, and then generate an aggregate source map by simply providing the original source maps along with some offset information. My understanding is that this is rarely used in practice. I'm only aware of two uses of it in the wild: ClojureScript and Turbopack.
This release provides basic support for indexed source maps. However, the implementation has not been tested on a real app (just on very simple test input). If you are using index source maps in a real app, please try this out and report back if anything isn't working for you.
Note that this is also not a complete implementation. For example, index source maps technically allows nesting source maps to an arbitrary depth, while esbuild's implementation in this release only supports a single level of nesting. It's unclear whether supporting more than one level of nesting is important or not given the lack of available test cases.
This feature was contributed by @clyfish.
v0.25.1
Compare Source
Fix incorrect paths in inline source maps (#4070, #4075, #4105)
This fixes a regression from version 0.25.0 where esbuild didn't correctly resolve relative paths contained within source maps in inline
sourceMappingURL
data URLs. The paths were incorrectly being passed through as-is instead of being resolved relative to the source file containing thesourceMappingURL
comment, which was due to the data URL not being a file URL. This regression has been fixed, and this case now has test coverage.Fix invalid generated source maps (#4080, #4082, #4104, #4107)
This release fixes a regression from version 0.24.1 that could cause esbuild to generate invalid source maps. Specifically under certain conditions, esbuild could generate a mapping with an out-of-bounds source index. It was introduced by code that attempted to improve esbuild's handling of "null" entries in source maps (i.e. mappings with a generated position but no original position). This regression has been fixed.
This fix was contributed by @jridgewell.
Fix a regression with non-file source map paths (#4078)
The format of paths in source maps that aren't in the
file
namespace was unintentionally changed in version 0.25.0. Path namespaces is an esbuild-specific concept that is optionally available for plugins to use to distinguish paths fromfile
paths and from paths meant for other plugins. Previously the namespace was prepended to the path joined with a:
character, but version 0.25.0 unintentionally failed to prepend the namespace. The previous behavior has been restored.Fix a crash with
switch
optimization (#4088)The new code in the previous release to optimize dead code in switch statements accidentally introduced a crash in the edge case where one or more switch case values include a function expression. This is because esbuild now visits the case values first to determine whether any cases are dead code, and then visits the case bodies once the dead code status is known. That triggered some internal asserts that guard against traversing the AST in an unexpected order. This crash has been fixed by changing esbuild to expect the new traversal ordering. Here's an example of affected code:
Update Go from 1.23.5 to 1.23.7 (#4076, #4077)
This should have no effect on existing code as this version change does not change Go's operating system support. It may remove certain reports from vulnerability scanners that detect which version of the Go compiler esbuild uses.
This PR was contributed by @MikeWillCook.
v0.25.0
Compare Source
This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of
esbuild
in yourpackage.json
file (recommended) or be using a version range syntax that only accepts patch upgrades such as^0.24.0
or~0.24.0
. See npm's documentation about semver for more information.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 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.