fix(bazel): use module-scoped npm extension repo

[Jess Sullivan (Jesssullivan)]

Summary

• rename the generated npm extension repo from generic npm to tummycrypt_tinyland_event_loader_npm
• update BUILD.bazel loads to use the module-scoped npm repo
• prepare the module for composition in the active Bazel registry

Validation

• pnpm typecheck
• pnpm test
• pnpm build
• pnpm check:package
• npx --yes @bazel/bazelisk build //:pkg //:test --verbose_failures

[greptile-apps]

Greptile Summary

This PR renames the Bazel npm extension repository from the generic npm to the module-scoped tummycrypt_tinyland_event_loader_npm, and updates all corresponding load statements in BUILD.bazel. The change is internally consistent and follows the standard Bazel convention for avoiding name collisions when composing modules in a registry.

Confidence Score: 5/5

Safe to merge — the rename is consistent across all references with no logic changes.

Both changed files are fully consistent: the new repo name in MODULE.bazel matches the load paths in BUILD.bazel exactly, and the module name prefix convention is followed. No logic, dependencies, or outputs are altered.

No files require special attention.

Important Files Changed

Filename	Overview
MODULE.bazel	Renames the npm extension repo from npm to tummycrypt_tinyland_event_loader_npm in both npm_translate_lock and use_repo, scoping it to this module for registry composition.
BUILD.bazel	Updates both load statements to reference the new module-scoped @tummycrypt_tinyland_event_loader_npm repo, consistent with the rename in MODULE.bazel.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[MODULE.bazel] -->|npm_translate_lock name| B[tummycrypt_tinyland_event_loader_npm]
    A -->|use_repo| B
    B -->|defs.bzl npm_link_all_packages| C[BUILD.bazel]
    B -->|vitest/package_json.bzl vitest_bin| C

Loading

_{Reviews (1): Last reviewed commit: "fix(bazel): use module-scoped npm extens..." | Re-trigger Greptile}