chore(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
enhanced-resolve	^5.22.2 → ^5.23.0
eslint-plugin-jsdoc	63.0.1 → 63.0.2
happy-dom	^20.10.1 → ^20.10.2
knip (source)	6.15.0 → 6.16.1
semver	7.8.1 → 7.8.2

---

Release Notes

webpack/enhanced-resolve (enhanced-resolve)

v5.23.0

Compare Source

Minor Changes

• Allow the path-like resolve options roots, modules, alias/fallback targets, restrictions, and tsconfig (the config file, configFile, baseUrl, and references) to accept file URL instances (such as new URL("./dir/", import.meta.url)), converting them to filesystem paths. Plain strings are still treated as literal paths, matching Node's fs. (by @​alexander-akait in #​604)

gajus/eslint-plugin-jsdoc (eslint-plugin-jsdoc)

v63.0.2

Compare Source

Bug Fixes

• allow typedef returns that may be void; fixes #​1390 (#​1699) (319e84b)

capricorn86/happy-dom (happy-dom)

v20.10.2

Compare Source

👷‍♂️ Patch fixes

• Updates external dependencies - By @​capricorn86 in task #​2163

webpro-nl/knip (knip)

v6.16.1: Release 6.16.1

Compare Source

• Resolve SvelteKit ./$types in monorepos (resolve #​1778) (370ef4c)

v6.16.0: Release 6.16.0

Compare Source

• Update sponsors data + fix sponsors layout on narrow screen (fadf13a)
• Detect binaries and entry files in node:child_process calls (fc3598c)
• It works™ (2d9ce84)
• Extend known issues doc w/ workaround (close #​1763) (fcd444b)
• Support ignoreExportsUsedInFile per workspace (close #​1495) (4b898a9)
• feat(vscode): add workspaceRoot config option to enable use in a VSCode workspace that does not have package.json at the workspace root (#​1667) (7c1ebef) - thanks @​anmilleriii!
• Replace minimist with node:util.parseArgs (resolve #​1492) (b360c5c)
• Preserve minimist numeric coercion and --no-x negation (c12153c)
• Simplify parseArgs adapter (ba15e41)
• Detect and credit registered custom elements (resolve #​1394) (62dcda5)
• Add Lit and FAST plugins to detect @​customElement classes (348d2c9)
• Add new testimonials (77fd7ed)
• Scope custom path aliases per workspace (resolve #​1775) (d908099)
• Restructure tests (ec4c779)
• Simplify boolean check in parseArgs adapter (ba6865d)
• Scope static custom-element define detection to the FAST plugin (94632cd)
• Add Custom Elements feature docs page (230bd73)
• Update known-issues.md (f1f4c1b)
• Fix crash on backtick string literals in plugin config (resolve #​1776) (f1adc7f)
• Format (e4720ca)
• Fix backtick string literals in require() and plugin-name config arrays (#​1776) (d14eb05)
• Credit custom elements via aliases, scoped registries, and static blocks (d7cbe12)
• Improve Stencil plugin: credit @​Component and recognize test files (152d730)
• Add Catalyst plugin to credit bare @​controller custom elements (8a37f8c)
• Document Stencil, Catalyst, static-block custom el reg. (105fba3)
• Auto-format md (f4fcf4e)

npm/node-semver (semver)

v7.8.2

Compare Source

Bug Fixes

• bea6028 #​870 increment dotted prerelease identifiers (#​870) (@​liuzemei, @​SheldonNeo)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "on Monday"
• 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.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	ofetch@​1.5.1
	scule@​1.3.0
	klona@​2.0.6
	ohash@​2.0.11
	perfect-debounce@​2.1.0
	pathe@​2.0.3
	mlly@​1.8.2
	knitwork@​1.3.0
	ufo@​1.6.4
	std-env@​4.1.0
	node-fetch@​3.3.2
	magic-string@​0.30.21
	pkg-types@​2.3.1
	hookable@​5.5.3

View full report

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@nuxt/bridge@1843

npm i https://pkg.pr.new/@nuxt/bridge-schema@1843

commit: 140a851

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm kind-of is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/kind-of@6.0.3 ℹ Read more on: This package | This alert | What is obfuscated code? 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/kind-of@6.0.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.
Warn		Obfuscated code: npm node-fetch-native is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/@nuxt/test-utils@3.23.0 → npm/ofetch@1.5.1 → npm/node-fetch-native@1.6.7 ℹ Read more on: This package | This alert | What is obfuscated code? 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/node-fetch-native@1.6.7. 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 node-forge is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/node-forge@1.4.0 ℹ Read more on: This package | This alert | What is obfuscated code? 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/node-forge@1.4.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 powershell-utils is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/powershell-utils@0.1.0 ℹ Read more on: This package | This alert | What is obfuscated code? 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/powershell-utils@0.1.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 string.prototype.trimend is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/string.prototype.trimend@1.0.9 ℹ Read more on: This package | This alert | What is obfuscated code? 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/string.prototype.trimend@1.0.9. 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 tar is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/tar@7.5.13 ℹ Read more on: This package | This alert | What is obfuscated code? 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/tar@7.5.13. 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.

View full report