ekklesiaandClaude Opus 5.5
fc422b6d8d
@ekklesia/module-sdk imports drizzle-orm at run time but declared it only as a peer and a development dependency. A workspace package is linked into its consumers as a directory, so its imports resolve from its own node_modules, where a consumer never satisfies a peer; a production install omits development dependencies. In the production image this made every module with a schema fail: the API exited at startup and Doctor reported NOT READY. - Move drizzle-orm to module-sdk's dependencies, keeping the peer. - Move react to @ekklesia/ui's dependencies, keeping the peer. The new guard flags it the same way; it is bundled at build time today, so it was not a live failure. Both lockfile entries keep the identical resolution, so nothing new is installed and the shell bundles still contain one React. - Add the boundary rule runtime-imports-are-production-dependencies: code a package ships (src/, bin/, excluding tests and .d.ts) must declare every runtime import in dependencies or optionalDependencies. Type-only imports are exempt; .tsx/.jsx implies react (automatic JSX runtime). Fixtures cover peer-only, dev-only, JSX, undeclared, and the accepted cases. Co-Authored-By: Claude Opus 5.5 <[email protected]>
14 lines
266 B
JSON
14 lines
266 B
JSON
{
|
|
"name": "@ekklesia/sdk",
|
|
"version": "0.0.0",
|
|
"type": "module",
|
|
"peerDependencies": { "drizzle-orm": "0.45.2" },
|
|
"devDependencies": { "drizzle-orm": "0.45.2" },
|
|
"exports": {
|
|
".": "./src/index.ts"
|
|
},
|
|
"ekklesia": {
|
|
"layer": "module-sdk"
|
|
}
|
|
}
|