@proj-airi/server-sdk@0.12.0-beta.1 cannot install because @proj-airi/better-ws is not published

[ppdbxdawj]

Summary

The public @proj-airi/server-sdk@0.12.0-beta.1 package cannot install in an external project.

The package depends on @proj-airi/better-ws@^0.12.0-beta.1. The public npm registry does not contain this dependency.

The Server SDK README gives external installation commands. I want to confirm the intended distribution path.

Environment

AIRI main: d5742dbb7a44fbb24e1887230c9f21328261efe4
OS: macOS 26.5.1 arm64
Node.js: v24.19.0
pnpm: 11.19.0
Registry: https://registry.npmjs.org

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.

The same dependency problem also affects @proj-airi/server-sdk@0.11.3.

In the current AIRI source, packages/better-ws/package.json contains "private": true.

Expected result

If the Server SDK supports external projects, the installation command succeeds with the public npm registry.

If the Server SDK is internal, its documentation identifies the supported external integration path.

Question

Is @proj-airi/server-sdk intended for use outside the AIRI monorepo?

Which solution matches the intended package design?

1. Publish @proj-airi/better-ws.
2. Bundle better-ws into server-sdk.
3. Remove or replace the private runtime dependency.
4. Keep server-sdk internal and document another external integration path.

Contribution

I am willing to prepare a focused PR after you confirm the preferred direction.

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

I did not vendor AIRI packages or use a local monorepo link. Those workarounds would make the external integration non-reproducible.

[ChangkeunJ]

To narrow the option list slightly, I checked the registry and better-ws is the only gap. @proj-airi/server-shared@0.12.0-beta.1 and @moeru/std both resolve fine, so this is one package rather than a general "the SDK was never published" situation.

Worth spelling out how this ships broken quietly, because it explains why 0.11.3 has it too. pnpm rewrites workspace:* into a real version range when it packs, but it skips private: true packages entirely at publish time. So the published manifest goes out pointing at ^0.12.0-beta.1 of something that will never exist on the registry, and nothing in the publish step fails or warns. It only surfaces when somebody installs from outside the monorepo, which is exactly what you did.

I'd treat your fourth option as a real contender alongside the first rather than a fallback. Publishing better-ws turns it into a public API surface the project then has to keep stable, which may not be the intent for what sounds like an internal transport. Bundling it into server-sdk at build time keeps the external install working without taking on that commitment, at the cost of it no longer being shared as its own unit.

Either way, the pack-and-install-into-a-clean-project test you offered is the part I'd want most, since that's the thing that would have caught this before 0.11.3 went out.