Skip to content

bug(server-sdk): published package cannot install because better-ws is missing from npm #2359

Description

@ppdbxdawj

Describe the bug

@proj-airi/server-sdk@0.12.0-beta.1 cannot be installed in a clean external project from the public npm registry.

The published SDK declares @proj-airi/better-ws@^0.12.0-beta.1 as a runtime dependency. That package is not available from the registry.

Steps to reproduce

mkdir airi-server-sdk-repro
cd airi-server-sdk-repro
pnpm init
pnpm add @proj-airi/server-sdk@0.12.0-beta.1 \
  --registry=https://registry.npmjs.org

Actual result

[ERR_PNPM_FETCH_404] GET https://registry.npmjs.org/@proj-airi%2Fbetter-ws: Not Found - 404

This error happened while installing the dependencies of @proj-airi/server-sdk@0.12.0-beta.1

@proj-airi/better-ws is not in the npm registry, or you have no permission to fetch it.

@proj-airi/server-sdk@0.11.3 fails for the same reason.

Expected result

A clean external project can install the published Server SDK with the command from its README.

Additional context

Possible fixes

The correct fix depends on the intended package design:

  1. Publish @proj-airi/better-ws.
  2. Bundle better-ws into @proj-airi/server-sdk.
  3. Remove the private runtime dependency, or replace it with a public dependency.
  4. Keep server-sdk internal. Document another supported external integration path.

After maintainers confirm the package design, I can prepare a focused PR.

I can also add a release regression test. The test will pack the related packages and install the Server SDK in a clean project.

System Info

The auto-generated host system information below is not the environment used for the reproduction.

Host shell:

  • OS: macOS 26.5.1, arm64 Apple M2 Pro
  • Node: 20.11.0
  • pnpm: 8.14.1

The installation failure was reproduced in a clean environment with:

The failure is a registry 404 for @proj-airi/better-ws, so it is independent of the host shell's Node and pnpm versions.

Validations

  • Follow our Code of Conduct
  • Read the Contributing Guide.
  • Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
  • Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.

Contributions

  • I am willing to submit a PR to fix this issue
  • I am willing to submit a PR with failing tests (actually just go ahead and do it, thanks!)

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingpending triageNot yet confirmed.scope/engineeringScope related to toolchain, workflow, workspace, and CI/CD, deploy, packaging, etc.

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions