You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
chore(deps): update all non-major dependencies - #1850
Allow the context path and request arguments of resolve (and resolveSync/resolvePromise) to accept file:URL instances, converting them to filesystem paths. Plain strings stay literal paths, matching Node's fs. (by @alexander-akait in #607)
Patch Changes
Make the resolver runtime-agnostic so it works in browsers, Deno and Bun as well as Node. File contents are decoded without assuming a Node Buffer, and browser shims are provided for the path, url and graceful-fs builtins (Node, Deno and Bun keep using the native ones) so the package bundles for the browser — supply your own fileSystem there. (by @alexander-akait in #606)
Rename the positional resolve/resolveSync/resolvePromise parameters to parent/specifier (from path/request) for ESM-aligned naming and document them in the README. Purely cosmetic — arguments are positional, so there is no behavior or API change. (by @alexander-akait in #611)
Next steps: Take a moment to review the security alert above. Review
the linked package source code to understand the potential risk. Ensure the
package is not malicious before proceeding. If you're unsure how to proceed,
reach out to your security team or ask the Socket team for help at
support@socket.dev.
Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/@typescript-eslint/eslint-plugin@8.61.0. You can
also ignore all packages with @SocketSecurity ignore-all.
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
Warn
Obfuscated code: npm happy-dom is 90.0% likely obfuscated
Next steps: Take a moment to review the security alert above. Review
the linked package source code to understand the potential risk. Ensure the
package is not malicious before proceeding. If you're unsure how to proceed,
reach out to your security team or ask the Socket team for help at
support@socket.dev.
Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/happy-dom@20.10.3. You can
also ignore all packages with @SocketSecurity ignore-all.
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
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
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:
^3.5.35→^3.5.38^8.16.0→^8.17.0^5.23.0→^5.24.0^65.0.0→^65.0.1^20.10.2→^20.10.3^0.6.6→^0.6.710.34.1→10.34.3^4.61.1→^4.62.07.8.2→7.8.4^8.60.1→^8.61.0Release Notes
vuejs/core (@vue/reactivity)
v3.5.38Compare Source
v3.5.37Compare Source
v3.5.36Compare Source
Bug Fixes
once: true(#14902) (450a8a8)acornjs/acorn (acorn)
v8.17.0Compare Source
webpack/enhanced-resolve (enhanced-resolve)
v5.24.0Compare Source
Minor Changes
contextpath andrequestarguments ofresolve(andresolveSync/resolvePromise) to acceptfile:URLinstances, converting them to filesystem paths. Plain strings stay literal paths, matching Node'sfs. (by @alexander-akait in #607)Patch Changes
Make the resolver runtime-agnostic so it works in browsers, Deno and Bun as well as Node. File contents are decoded without assuming a Node
Buffer, and browser shims are provided for thepath,urlandgraceful-fsbuiltins (Node, Deno and Bun keep using the native ones) so the package bundles for the browser — supply your ownfileSystemthere. (by @alexander-akait in #606)Rename the positional
resolve/resolveSync/resolvePromiseparameters toparent/specifier(frompath/request) for ESM-aligned naming and document them in the README. Purely cosmetic — arguments are positional, so there is no behavior or API change. (by @alexander-akait in #611)sindresorhus/eslint-plugin-unicorn (eslint-plugin-unicorn)
v65.0.1Compare Source
no-unused-array-method-return: Fix false positive on type assertions (#3065)4939b00prefer-https: Fix false positive on XML namespace URIs (#3063)5184262capricorn86/happy-dom (happy-dom)
v20.10.3Compare Source
pnpm/pnpm (pnpm)
v10.34.3Compare Source
v10.34.2Compare Source
rollup/rollup (rollup)
v4.62.0Compare Source
2026-06-13
Features
Pull Requests
npm/node-semver (semver)
v7.8.4Compare Source
Bug Fixes
e583226#874 reject numeric segments after x-ranges (@pupuking723)v7.8.3Compare Source
Bug Fixes
046da7f#872 align caret includePrerelease lower bounds (#872) (@wayyoungboy)Chores
3485dda#866 bump @npmcli/eslint-config from 6.0.1 to 7.0.0 (#866) (@dependabot[bot])typescript-eslint/typescript-eslint (typescript-eslint)
v8.61.0Compare Source
This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
Configuration
📅 Schedule: (UTC)
🚦 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.