Update enhanced-resolve 5.20.1 → 5.21.0 (minor)

[depfu]

[ci-all]

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ enhanced-resolve (5.20.1 → 5.21.0) · Repo · Changelog

Release Notes

5.21.0

Minor Changes

• Added promise API and support to resolve without context and resolveContext. (by @alexander-akait in #520)

• Add extensionAliasForExports option. When true, extensionAlias also applies to paths resolved through the package.json exports field. Off by default to match Node.js; opt in for full TypeScript-resolver parity with packages that ship .ts sources alongside the compiled .js they declare in exports. (by @alexander-akait in #554)

Patch Changes

• Properly handle DOS device paths (\\?\… and \\.\…). (by @alexander-akait in #551)

• Prevent fallback to parent node_modules when the exports field target file is not found. (by @xiaoxiaojx in #495)

• Imports field spec deviation: non-relative targets (e.g. "#a": "#b") no longer re-enter imports resolution, aligning with the Node.js ESM spec where PACKAGE_IMPORTS_RESOLVE does not recursively resolve # specifiers. (by @xiaoxiaojx in #503)

  Previously { "#a": "#b", "#b": "./the.js" } would chain-resolve #a to ./the.js; now it correctly fails, matching Node.js behavior.

• Move cachedJoin/cachedDirname/createCachedBasename caches from module-level globals to per-Resolver instances. This prevents unbounded memory growth in long-running processes — when a Resolver is garbage collected, its join/dirname/basename caches are released with it. (by @xiaoxiaojx in #507)

• Fixed when tsconfig: true is used (default config file) and no tsconfig.json exists. (by @xiaoxiaojx in #502)

• Apply the extensionAlias option to the imports field to be align with typescript resolution. (by @alexander-akait in #549)

• Improved performance of the many plugins. (by @alexander-akait in #529)

• Replace the Set<string>-based resolver stack with a singly-linked StackEntry class that exposes a Set-compatible API. (by @xiaoxiaojx in #526)

  Each doResolve call now prepends a single linked-list node instead of cloning the entire Set, making stack push O(1) in time and memory. Recursion detection walks the linked list (O(n)), but because the stack is typically shallow this is much cheaper than cloning a Set per call.

• Cache the result of stripJsonComments + JSON.parse in readJson using a WeakMap keyed by the raw file buffer. This avoids redundant comment-stripping and JSON parsing on every resolve call that reads tsconfig.json files (via stripComments: true), improving TsconfigPathsPlugin warm performance by ~20-35% depending on the depth of the extends chain. (by @xiaoxiaojx in #524)

• Avoid OOM in CachedInputFileSystem when duration is Infinity. (by @alexander-akait in #527)

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 24825af4-4650-4643-82d8-ac5e3f241898

📥 Commits

Reviewing files that changed from the base of the PR and between 3adb79b and a7891f7.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (4)

• packages/@tailwindcss-cli/package.json
• packages/@tailwindcss-node/package.json
• packages/@tailwindcss-standalone/package.json
• packages/@tailwindcss-upgrade/package.json

✅ Files skipped from review due to trivial changes (4)

• packages/@tailwindcss-node/package.json
• packages/@tailwindcss-upgrade/package.json
• packages/@tailwindcss-cli/package.json
• packages/@tailwindcss-standalone/package.json

---

Walkthrough

The changes update the enhanced-resolve dependency version in four packages from ^5.20.1 to ^5.21.0: @tailwindcss/cli, @tailwindcss-node, @tailwindcss-standalone, and @tailwindcss-upgrade. Each package.json file has a single line modified. No exported or public entity declarations were changed.

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically summarizes the main change: updating enhanced-resolve from version 5.20.1 to 5.21.0.
Description check	✅ Passed	The description is comprehensive and directly related to the changeset, providing detailed information about the enhanced-resolve update, release notes, and changes across all affected packages.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

_{Review rate limit: 4/5 reviews remaining, refill in 12 minutes.}

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[depfu]

Sorry, but the merge failed with:

At least 1 approving review is required by reviewers with write access.