@goatech/server (deprecated)

This package is a backward-compatibility shim. The Sheepit Server SDK has moved to @sheepit-ai/server.

All exports are identical — only the package name changed. Swap your dependency:

- "@goatech/server": "^1.0.0"
+ "@sheepit-ai/server": "^1.0.0"

If you're on ^0.1.x: this shim publishes as 1.0.0, so ^0.1.x will NOT auto-resolve. Change your range to ^1.0.0 (or migrate directly to @sheepit-ai/server@^1.0.0).

And update your imports:

- import { GoaTechServer } from "@goatech/server";
- import { getGoaTech } from "@goatech/server/nextjs";
+ import { GoaTechServer } from "@sheepit-ai/server";
+ import { getGoaTech } from "@sheepit-ai/server/nextjs";

The class name GoaTechServer is unchanged — only the package import path moves. A future v2 of @sheepit-ai/server may rename to Sheepit/SheepitServer with deprecated aliases; that's a separate migration.

This shim will emit a console.warn on import until you migrate (once per JS realm — that's once per main thread, once per worker_thread, once per vm.Context). It will stop receiving updates after 2026-11-26.

Full migration guide: https://www.goatech.ai/docs/migrate-to-sheepit

Publishing this shim (maintainers only)

Order matters. The shim depends on @sheepit-ai/server: workspace:*, which pnpm publish rewrites to a real semver range. That rewrite fails closed if the dependency isn't published yet:

1. pnpm --filter @sheepit-ai/server publish --access public — must succeed first.
2. pnpm --filter @goatech/server publish --access public — shim publishes after.
3. npm deprecate "@goatech/server@<2.0.0" "Renamed to @sheepit-ai/server. See README."

Reversing the order publishes the shim with a broken dep.