Jason Bedard

refactor(npm): add validation of parsed pnpm-lock data

1

This has been useful debugging and I think should always be done. For now it outputs errors to stdout, maybe we can change that to `fail` if/when we are more...

fix(npm): pnpm v9 file: archive references

1

--- ### Changes are visible to end-users: yes/no - Searched for relevant documentation and updated as needed: yes/no - Breaking change (forces users to change their own code or config):...

It seems they are treated as file: project references due to how pnpm9 uses the `file:...` path as the version number.

[FR]: do not propagate type-check/compile-time only dependencies

1

### What is the current behavior? Things like `@types` are only required at type-check time but are passed through all the way into the runfiles. ### Describe the feature Prevent...

### What is the current behavior? All transitive npm packages within `npm_package(srcs)` get collected and put into the `.aspect_rules_js/{pkg}@0.0.0/node_modules/*`. Of those transitive packages include multiple versions of a package under...

refactor(npm): change npm_import_links(replace_package) to label attribute

1

### Changes are visible to end-users: no ### Test plan - Covered by existing test cases

fix(npm): replace npm_translate_lock(replace_packages) with replace_package module extension

1

A replacement of the `npm_translate_lock(replace_packages)` API for bzlmod to ensure labels are passed from the user module instead of strings. --- ### Changes are visible to end-users: no ### Test...

WIP: an alternative of https://github.com/aspect-build/rules_js/pull/1808 --- ### Changes are visible to end-users: yes/no - Searched for relevant documentation and updated as needed: yes/no - Breaking change (forces users to change...

Instead of in the sequential walk of the trie while `Configure`/`GenerateRules` is invoked...

The go 1.24 [AddFinalizer](https://tip.golang.org/doc/go1.24#improved-finalizers) may provide better performance and be more reliable. Manually invoking `tree.Close()` might be worth ensuring cleanup is actually invoked since `runtime.SetFinalizer` seems to have many edge...