web-infra-dev / nodejs_resolver

web-infra-dev/nodejs_resolver Issues

feat: resolve absolute path alias
Closed 6 months ago14
Is there a way to resolve request without cache?
Updated 6 months ago
is able to use it in wasm, e.g. swc plugin?
Closed 7 months ago1
Get ready for v1.0.0
Closed 7 months ago
Add parcel's node resolver to the benchmarks
Updated a year ago
can't deal with priority correctlly
Closed a year ago1
feat: support extensionAlias
Closed a year ago
Perf: make `resolve_file_with_ext` faster
Closed a year ago
perf: heavy load on hashing Path
Closed a year ago1
More privacy friendly error message
Updated a year ago
perf: remove raw value of package.json and tsconfig.json
Closed a year ago1
Perf: reuse file size for `fs::read_to_string`
Closed a year ago1
Feat: port DescriptionFilePlugin for package.json
Closed a year ago2
Perf: Better cache hit for `std::fs::canonicalize` and `std::fs::metadata`
Closed a year ago3
Bug: Failed performing readlink on relative path
Closed a year ago2
Feat: detect out of scope target
Closed a year ago
Why is the benchmark comment stuck on comparing to `Previous: 42e5d11` ?
Closed a year ago
`Eq` for `PathBuf`
Closed a year ago
Refactor: more idiomatic Rust codebase
Closed a year ago1
Perf: use `Cow<Path>` and `Arc<Path>` to reduce re-allocation
Closed a year ago1
Refactor: use CanonicalPath for better readability
Closed a year ago
perf: `parse_identifier` can return `SmolStr` directly instead of allocating for a `String`
Closed a year ago1