Skip to content

chore(deps): migrate unrs-resolver to new oxc-resolver #422

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

JounQin
Copy link
Member

@JounQin JounQin commented Aug 19, 2025

Important

Migrate from unrs-resolver to oxc-resolver and update dependencies in package.json, with changes in node-resolver.ts and declared-scope.ts.

  • Dependencies:
    • Replace unrs-resolver with oxc-resolver in package.json and node-resolver.ts.
    • Update @typescript-eslint/types, eslint-import-context, minimatch, and other dependencies in package.json.
  • Code Changes:
    • Update import statements in node-resolver.ts to use oxc-resolver.
    • Change return type of declaredScope() in declared-scope.ts to ScopeType | undefined.

This description was created by Ellipsis for f75c0e4. You can customize this summary. It will automatically update as commits are pushed.

Summary by CodeRabbit

  • Chores
    • Updated development and build dependencies to latest versions for improved compatibility and stability. No user-facing functionality changes.
  • Refactor
    • Replaced the internal module resolution backend with a maintained alternative; behavior and results remain unchanged.
  • Tests
    • Updated patch metadata without altering test behavior.
  • Notes
    • Public API and runtime behavior are unchanged.

@JounQin JounQin self-assigned this Aug 19, 2025
Copy link

changeset-bot bot commented Aug 19, 2025

⚠️ No Changeset found

Latest commit: f75c0e4

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

coderabbitai bot commented Aug 19, 2025

Walkthrough

Dependency updates in package.json, including replacing unrs-resolver with oxc-resolver. Node resolver code updated to import from oxc-resolver with unchanged runtime flow and API. One utility function now has an explicit return type. A patch file’s metadata index updated without content changes.

Changes

Cohort / File(s) Summary of edits
Dependencies & metadata
package.json
Bumped multiple dependencies/devDependencies; removed unrs-resolver, added oxc-resolver; added some @typescript-eslint packages; updated resolutions; no functional code in this file.
Resolver migration
src/node-resolver.ts
Switched imports from unrs-resolver to oxc-resolver (ResolverFactory, options). Resolution logic and exported API remain the same.
Scope typing
src/utils/declared-scope.ts
Added type import ScopeType; annotated declaredScope to return `ScopeType
Patch metadata
patches/@swc-node+jest+1.9.1.patch
Updated patch index metadata only; no changes to patched code contents.

Sequence Diagram(s)

sequenceDiagram
  autonumber
  actor L as Linter/Rule
  participant R as createNodeResolver
  participant O as oxc-resolver (sync)
  note over L,R: New resolver backend integration
  L->>R: resolve(request, importer)
  alt built-in or data: URI
    R-->>L: short-circuit (found: false/path unchanged)
  else
    R->>O: sync resolve(request, importer, options)
    O-->>R: resolved path or error
    R-->>L: result (found/path) with errors swallowed on failure
  end
Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Poem

I twitch my whiskers at resolve and scope,
A hop from unrs to oxc—smooth as soap.
Types now declare where they intend,
Dependencies trimmed, on we wend.
Patch whispers, “no code to tweak.”
Carrot-commit made this week. 🥕✨

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch chore/deps

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

codacy-production bot commented Aug 19, 2025

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation Diff coverage
+0.00% (target: -1.00%)
Coverage variation details
Coverable lines Covered lines Coverage
Common ancestor commit (27b175f) 3722 3561 95.67%
Head commit (f75c0e4) 3722 (+0) 3561 (+0) 95.67% (+0.00%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details
Coverable lines Covered lines Diff coverage
Pull request (#422) 0 0 ∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

Copy link

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Copy link

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

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Added@​rolldown/​binding-android-arm64@​1.0.0-beta.33831003796100
Added@​rolldown/​binding-darwin-arm64@​1.0.0-beta.33961003798100
Added@​rolldown/​binding-darwin-x64@​1.0.0-beta.33891003798100
Added@​rolldown/​binding-freebsd-x64@​1.0.0-beta.33861003798100
Added@​rolldown/​binding-linux-arm-gnueabihf@​1.0.0-beta.33871003798100
Added@​rolldown/​binding-linux-arm64-gnu@​1.0.0-beta.33951003798100
Added@​rolldown/​binding-linux-arm64-musl@​1.0.0-beta.33951003798100
Added@​rolldown/​binding-linux-x64-gnu@​1.0.0-beta.331001003798100
Added@​rolldown/​binding-linux-x64-musl@​1.0.0-beta.331001003798100
Added@​rolldown/​binding-openharmony-arm64@​1.0.0-beta.33851003791100
Added@​rolldown/​binding-win32-arm64-msvc@​1.0.0-beta.33871003798100
Added@​rolldown/​binding-win32-ia32-msvc@​1.0.0-beta.33861003798100
Added@​rolldown/​binding-win32-x64-msvc@​1.0.0-beta.33951003798100
Added@​oxc-resolver/​binding-android-arm-eabi@​11.6.1991003785100
Added@​oxc-resolver/​binding-android-arm64@​11.6.1991003785100
Added@​oxc-resolver/​binding-linux-arm-musleabihf@​11.6.1991003785100
Added@​oxc-resolver/​binding-linux-ppc64-gnu@​11.6.1991003785100
Added@​oxc-resolver/​binding-linux-riscv64-musl@​11.6.1991003785100
Added@​oxc-resolver/​binding-win32-ia32-msvc@​11.6.1991003785100
Updated@​unrs/​resolver-binding-android-arm-eabi@​1.9.2 ⏵ 1.11.11001003786 -3100
Updated@​unrs/​resolver-binding-android-arm64@​1.9.2 ⏵ 1.11.11001003786 -3100
Updated@​unrs/​resolver-binding-darwin-arm64@​1.9.2 ⏵ 1.11.11001003791 -4100
Updated@​unrs/​resolver-binding-darwin-x64@​1.9.2 ⏵ 1.11.11001003791 -4100
Updated@​unrs/​resolver-binding-freebsd-x64@​1.9.2 ⏵ 1.11.11001003791 -4100
Updated@​unrs/​resolver-binding-linux-arm-gnueabihf@​1.9.2 ⏵ 1.11.11001003791 -4100
Updated@​unrs/​resolver-binding-linux-arm-musleabihf@​1.9.2 ⏵ 1.11.11001003791 -4100
Updated@​unrs/​resolver-binding-linux-arm64-gnu@​1.9.2 ⏵ 1.11.11001003791 -4100
Updated@​unrs/​resolver-binding-linux-arm64-musl@​1.9.2 ⏵ 1.11.11001003791 -4100
Updated@​unrs/​resolver-binding-linux-ppc64-gnu@​1.9.2 ⏵ 1.11.11001003791 -4100
Updated@​unrs/​resolver-binding-linux-riscv64-gnu@​1.9.2 ⏵ 1.11.11001003791 -4100
Updated@​unrs/​resolver-binding-linux-riscv64-musl@​1.9.2 ⏵ 1.11.11001003790 -4100
Updated@​unrs/​resolver-binding-linux-s390x-gnu@​1.9.2 ⏵ 1.11.11001003791 -4100
Updated@​unrs/​resolver-binding-linux-x64-gnu@​1.9.2 ⏵ 1.11.11001003791 -2100
See 270 more rows in the dashboard

View full report

Copy link

codecov bot commented Aug 19, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 96.10%. Comparing base (27b175f) to head (f75c0e4).

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #422   +/-   ##
=======================================
  Coverage   96.10%   96.10%           
=======================================
  Files          96       96           
  Lines        4952     4952           
  Branches     1837     1860   +23     
=======================================
  Hits         4759     4759           
  Misses        192      192           
  Partials        1        1           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link

@ellipsis-dev ellipsis-dev bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Important

Looks good to me! 👍

Reviewed everything up to f75c0e4 in 44 seconds. Click for details.
  • Reviewed 162 lines of code in 3 files
  • Skipped 2 files when reviewing.
  • Skipped posting 3 draft comments. View those below.
  • Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.
1. package.json:77
  • Draft comment:
    Migrated dependency: removal of 'unrs-resolver' and addition of 'oxc-resolver'. Ensure the new package’s API is fully compatible.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is about a dependency change, specifically the removal of one package and the addition of another. The comment asks to ensure API compatibility, which is not allowed according to the rules. The rules state not to comment on dependency changes or ask the author to ensure compatibility.
2. src/node-resolver.ts:4
  • Draft comment:
    Verify that 'oxc-resolver' exposes a compatible ResolverFactory and that 'resolver.sync' behaves as expected.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is asking the PR author to verify the behavior of 'oxc-resolver' and 'resolver.sync', which is against the rules as it asks for confirmation of intended behavior.
3. src/utils/declared-scope.ts:10
  • Draft comment:
    Explicit return type 'ScopeType | undefined' improves clarity. Confirm this matches all expected outcomes.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 50% <= threshold 50% The comment suggests an improvement by making the return type explicit, which is a valid suggestion. However, it also asks the author to confirm that this matches all expected outcomes, which violates the rule against asking for confirmation. The suggestion itself is useful, but the request for confirmation is not allowed.

Workflow ID: wflow_UYR14YjSC75jyLRb

You can customize Ellipsis by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.

Copy link

pkg-pr-new bot commented Aug 19, 2025

Open in StackBlitz

npm i https://pkg.pr.new/eslint-plugin-import-x@422

commit: f75c0e4

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
src/node-resolver.ts (2)

28-31: Optionally handle file:// specifiers

Node supports file URLs; short-circuiting them avoids handing off to the resolver and improves correctness for such imports.

Apply:

 import { isBuiltin } from 'node:module'
 import path from 'node:path'
+import { fileURLToPath } from 'node:url'

 ...
       if (isBuiltin(modulePath) || modulePath.startsWith('data:')) {
         return { found: true, path: null }
       }
+
+      if (modulePath.startsWith('file://')) {
+        try {
+          return { found: true, path: fileURLToPath(modulePath) }
+        } catch {
+          // fall through to resolver
+        }
+      }

32-40: Swallowed resolve errors — consider debug logging

Silent catch is fine for normal operation, but adding a guarded debug log can help diagnose resolution edge cases without impacting users.

-      } catch {
-        //
-      }
+      } catch (e) {
+        // eslint-disable-next-line no-empty
+        if (process.env.DEBUG?.includes('eslint-plugin-import-x')) {
+          // Lazy require to avoid adding hard dep on debug
+          // eslint-disable-next-line @typescript-eslint/no-var-requires
+          const dbg = require('node:console'); // or integrate 'debug' if already in deps
+          dbg.error?.('[import-x:node] resolve error:', e, { modulePath, sourceFile })
+        }
+      }
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 27b175f and f75c0e4.

⛔ Files ignored due to path filters (1)
  • yarn.lock is excluded by !**/yarn.lock, !**/*.lock
📒 Files selected for processing (4)
  • package.json (4 hunks)
  • patches/@swc-node+jest+1.9.1.patch (1 hunks)
  • src/node-resolver.ts (1 hunks)
  • src/utils/declared-scope.ts (2 hunks)
🧰 Additional context used
🧠 Learnings (3)
📚 Learning: 2025-03-30T14:44:11.779Z
Learnt from: SukkaW
PR: un-ts/eslint-plugin-import-x#272
File: src/utils/resolve.ts:0-0
Timestamp: 2025-03-30T14:44:11.779Z
Learning: In eslint-plugin-import-x's node resolver, the `modules` parameter of `createNodeResolver` function accepts both string and string array types, making it flexible when passing values like `moduleDirectory`.

Applied to files:

  • src/node-resolver.ts
📚 Learning: 2025-03-30T09:06:59.006Z
Learnt from: JounQin
PR: un-ts/eslint-plugin-import-x#271
File: test/rules/no-unused-modules.spec.ts:1528-1532
Timestamp: 2025-03-30T09:06:59.006Z
Learning: The import from 'eslint8.56/use-at-your-own-risk' has incorrect TypeScript types but works correctly at runtime, which is properly handled with a `ts-expect-error` comment.

Applied to files:

  • package.json
📚 Learning: 2025-06-18T12:49:41.795Z
Learnt from: JounQin
PR: un-ts/eslint-plugin-import-x#385
File: src/rules/prefer-namespace-import.ts:0-0
Timestamp: 2025-06-18T12:49:41.795Z
Learning: The eslint-plugin-import-x project requires Node versions `^18.18.0 || ^20.9.0 || >=21.1.0` as specified in package.json, so modern JavaScript features like String.prototype.at() are safe to use.

Applied to files:

  • package.json
🧬 Code Graph Analysis (2)
src/utils/declared-scope.ts (1)
src/types.ts (1)
  • RuleContext (69-78)
package.json (1)
test/core/export-map.spec.ts (2)
  • fakeContext (13-486)
  • espreeContext (292-334)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (190)
  • GitHub Check: Codacy Static Code Analysis
  • GitHub Check: Lint and Test with Node.js 20 and ESLint 9 on windows-latest
  • GitHub Check: Lint and Test with Node.js 20 and ESLint 8 on windows-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 8 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 9 on windows-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 8.56 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 8 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 9 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 20 and ESLint 8 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 8.56 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 9 on macos-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 9 on macos-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 8 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 8 on windows-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 9 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 8.56 on windows-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 9 on windows-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 8.56 on windows-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 9 on macos-latest
  • GitHub Check: Codacy Static Code Analysis
  • GitHub Check: Lint and Test with Node.js 20 and ESLint 9 on windows-latest
  • GitHub Check: Lint and Test with Node.js 20 and ESLint 8 on windows-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 8 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 9 on windows-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 8.56 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 8 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 9 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 20 and ESLint 8 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 8.56 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 9 on macos-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 9 on macos-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 8 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 8 on windows-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 9 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 8.56 on windows-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 9 on windows-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 8.56 on windows-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 9 on macos-latest
  • GitHub Check: Codacy Static Code Analysis
  • GitHub Check: Lint and Test with Node.js 20 and ESLint 9 on windows-latest
  • GitHub Check: Lint and Test with Node.js 20 and ESLint 8 on windows-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 8 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 9 on windows-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 8.56 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 8 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 9 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 20 and ESLint 8 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 8.56 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 9 on macos-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 9 on macos-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 8 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 8 on windows-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 9 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 8.56 on windows-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 9 on windows-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 8.56 on windows-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 9 on macos-latest
  • GitHub Check: Codacy Static Code Analysis
  • GitHub Check: Lint and Test with Node.js 20 and ESLint 9 on windows-latest
  • GitHub Check: Lint and Test with Node.js 20 and ESLint 8 on windows-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 8 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 9 on windows-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 8.56 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 8 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 9 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 20 and ESLint 8 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 8.56 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 9 on macos-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 9 on macos-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 8 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 8 on windows-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 9 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 8.56 on windows-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 9 on windows-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 8.56 on windows-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 9 on macos-latest
  • GitHub Check: Codacy Static Code Analysis
  • GitHub Check: Lint and Test with Node.js 20 and ESLint 9 on windows-latest
  • GitHub Check: Lint and Test with Node.js 20 and ESLint 8 on windows-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 8 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 9 on windows-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 8.56 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 8 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 9 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 20 and ESLint 8 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 8.56 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 9 on macos-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 9 on macos-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 8 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 8 on windows-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 9 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 8.56 on windows-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 9 on windows-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 8.56 on windows-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 9 on macos-latest
  • GitHub Check: Codacy Static Code Analysis
  • GitHub Check: Lint and Test with Node.js 20 and ESLint 9 on windows-latest
  • GitHub Check: Lint and Test with Node.js 20 and ESLint 8 on windows-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 8 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 9 on windows-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 8.56 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 8 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 9 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 20 and ESLint 8 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 8.56 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 9 on macos-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 9 on macos-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 8 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 8 on windows-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 9 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 8.56 on windows-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 9 on windows-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 8.56 on windows-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 9 on macos-latest
  • GitHub Check: Codacy Static Code Analysis
  • GitHub Check: Lint and Test with Node.js 20 and ESLint 9 on windows-latest
  • GitHub Check: Lint and Test with Node.js 20 and ESLint 8 on windows-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 8 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 9 on windows-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 8.56 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 8 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 9 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 20 and ESLint 8 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 8.56 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 9 on macos-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 9 on macos-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 8 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 8 on windows-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 9 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 8.56 on windows-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 9 on windows-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 8.56 on windows-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 9 on macos-latest
  • GitHub Check: Codacy Static Code Analysis
  • GitHub Check: Lint and Test with Node.js 20 and ESLint 9 on windows-latest
  • GitHub Check: Lint and Test with Node.js 20 and ESLint 8 on windows-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 8 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 9 on windows-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 8.56 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 8 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 9 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 20 and ESLint 8 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 8.56 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 9 on macos-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 9 on macos-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 8 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 8 on windows-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 9 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 8.56 on windows-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 9 on windows-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 8.56 on windows-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 9 on macos-latest
  • GitHub Check: Codacy Static Code Analysis
  • GitHub Check: Lint and Test with Node.js 20 and ESLint 9 on windows-latest
  • GitHub Check: Lint and Test with Node.js 20 and ESLint 8 on windows-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 8 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 9 on windows-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 8.56 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 8 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 9 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 20 and ESLint 8 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 8.56 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 9 on macos-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 9 on macos-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 8 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 8 on windows-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 9 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 8.56 on windows-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 9 on windows-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 8.56 on windows-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 9 on macos-latest
  • GitHub Check: Codacy Static Code Analysis
  • GitHub Check: Lint and Test with Node.js 20 and ESLint 9 on windows-latest
  • GitHub Check: Lint and Test with Node.js 20 and ESLint 8 on windows-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 8 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 9 on windows-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 8.56 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 8 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 9 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 20 and ESLint 8 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 8.56 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 9 on macos-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 9 on macos-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 8 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 8 on windows-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 9 on ubuntu-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 8.56 on windows-latest
  • GitHub Check: Lint and Test with Node.js 22 and ESLint 9 on windows-latest
  • GitHub Check: Lint and Test with Node.js 18 and ESLint 8.56 on windows-latest
  • GitHub Check: Lint and Test with Node.js 24.5 and ESLint 9 on macos-latest
🔇 Additional comments (7)
patches/@swc-node+jest+1.9.1.patch (1)

2-18: Patch metadata updated — please verify it still applies cleanly with @swc-node/jest 1.9.1

We’ve rebased the patch to use the new upstream index hash (4060446); the functional changes (expanded file/glob regex and returning {code: src}) remain the same. Please confirm:

• Location: patches/@swc-node+jest+1.9.1.patch (targets node_modules/@swc-node/jest/lib/index.js)
• Steps to verify:

  1. Run yarn install && yarn prepare
  2. Ensure you see “Applying patches…” with no errors

(Optional) Diff for quick reference:

index 9a2fc9d..4060446 100644
--- a/node_modules/@swc-node/jest/lib/index.js
+++ b/node_modules/@swc-node/jest/lib/index.js
@@ -17,13 +17,13 @@
-        if (/\.(tsx?|jsx?|mjs)$/.test(path)) {
+        if (/\.([cm]ts|tsx?|[cm]js|jsx?)$/.test(path)) {
…
-        return src;
+        return { code: src };
src/node-resolver.ts (2)

4-6: API migration to oxc-resolver looks correct

Import switch and types align with the expected API surface; the rest of the resolver flow remains intact. Good job keeping the public resolver contract unchanged.


10-14: Confirm modules option parity
NapiResolveOptions in oxc-resolver@11.6.1 declares

modules?: string | string[]

and our createNodeResolver({ …restOptions }) spreads it directly into ResolverFactory, preserving the original union and default behaviour. No changes needed.

src/utils/declared-scope.ts (1)

1-14: Stronger typing for declaredScope return type

Explicit ScopeType | undefined improves downstream safety with no runtime changes. LGTM.

package.json (3)

78-87: Dependency swap to oxc-resolver aligns with code changes

Replacing unrs-resolver with oxc-resolver@^11.6.1 matches the migrated resolver code. No issues spotted.


64-76: Peer deps remain compatible with updated toolchain

ESLint ranges and @typescript-eslint utils alignment look fine given the devDep bumps. No action needed.


96-112: Verify @swc-node/jest patch for proper regex coverage

I confirmed the patch returns { code: src } at line 17, but the expanded file-extension regex (/\.(?:[cm]ts|tsx?|[cm]js|jsx?)$/) wasn’t found in the patch. Please ensure that:

  • The transform regex in patches/@swc-node+jest+1.9.1.patch covers all relevant extensions: .cts, .mts, .tsx, .jsx, etc.
  • The patch still returns an object with { code } rather than a raw string.

Once updated, rerun:

yarn test -w 1

to validate that Jest transforms behave as expected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant