@clearcms/db@0.1.2

Patch Changes

• 68f91de Thanks @slavasolutions! - Fix @clearcms/db to ship a compiled dist/ instead of raw .ts
  sources. Closes #87 (Node 22+ admin requests 500 with
  ERR_UNSUPPORTED_NODE_MODULES_TYPE_STRIPPING) and #89 (the dev
  script NODE_OPTIONS workaround that the missing dist forced).

  What changed:

  • packages/db/tsconfig.build.json — new file, mirrors
    packages/spec/tsconfig.build.json (noEmit: false,
    declaration, declarationMap, sourceMap,
    rewriteRelativeImportExtensions, excludes test files).
  • packages/db/package.json:
    • main / types → ./dist/index.js / ./dist/index.d.ts.
    • exports — each entry (., ./schema, ./client,
      ./migrate) is a {types, default} conditional pointing at
      the corresponding compiled file. ./migrations keeps pointing
      at the bare directory (drizzle SQL files, not compiled).
    • scripts.build — tsc -p tsconfig.build.json. Picked up by
      the monorepo's pnpm -r build automatically.
    • files — replaces src with dist. Raw .ts no longer ships
      in the published tarball; consumers get only the compiled JS +
      types + the migrations directory.

  pnpm --filter @clearcms/db build produces 4 modules × 4 artifacts
  (.js, .js.map, .d.ts, .d.ts.map) under dist/. Typecheck
  clean.

  Audit of other @clearcms/* packages confirms no other shipped-version
  package is in the same state: mcp and index already compile to
  dist/ and ship correctly; design is a CSS/SVG/CJS asset bundle
  (intentionally not TS-compiled); spec / storage / sdk / core
  known good.