Releases: web-infra-dev/rspack-resolver
v0.6.6
What's Changed
- fix: json parse error handle by @stormslowly in #124
- perf: pre-allocate path buffer for extension load by @stormslowly in #127
- chore: enable CI nodejs matrix by @stormslowly in #129
- chore: fix doc.rs build failure by @stormslowly in #130
corresponding npm package @rspack/resolver@0.2.5
Full Changelog: v0.6.5...v0.6.6
v0.6.5
What's Changed
- perf: use simd json for json parse by @stormslowly in #117
- feat: update pnp dependency version to 0.12.4 by @arcanis in #103
corresponding npm package @rspack/resolver@0.2.4
Full Changelog: v0.6.4...v0.6.5
v0.6.4
What's Changed
- feat: real path of symlink resolved file should be in file dependencies by @stormslowly in #108
- fix(windows): wrong file dependencies when specifier is posix style abs path by @stormslowly in #112
corresponding npm package @rspack/resolver@0.2.3
Full Changelog: v0.6.3...v0.6.4
v0.6.3
What's Changed
- feat(napi): async resolve by @CPunisher in #92
- fix(napi): align alias config type with enhance-resolver by @stormslowly in #100
corresponding npm package @rspack/resolver@0.2.2
Full Changelog: v0.6.2...v0.6.3
v0.6.2
What's Changed
- feat: support wasm by @CPunisher in #90
- fix: resolve security issues that are reported by dependabot by @stormslowly in #86
- chore: fix clippy warnings by @CPunisher in #88
- chore: fix clippy warnings by @CPunisher in #89
- chore: release by explicit commit not by workflow ref by @stormslowly in #87
New Contributors
- @CPunisher made their first contribution in #88
Full Changelog: v0.6.1...v0.6.2
v0.6.1
Hightlights
First of all, great thanks to @arcanis for helping us to upgrade pnp crate in #80. It will bring performance improvment to pnp enabled projects and smaller binding size of @rspack/resolver.
Now, crate rspack_resolver is publishing by trusted publishing feature of cretes.io. Besides, @rspack/resolver has been published by the Continuous Factor Authentication. Both of them are published in a security and trusted way.
What's Changed
-
feat: use crates.io trusted publishing by @stormslowly in #82
-
docs: add tsconfig config doc by @stormslowly in #77
-
docs: add basic npm usage and example code by @stormslowly in #78
-
chore: add tracing debug for pnp by @stormslowly in #83
-
chore: add prettier by @stormslowly in #84
Full Changelog: v0.6.0...v0.6.1
corresponding npm package @rspack/resolver@0.2.1
v0.6.0
‼️ Breaking Change
0.6.0 introduces a Breaking change with tsconfig's paths match, more detail please refer to #74.
If you want to seperate paths mathing in different typescript project, you can use the references to seperate paths match in different project. Reference Example.
What's Changed
- fix!: paths match align with tsconfig-paths-webpack-plugin by @stormslowly in #74
Full Changelog: v0.5.5...v0.6.0
corresponding npm package @rspack/resolver@0.2.0
v0.5.6
Highlight
⚡️ #69 improve resolving performance 5 times faster in yarn-pnp project.
Thank you ❤️ @elbywan @arcanis
What's Changed
- fix(pnp): cache the manifest by its own path by @elbywan in #69
- chore: update pnp-rs to 0.9.4 by @stormslowly in #70
- chore: add pnp resolve benchmark by @stormslowly in #71
New Contributors
Full Changelog: v0.5.5...v0.5.6
the @rspack/resolver@0.1.6 is using rspack_resolver@0.5.6
v0.5.5
What's Changed
- fix: restrictions with extensions by @SyMind in #66
- fix(pnp): full path resolved file found wrong description file by @stormslowly in #67
- chore: exclude benches pnpm lock file by @stormslowly in #64
- chore: release node binding by @stormslowly in #62
Now npm package @rspack/resolver is released, you can use rspack resolve in your NodeJS Project.
Full Changelog: v0.5.4...v0.5.5
v0.5.4
What's Changed
- feat: support resolving path with extra query by @JounQin in #54
- feat: support pass closure to restriction by @SyMind in #60
- feat: async fs by @nilptr in #38
- fix: template variable not replaced in baseUrl of tsconfig by @stormslowly in #61
New Contributors
Full Changelog: v0.5.3...v0.5.4