Skip to content

Conversation

@JounQin
Copy link
Member

@JounQin JounQin commented Apr 6, 2025

🤖 New release

  • unrs_resolver: 1.3.3 -> 1.4.0 (✓ API compatible changes)
Changelog


This PR was generated with release-plz.

Summary by CodeRabbit

  • New Features
    • Released version 1.4.0 with significant updates, including enhanced support for various configurations and improvements to the FileSystem API.
  • Bug Fixes
    • Addressed issues with handling queries and fragments in package exports and imports, ensuring better compatibility with Windows paths.
  • Documentation
    • Updated the CHANGELOG with detailed notes on version 1.4.0 and clarified existing documentation.
  • Refactor
    • Improved code quality and removed deprecated calls for enhanced performance.

@JounQin JounQin force-pushed the release-plz-2025-04-06T18-57-39Z branch from 7dcb630 to e099899 Compare April 6, 2025 18:57
@coderabbitai
Copy link

coderabbitai bot commented Apr 6, 2025

Walkthrough

This pull request updates the project to version 1.4.0. The changelog now includes a detailed section for version 1.4.0 with notes on new features, bug fixes, performance improvements, documentation adjustments, refactoring, and testing changes. Notable modifications include resolving emitDecoratorMetadata, adding mimalloc, transitioning to Rust Edition 2024, and updates to the FileSystem API. Additionally, the package versions in both Cargo.toml and npm/package.json have been updated from 1.3.3 to 1.4.0.

Changes

File(s) Change Summary
CHANGELOG.md Added a new version section for 1.4.0 with details on features, bug fixes, performance improvements, documentation, refactoring, and testing.
Cargo.toml, npm/package.json Updated package version from 1.3.3 to 1.4.0, reflecting minor updates and improvements in functionality.
napi/index.js Modified isMuslFromReport function to change how the report variable is initialized and to include an additional property setting for excludeNetwork.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant FS_API as FileSystem API
    participant System as Underlying System

    Client->>FS_API: Initiate file operation
    FS_API->>System: Process updated API call
    System-->>FS_API: Return operation result
    FS_API-->>Client: Deliver result
Loading

Poem

Hop, hop, I'm a coding bunny,
Leaping ‘round in version one-point-four—so funny!
With mimalloc and a file system twist,
Bugs vanish away, they simply can't resist.
I nibble on code with joy and delight,
Celebrating changes from morning to night!
🐰💻 Happy coding, under the moonlight!


🪧 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.
    • Generate unit testing code for this file.
    • 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. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • 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 src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai plan to trigger planning for file edits and PR creation.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

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

Documentation and Community

  • 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.

@codecov
Copy link

codecov bot commented Apr 6, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.75%. Comparing base (fe820ba) to head (7032569).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #50   +/-   ##
=======================================
  Coverage   92.75%   92.75%           
=======================================
  Files          13       13           
  Lines        2842     2842           
=======================================
  Hits         2636     2636           
  Misses        206      206           

☔ 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.

@codspeed-hq
Copy link

codspeed-hq bot commented Apr 6, 2025

CodSpeed Performance Report

Merging #50 will not alter performance

Comparing release-plz-2025-04-06T18-57-39Z (7032569) with main (fe820ba)

Summary

✅ 3 untouched benchmarks

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 (1)
CHANGELOG.md (1)

30-32: Typographical Correction

There appears to be a typographical error in the bug fixes section: "pacakge.json" should be corrected to "package.json" for clarity.

Apply this diff to correct the typo:

- - handle query and fragment in pacakge.json `exports` and `imports` field ([#443](https://github.com/unrs/unrs-resolver/pull/443))
+ - handle query and fragment in package.json `exports` and `imports` field ([#443](https://github.com/unrs/unrs-resolver/pull/443))
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between bc0ccf0 and e099899.

⛔ Files ignored due to path filters (1)
  • Cargo.lock is excluded by !**/*.lock
📒 Files selected for processing (3)
  • CHANGELOG.md (1 hunks)
  • Cargo.toml (1 hunks)
  • npm/package.json (1 hunks)
🧰 Additional context used
🪛 LanguageTool
CHANGELOG.md

[uncategorized] ~63-~63: This verb may not be in the correct form. Consider using a different form for this context.
Context: ...nt on Context::missing_dependencies - mention extension must start with a . in `wit...

(AI_EN_LECTOR_REPLACEMENT_VERB_FORM)


[grammar] ~77-~77: “Windows” (operating system by Microsoft) is a proper noun and needs to be capitalized.
Context: ...### Testing - fix warning on windows - fix symlink test init on windows ([#3...

(A_WINDOWS)

⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Benchmark
🔇 Additional comments (3)
Cargo.toml (1)

7-7: Version Update Confirmed

The package version has been updated from "1.3.3" to "2.0.0", in line with the release objectives. Ensure that any related API compatibility tests have been executed.

npm/package.json (1)

3-3: Version Update Consistency

The npm package version is correctly updated to "2.0.0". This change aligns with the updates in Cargo.toml and supports the release of v2.0.0.

CHANGELOG.md (1)

9-44: Comprehensive Changelog for v2.0.0

The changelog entry for version 2.0.0 is well detailed and follows the Keep a Changelog format. It clearly lists new features, bug fixes, performance improvements, refactorings, and testing adjustments. Please verify that all the noted entries accurately reflect the implemented changes.

@JounQin JounQin force-pushed the release-plz-2025-04-06T18-57-39Z branch from e099899 to 69802c5 Compare April 6, 2025 19:18
@JounQin JounQin force-pushed the release-plz-2025-04-06T18-57-39Z branch from 69802c5 to e26509e Compare April 6, 2025 19:18
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 (4)
CHANGELOG.md (4)

11-29: Comprehensive Features Section
The Features section for version 2.0.0 is detailed and well organized. Note that several items are marked as [breaking]. Since the PR objective mentions API compatibility, please confirm that these breaking changes do not unintentionally affect the public API. Additionally, verify that all feature links (e.g. [#439], [#402], etc.) are valid.


30-44: Bug Fixes Details and Minor Typo
The Bug Fixes section is thorough. However, on line 32 the text contains a typo:

  • Current: “handle query and fragment in pacakge.json exports and imports field”
  • Suggested: “handle query and fragment in package.json exports and imports field”
    Please correct the typo and verify that all other bug fix entries accurately reflect the resolved issues.
- - handle query and fragment in pacakge.json `exports` and `imports` field ([#443](https://github.com/unrs/unrs-resolver/pull/443))
+ - handle query and fragment in package.json `exports` and `imports` field ([#443](https://github.com/unrs/unrs-resolver/pull/443))

45-59: Performance Section Review and Typo Correction
The Performance section presents multiple improvements. On line 58, the phrase “avoid usless syscall” appears to have a typo. It is recommended to change “usless” to “useless” for clarity.

- - use custom canonicalize impl to avoid usless syscall ([#220](https://github.com/unrs/unrs-resolver/pull/220))
+ - use custom canonicalize impl to avoid useless syscall ([#220](https://github.com/unrs/unrs-resolver/pull/220))

75-79: Testing Section: Capitalization Consistency
The Testing section includes two entries referring to “windows.” For clarity and consistency (as noted by static analysis), please capitalize “Windows” in both cases.

- - fix warning on windows
+ - fix warning on Windows

- - fix symlink test init on windows ([#307](https://github.com/unrs/unrs-resolver/pull/307))
+ - fix symlink test init on Windows ([#307](https://github.com/unrs/unrs-resolver/pull/307))
🧰 Tools
🪛 LanguageTool

[grammar] ~77-~77: “Windows” (operating system by Microsoft) is a proper noun and needs to be capitalized.
Context: ...### Testing - fix warning on windows - fix symlink test init on windows ([#3...

(A_WINDOWS)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between e099899 and e26509e.

⛔ Files ignored due to path filters (1)
  • Cargo.lock is excluded by !**/*.lock
📒 Files selected for processing (3)
  • CHANGELOG.md (1 hunks)
  • Cargo.toml (1 hunks)
  • npm/package.json (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (2)
  • Cargo.toml
  • npm/package.json
🧰 Additional context used
🪛 LanguageTool
CHANGELOG.md

[uncategorized] ~63-~63: This verb may not be in the correct form. Consider using a different form for this context.
Context: ...nt on Context::missing_dependencies - mention extension must start with a . in `wit...

(AI_EN_LECTOR_REPLACEMENT_VERB_FORM)


[grammar] ~77-~77: “Windows” (operating system by Microsoft) is a proper noun and needs to be capitalized.
Context: ...### Testing - fix warning on windows - fix symlink test init on windows ([#3...

(A_WINDOWS)

🔇 Additional comments (3)
CHANGELOG.md (3)

9-10: New Version Header Added
The new header for version 2.0.0 is clearly introduced with a compare link and release date. Please double-check that the release date (2025-04-06) and link to the comparison (v1.3.3...v2.0.0) match the project’s release timeline.


60-65: Documentation Section Confirmation
The Documentation section is concise and clear. The note “mention extension must start with a . in with_extension” is important and correctly included. No changes are needed here, but please ensure that any similar notes elsewhere (e.g. in test cases or user guides) follow consistent formatting.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~63-~63: This verb may not be in the correct form. Consider using a different form for this context.
Context: ...nt on Context::missing_dependencies - mention extension must start with a . in `wit...

(AI_EN_LECTOR_REPLACEMENT_VERB_FORM)


66-74: Refactor Section Verification
The Refactor section is well maintained. The removal of deprecated calls and the clean-up efforts (e.g. replacing UnsafeCell with RefCell and running clippy fixes) contribute to improved code hygiene. No issues found here.

@JounQin JounQin changed the title chore: release v2.0.0 chore: release v1.4.0 Apr 6, 2025
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: 1

🧹 Nitpick comments (2)
CHANGELOG.md (2)

32-33: Typo in changelog entry.

There's a typographical error in the bug fix entry - "pacakge.json" should be "package.json".

-handle query and fragment in pacakge.json `exports` and `imports` field ([#443](https://github.com/oxc-project/oxc-resolver/pull/443))
+handle query and fragment in package.json `exports` and `imports` field ([#443](https://github.com/oxc-project/oxc-resolver/pull/443))

62-64: Capitalize "Windows" in testing section.

The operating system name "Windows" should be capitalized.

-fix warning on windows
-fix symlink test init on windows ([#307](https://github.com/oxc-project/oxc-resolver/pull/307))
+fix warning on Windows
+fix symlink test init on Windows ([#307](https://github.com/oxc-project/oxc-resolver/pull/307))
🧰 Tools
🪛 LanguageTool

[uncategorized] ~63-~63: This verb may not be in the correct form. Consider using a different form for this context.
Context: ...nt on Context::missing_dependencies - mention extension must start with a . in `wit...

(AI_EN_LECTOR_REPLACEMENT_VERB_FORM)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between e26509e and 00f9825.

⛔ Files ignored due to path filters (1)
  • Cargo.lock is excluded by !**/*.lock
📒 Files selected for processing (4)
  • CHANGELOG.md (1 hunks)
  • Cargo.toml (1 hunks)
  • napi/index.js (1 hunks)
  • npm/package.json (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (2)
  • npm/package.json
  • Cargo.toml
🧰 Additional context used
🪛 LanguageTool
CHANGELOG.md

[uncategorized] ~63-~63: This verb may not be in the correct form. Consider using a different form for this context.
Context: ...nt on Context::missing_dependencies - mention extension must start with a . in `wit...

(AI_EN_LECTOR_REPLACEMENT_VERB_FORM)


[grammar] ~77-~77: “Windows” (operating system by Microsoft) is a proper noun and needs to be capitalized.
Context: ...### Testing - fix warning on windows - fix symlink test init on windows ([#3...

(A_WINDOWS)

⏰ Context from checks skipped due to timeout of 90000ms (7)
  • GitHub Check: Lint
  • GitHub Check: Test wasi target
  • GitHub Check: Test (ubuntu-latest)
  • GitHub Check: Test (windows-latest)
  • GitHub Check: Check Wasm
  • GitHub Check: Test (macos-14)
  • GitHub Check: Benchmark
🔇 Additional comments (3)
napi/index.js (1)

37-42: Improved robustness for process report handling.

The changes to isMuslFromReport function add defensive programming with optional chaining, exclude unnecessary network information, and clarify the initialization flow.

These improvements help prevent potential errors when process.report is undefined and optimize the report generation by excluding network information that isn't needed for musl detection.

CHANGELOG.md (2)

13-29: Comprehensive feature changes noted in changelog.

The feature section effectively captures significant changes including breaking changes and important updates like Rust Edition 2024, mimalloc integration, and FileSystem API changes.

These detailed release notes will help users understand the impact of updating to the new version.


47-59: Well-documented performance improvements.

The changelog provides a thorough list of performance optimizations including memory allocation improvements and path resolution optimizations.

Users will appreciate understanding the performance benefits they'll gain with this update.

@JounQin JounQin force-pushed the release-plz-2025-04-06T18-57-39Z branch from 00f9825 to 7032569 Compare April 6, 2025 19:26
@sonarqubecloud
Copy link

sonarqubecloud bot commented Apr 6, 2025

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 (1)
CHANGELOG.md (1)

60-65: Address Documentation Grammar and Accuracy
The Documentation section includes a fix for an incorrect comment on Context::missing_dependencies and clarifies that extensions must start with a dot. A static analysis hint noted a potential grammatical issue in this comment. It is advisable to review and, if needed, refine the phrasing for better clarity and correctness.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~63-~63: This verb may not be in the correct form. Consider using a different form for this context.
Context: ...nt on Context::missing_dependencies - mention extension must start with a . in `wit...

(AI_EN_LECTOR_REPLACEMENT_VERB_FORM)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 00f9825 and 7032569.

⛔ Files ignored due to path filters (1)
  • Cargo.lock is excluded by !**/*.lock
📒 Files selected for processing (4)
  • CHANGELOG.md (1 hunks)
  • Cargo.toml (1 hunks)
  • napi/index.js (1 hunks)
  • npm/package.json (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (3)
  • npm/package.json
  • Cargo.toml
  • napi/index.js
🧰 Additional context used
🪛 LanguageTool
CHANGELOG.md

[uncategorized] ~63-~63: This verb may not be in the correct form. Consider using a different form for this context.
Context: ...nt on Context::missing_dependencies - mention extension must start with a . in `wit...

(AI_EN_LECTOR_REPLACEMENT_VERB_FORM)

🔇 Additional comments (6)
CHANGELOG.md (6)

9-10: Confirm Version Consistency
The changelog entry for version 1.4.0 (dated 2025-04-06) is formatted correctly and appears aligned with the PR objectives. However, note that a previous review comment raised a potential version inconsistency (mentioning v2.0.0). Please double-check that 1.4.0 is indeed the intended release version and update any conflicting documentation if needed.


11-29: Review Features Section Clarity and Completeness
The Features section for version 1.4.0 is comprehensive and details new functionalities and breaking changes (e.g., changes to Rust Edition, the addition of mimalloc, and updates to the tsconfig options). Please verify that each bullet accurately reflects the intended changes and that any breaking change is documented in the broader API documentation.


30-44: Validate Bug Fixes Documentation
The Bug Fixes section clearly lists fixes such as handling queries in package.json fields, normalizing Windows paths, and correcting module resolution issues. Ensure that these fixes have been cross-referenced with the corresponding pull requests and bug reports for full clarity.


45-59: Assess Performance Improvements
The Performance section outlines several optimizations (e.g., using a thread-local path, reducing memory allocations, and optimizing hash calculations). It would be beneficial to confirm that these changes have been benchmarked and validated across supported platforms.


66-74: Review Refactor Improvements
The Refactor section lists several improvements (such as removing deprecated calls, replacing UnsafeCell with RefCell, and cleaning up elided lifetimes). These changes seem well organized and help improve code quality. No further action is required unless additional internal consistency checks are needed.


75-78: Verify Testing Fixes on Windows
The Testing section documents fixes for Windows warnings and issues with symlink test initialization. Please confirm that these changes result in passing test suites across all targeted platforms.

@JounQin JounQin merged commit 5c511b5 into main Apr 6, 2025
19 checks passed
@JounQin JounQin deleted the release-plz-2025-04-06T18-57-39Z branch April 6, 2025 19:31
@coderabbitai coderabbitai bot mentioned this pull request Apr 7, 2025
JounQin pushed a commit that referenced this pull request Jun 10, 2025
## 🤖 New release

* `oxc_resolver`: 8.0.0 -> 9.0.0 (⚠ API breaking changes)
* `oxc_napi_resolver`: 8.0.0

### ⚠ `oxc_resolver` breaking changes

```text
--- failure constructible_struct_adds_field: externally-constructible struct adds field ---

Description:
A pub struct constructible with a struct literal has a new pub field. Existing struct literals must be updated to include the new field.
        ref: https://doc.rust-lang.org/reference/expressions/struct-expr.html
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.40.0/src/lints/constructible_struct_adds_field.ron

Failed in:
  field ResolveOptions.modules in /tmp/.tmpTBvVad/oxc-resolver/src/options.rs:114

--- failure trait_method_added: pub trait method added ---

Description:
A non-sealed public trait added a new method without a default implementation, which breaks downstream implementations of the trait
        ref: https://doc.rust-lang.org/cargo/reference/semver.html#trait-new-item-no-default
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.40.0/src/lints/trait_method_added.ron

Failed in:
  trait method oxc_resolver::CachedPath::module_directory in file /tmp/.tmpTBvVad/oxc-resolver/src/cache.rs:69
  trait method oxc_resolver::CachedPath::cached_node_modules in file /tmp/.tmpTBvVad/oxc-resolver/src/cache.rs:76
```

<details><summary><i><b>Changelog</b></i></summary><p>

## `oxc_resolver`

<blockquote>

##
[9.0.0](oxc-project/oxc-resolver@oxc_resolver-v8.0.0...oxc_resolver-v9.0.0)
- 2025-05-09

### <!-- 1 -->Bug Fixes

- hash import does not need to load from node_modules
([#501](oxc-project/oxc-resolver#501))

### <!-- 7 -->Chore

- add `--tsconfig` to example
([#505](oxc-project/oxc-resolver#505))
- publish `oxc_napi_resolver`
([#496](oxc-project/oxc-resolver#496))
</blockquote>

## `oxc_napi_resolver`

<blockquote>

##
[8.0.0](https://github.com/oxc-project/oxc-resolver/releases/tag/oxc_napi_resolver-v8.0.0)
- 2025-05-09

### <!-- 0 -->Features

- *(napi)* add mimalloc
([#423](oxc-project/oxc-resolver#423))
- [**breaking**] Rust Edition 2024
([#402](oxc-project/oxc-resolver#402))
- expose `package_json_path`
([#376](oxc-project/oxc-resolver#376))
- *(napi)* expose module type info in ResolveResult
([#223](oxc-project/oxc-resolver#223))
- *(napi)* add tracing via `OXC_LOG:DEBUG`
([#202](oxc-project/oxc-resolver#202))
- *(napi)* add async API
([#191](oxc-project/oxc-resolver#191))
- add `imports_fields` option
([#138](oxc-project/oxc-resolver#138))
- add more builder functions for options
([#110](oxc-project/oxc-resolver#110))
- *(napi)* support wasi target
([#31](oxc-project/oxc-resolver#31))
- add file_dependencies and missing_dependencies API
([#50](oxc-project/oxc-resolver#50))
- *(napi)* expose cloneWithOptions and clearCache methods
([#40](oxc-project/oxc-resolver#40))
- *(napi)* update the doc and type for tsconfig references
([#24](oxc-project/oxc-resolver#24))
- *(napi)* add options
([#19](oxc-project/oxc-resolver#19))
- *(resolver)* add tracing-subscriber feature
([#904](https://github.com/oxc-project/oxc-resolver/pull/904))
- *(resolver)* tsconfig project references
([#862](https://github.com/oxc-project/oxc-resolver/pull/862))
- *(resolver)* add thiserror
([#847](https://github.com/oxc-project/oxc-resolver/pull/847))
- *(resolver)* implement nested alias field
([#795](oxc-project/oxc-resolver#795))
- *(resolver)* implement tsconfig-paths
([#750](oxc-project/oxc-resolver#750))
- *(resolver)* implement configurable `exports_fields` option
([#733](oxc-project/oxc-resolver#733))
- *(resolver)* implement `main_fields`
- *(resolver)* implement resolveToContext
([#694](oxc-project/oxc-resolver#694))
- *(resolver)* implement restrictions (path only)
([#693](oxc-project/oxc-resolver#693))
- *(resolver)* implement fully specified
([#687](oxc-project/oxc-resolver#687))
- *(resolver)* imports field
([#681](oxc-project/oxc-resolver#681))
- *(resolver)* finish most of exports field
([#674](oxc-project/oxc-resolver#674))
- *(resolver)* port the rest of the exports field tests
([#659](oxc-project/oxc-resolver#659))
- *(resolver)* implement symlinks
([#582](oxc-project/oxc-resolver#582))
- *(resolver)* complete query and fragment parsing
([#579](oxc-project/oxc-resolver#579))
- *(resolver)* add preferRelative and preferAbsolute
([#577](oxc-project/oxc-resolver#577))
- *(resolver)* implement roots
([#576](oxc-project/oxc-resolver#576))
- *(resolver)* implement fallback
([#572](oxc-project/oxc-resolver#572))
- *(resolver)* implement enforceExtension
([#566](oxc-project/oxc-resolver#566))
- *(resolver)* implement descriptionFiles option
([#565](oxc-project/oxc-resolver#565))
- *(resolver)* implement the basics of path alias
([#564](oxc-project/oxc-resolver#564))
- *(resolver)* accept different file system implementations
([#562](oxc-project/oxc-resolver#562))
- *(resolver)* implement browser field
([#561](oxc-project/oxc-resolver#561))
- *(resolver)* implement scoped packages
([#558](oxc-project/oxc-resolver#558))
- *(resolver)* port incorrect description file test
([#557](oxc-project/oxc-resolver#557))
- *(resolver)* implement extension_alias
([#556](oxc-project/oxc-resolver#556))
- *(resolver)* port resolve tests
([#555](oxc-project/oxc-resolver#555))
- *(resolver)* resolve extensions
([#549](oxc-project/oxc-resolver#549))
- *(resolver)* add resolver test fixtures
([#542](oxc-project/oxc-resolver#542))

### <!-- 1 -->Bug Fixes

- hash import does not need to load from node_modules
([#501](oxc-project/oxc-resolver#501))
- *(napi)* `new ResolverFactory()` options should be optional
([#256](oxc-project/oxc-resolver#256))
- *(napi)* update buggy NAPI-RS versions
([#225](oxc-project/oxc-resolver#225))
- canonicalize is not supported on wasi target
([#124](oxc-project/oxc-resolver#124))
- resolve "browser" field when "exports" is present
([#59](oxc-project/oxc-resolver#59))

### <!-- 4 -->Refactor

- [**breaking**] remove `description_files` option
([#488](oxc-project/oxc-resolver#488))
- [**breaking**] remove `modules` options
([#484](oxc-project/oxc-resolver#484))
- vitest ([#380](oxc-project/oxc-resolver#380))
- apply latest `cargo +nightly fmt`
([#281](oxc-project/oxc-resolver#281))
- selectively parse package_json fields instead of parsing everything
([#103](oxc-project/oxc-resolver#103))
- *(resolver)* clean up some code and tests
- *(resolver)* change internal funcs to non-pub by moving to unit tests
([#682](oxc-project/oxc-resolver#682))

### <!-- 7 -->Chore

- publish `oxc_napi_resolver`
([#496](oxc-project/oxc-resolver#496))
- *(napi)* make mimalloc optional to build
([#495](oxc-project/oxc-resolver#495))
- *(README)* add wasm usage example
- *(README)* crates.io badge use recent downloads
- *(napi)* auto download wasm binding on webcontainer
([#471](oxc-project/oxc-resolver#471))
- use root package.json for napi build
([#469](oxc-project/oxc-resolver#469))
- *(deps)* update github-actions
([#444](oxc-project/oxc-resolver#444))
- *(deps)* lock file maintenance npm packages
([#436](oxc-project/oxc-resolver#436))
- bump napi
([#404](oxc-project/oxc-resolver#404))
- *(deps)* lock file maintenance npm packages
([#391](oxc-project/oxc-resolver#391))
- *(deps)* lock file maintenance rust crates
([#390](oxc-project/oxc-resolver#390))
- *(README)* clarify Rust and node.js usages
- add dprint
([#326](oxc-project/oxc-resolver#326))
- *(deps)* update napi-rs to 3.0.0-alpha
- `cargo upgrade` && `pnpm upgrade`
- *(deps)* update napi-rs to 3.0.0-alpha
- update napi changes
- *(deps)* update rust crate napi-derive to 3.0.0-alpha
- *(deps)* update rust crate napi to 3.0.0-alpha
- *(deps)* update napi-rs to 2.16.8
- *(napi)* make napi binary smaller with minimal tracing features
([#213](oxc-project/oxc-resolver#213))
- *(napi)* remove tokio
([#212](oxc-project/oxc-resolver#212))
- document directory is an absolute path for `resolve(directory,
specifier)`
([#206](oxc-project/oxc-resolver#206))
- re-enable the wasi build
([#193](oxc-project/oxc-resolver#193))
- use pnpm workspace
([#182](oxc-project/oxc-resolver#182))
- *(deps)* update rust crates
([#176](oxc-project/oxc-resolver#176))
- *(napi)* update NAPI-RS cli version and binding template
([#111](oxc-project/oxc-resolver#111))
- update project github url
- *(deps)* update pnpm to v8.14.1
([#52](oxc-project/oxc-resolver#52))
- *(deps)* update pnpm to v8.14.0
([#48](oxc-project/oxc-resolver#48))
- *(deps)* update pnpm to v8.13.1
([#42](oxc-project/oxc-resolver#42))
- remove FIXME comments
- *(napi)* align `*Fields` user options with enhanced-resolve
([#35](oxc-project/oxc-resolver#35))
- *(deps)* update pnpm to v8.12.1
([#21](oxc-project/oxc-resolver#21))
- add some doc for napi TsconfigOptions
([#20](oxc-project/oxc-resolver#20))
- *(deps)* update pnpm to v8.12.0
([#18](oxc-project/oxc-resolver#18))
- *(README)* adding debugging command from Rspack
- *(deps)* update pnpm to v8.11.0
([#9](oxc-project/oxc-resolver#9))
- *(resolver)* remove tracing_subscriber
([#1362](https://github.com/oxc-project/oxc-resolver/pull/1362))
- *(resolver)* improve documentation
([#591](oxc-project/oxc-resolver#591))

### <!-- 8 -->CI

- check for napi .d.index changes
([#491](oxc-project/oxc-resolver#491))
- *(release-napi)* support `riscv64gc-unknown-linux-gnu` and
`s390x-unknown-linux-gnu`
([#451](oxc-project/oxc-resolver#451))
</blockquote>


</p></details>

---
This PR was generated with
[release-plz](https://github.com/release-plz/release-plz/).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants