[Snyk] Upgrade resolve from 1.19.0 to 1.22.12

[newf-bgreet]

Snyk has created this PR to upgrade resolve from 1.19.0 to 1.22.12.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 16 versions ahead of your current version.

• The recommended version was released 3 months ago.

Issues fixed by the recommended upgrade:

	Issue	Score	Exploit Maturity
	Regular Expression Denial of Service (ReDoS) SNYK-JS-PATHPARSE-1077067	586	Proof of Concept

Breaking Change Risk

Notice: This assessment is enhanced by AI.

Release notes

Package name: resolve

• 1.22.12 - 2026-04-11
  
  • [Fix] defaultPaths: handle null homedir gracefully
  • [Fix] homedir: fix operator precedence bug with HOMEDRIVE/HOMEPATH concatenation
  • [Fix] loadpkg: add missing return after error callback to prevent double-callback
  • [Performance] avoid an unnecessary slice
  • [Robustness] use es-errors
  • [Refactor] use non-hoisted declarations instead of expressions
  • [readme] replace runkit CI badge with shields.io check-runs badge
  • [readme] add CII Best Practices badge
  • [meta] update security policy to use GitHub PVR instead of Tidelift
  • [meta] add CONTRIBUTING.md
  • [Test] add test from v2 branch
  • [Dev Deps] update eslint, @ ljharb/eslint-config, mkdirp
  • [Dev Deps] update @ ljharb/eslint-config, eslint, npmignore
  • [actions] fix workflow permissions
• 1.22.11 - 2025-10-20
  
  • [Refactor] hoist regex expressions for efficiency (#336)
  • [meta] Fix broken repository URL in package.json (#334)
  • [meta] add threat model
  • [meta] gitignore coverage output
  • [meta] add IRP
  • [Deps] update is-core-module
  • [actions] set proper permissions
  • [Tests] install npm 5 before npm 6 in node 7 on windows
  • [Dev Deps] update @ ljharb/eslint-config, array.prototype.map
• 1.22.10 - 2024-12-19
  
  • [meta] ensure list-export fixtures are not published
  • [meta] add missing engines.node
• 1.22.9 - 2024-12-13
  
  • [Deps] update is-core-module
  • [Dev Deps] update @ ljharb/eslint-config, array.prototype.map, npmignore, tape
  • [actions] split out node 10-20, and 20+
  • [Tests] replace aud with npm audit
• 1.22.8 - 2023-10-10
  
  • [Tests] rename innocent test project to avoid flawed security scanners
  • [Tests] skip some tests for a broken require.resolve in node v8.9, v9.0-v9.2
• 1.22.7 - 2023-10-10
  
  • [Tests] avoid publishing "malformed package.json" test to avoid flawed security scanners
• 1.22.6 - 2023-09-15
  
  • [Fix] allow npx resolve to work (#316)
  • [actions] use reusable rebase action
• 1.22.5 - 2023-09-14
  
  • [Fix] fix npx resolve by handling symlinks (#315)
  • [Dev Deps] update array.prototype.map
• 1.22.4 - 2023-08-04
• 1.22.3 - 2023-04-14
• 1.22.2 - 2023-04-05
• 1.22.1 - 2022-06-17
• 1.22.0 - 2022-01-22
• 1.21.1 - 2022-01-21
• 1.21.0 - 2022-01-03
• 1.20.0 - 2021-02-11
• 1.19.0 - 2020-11-10

from resolve GitHub release notes

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.
• Max score is 1000. Note that the real score may have changed since the PR was raised.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[newf-bgreet]

This is a minor version upgrade for the resolve package. While minor updates within the same major version are typically safe and do not contain breaking API changes, no explicit changelog or release notes could be found for the specific version range from 1.19.0 to 1.22.12.

Package documentation notes a future breaking change regarding the default value of the preserveSymlinks option, but this is scheduled for the next major version (v2.0.0) and does not affect this upgrade.

Verification: Due to the lack of detailed release notes, the risk is assessed as medium. It is recommended to run tests after the upgrade to ensure that bug fixes or other undocumented changes have not impacted your project's behavior.

Source: Package documentation

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.