Skip to content

bug: ghost-deps uninstallable under bun (vendored @ghostdeps/* deps fail registry resolution) #520

Description

@rowkav09

Found dogfooding the 0.1.6 line (rollout wave 1, GitHub-profile-stats): `bun add -d ghost-deps` fails:

```
error: @ghostdeps/python@0.1.6 failed to resolve
error: @ghostdeps/javascript-typescript@0.1.6 failed to resolve
```

The staged manifest lists the vendored workspace packages in `dependencies` AND `bundledDependencies`. npm handles this: the tarballs ship `node_modules/@ghostdeps/`, so npm never resolves those names from the registry. Bun resolves every `dependencies` entry from the registry regardless of `bundledDependencies`, and the `@ghostdeps/` names are unpublished - so the install dies.

Options: (a) publish the @ghostdeps/* packages for real (bigger surface, contradicts the single-package design); (b) drop the vendored names from `dependencies` and let the bundling speak for itself - needs verification that npm still links them correctly from the tarball; (c) accept and document bun as unsupported. Judgment call for design; (b) looks right if npm's behavior holds without the declarations.

Repro: `mkdir t && cd t && bun init -y && bun add ghost-deps@0.1.6`.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions