fix(shared): replace CJS require() with static ESM import for semver

[EduardF1]

Problem

When running any example with tsx (or any Node.js ESM loader), startup crashes immediately:

Error: Dynamic require of "semver" is not supported
    at getNpmSemver (packages/shared/dist/chunk-Y6FXYEAI.mjs:5:9)
    at satisfies (packages/shared/dist/index.mjs:132:10)

Root cause: packages/shared/src/semver.ts uses a lazy-init pattern with require("semver") (CJS). When tsup bundles this into .mjs output for the ESM format, the dynamic require() call is preserved in the bundle but require is not available in ESM context — Node.js throws at runtime.

Fix

Replace the lazy require() with a static top-level import:

// Before
function getNpmSemver() {
  _npmSemver ??= require("semver")
  return _npmSemver
}

// After
import semver from "semver"

The lazy-loading was purely a startup-cost optimisation; with a static import tsup can tree-shake unused exports and the module resolves correctly in both CJS and ESM bundles.

Testing

pnpm build
npx tsx examples/agent-cli/index.tsx  # now starts correctly ✅

Tested on Node.js v24.15.0, pnpm v10.32.1, Windows.

[EduardF1]

Hi @Minnzen, friendly nudge on this one. The change replaces the CJS require('semver') call with a static ESM import to fix the resolution error in the linked issue. Single-file change, runtime behavior identical when semver loads.

[Minnzen]

Thanks for the catch and the clean fix, @EduardF1! 🙏 Verified locally, merging now