fix(deps): update npm - - package.json #1135
Open
+223
−223
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:
^0.25.8
->^0.25.9
^0.25.8
->^0.25.9
0.25.8
->0.25.9
0.25.8
->0.25.9
^22.17.0
->^22.17.1
^8.38.0
->^8.39.1
^8.38.0
->^8.39.1
^14.5.3
->^14.5.4
^5.5.3
->^5.5.4
^1.32.2
->^1.32.3
^6.6.2
->^6.6.4
^4.20.3
->^4.20.4
^5.8.3
->^5.9.2
Release Notes
evanw/esbuild (@esbuild/darwin-arm64)
v0.25.9
Compare Source
Better support building projects that use Yarn on Windows (#3131, #3663)
With this release, you can now use esbuild to bundle projects that use Yarn Plug'n'Play on Windows on drives other than the
C:
drive. The problem was as follows:C:
driveD:
drive../..
to get from the project directory to the cache directory..
(soD:\..
is justD:
)Yarn works around this edge case by pretending Windows-style paths beginning with
C:\
are actually Unix-style paths beginning with/C:/
, so the../..
path segments are able to navigate across drives inside Yarn's implementation. This was broken for a long time in esbuild but I finally got access to a Windows machine and was able to debug and fix this edge case. So you should now be able to bundle these projects with esbuild.Preserve parentheses around function expressions (#4252)
The V8 JavaScript VM uses parentheses around function expressions as an optimization hint to immediately compile the function. Otherwise the function would be lazily-compiled, which has additional overhead if that function is always called immediately as lazy compilation involves parsing the function twice. You can read V8's blog post about this for more details.
Previously esbuild did not represent parentheses around functions in the AST so they were lost during compilation. With this change, esbuild will now preserve parentheses around function expressions when they are present in the original source code. This means these optimization hints will not be lost when bundling with esbuild. In addition, esbuild will now automatically add this optimization hint to immediately-invoked function expressions. Here's an example:
Note that you do not want to wrap all function expressions in parentheses. This optimization hint should only be used for functions that are called on initial load. Using this hint for functions that are not called on initial load will unnecessarily delay the initial load. Again, see V8's blog post linked above for details.
Update Go from 1.23.10 to 1.23.12 (#4257, #4258)
This should have no effect on existing code as this version change does not change Go's operating system support. It may remove certain false positive reports (specifically CVE-2025-4674 and CVE-2025-47907) from vulnerability scanners that only detect which version of the Go compiler esbuild uses.
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v8.39.1
Compare Source
This was a version bump only for eslint-plugin to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.39.0
Compare Source
🚀 Features
🩹 Fixes
unsafeObjectPattern
message (#11403)check
option for most RHS of a chain (#11272)❤️ Thank You
You can read about our versioning strategy and releases on our website.
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
v8.39.1
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.
v8.39.0
Compare Source
🚀 Features
❤️ Thank You
You can read about our versioning strategy and releases on our website.
cypress-io/cypress (cypress)
v14.5.4
Compare Source
Changelog: https://docs.cypress.io/app/references/changelog#14-5-4
prettier/eslint-plugin-prettier (eslint-plugin-prettier)
v5.5.4
Compare Source
Patch Changes
#755
723f7a8
Thanks @kbrilla! - fix: add 'oxc', 'oxc-ts' and 'hermes' parsers toparserBlocklist
#751
cf52b30
Thanks @andreww2012! - fix: disallow extra properties in rule optionsisomorphic-git/isomorphic-git (isomorphic-git)
v1.32.3
Compare Source
Bug Fixes
panva/openid-client (openid-client)
v6.6.4
Compare Source
Fixes
v6.6.3
Compare Source
Documentation
Refactor
privatenumber/tsx (tsx)
v4.20.4
Compare Source
microsoft/TypeScript (typescript)
v5.9.2
Compare Source
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.