Danny Avila 98755d86c8 📦 chore: Declare runtime deps externalized by tsdown in @librechat/api (#13600) ... The tsdown migration (#13595) externalizes all third-party imports (Rollup inlined them), so several modules the api source imports must be present at runtime. Six were not, causing production (`npm ci --omit=dev`) to crash on boot with `Cannot find module 'get-stream'` (then the next). Fixed following the package's existing convention — packages/api declares runtime libs as `peerDependencies`, and the `/api` app provides them as real `dependencies` (how express/mongoose/sharp already resolve): - `api/package.json` (the prod app, the provider): add the 3 that were missing — `get-stream`, `jszip`, `mongodb`. (`dedent`/`lodash`/`nanoid` were already provided by /api.) - `packages/api/package.json`: add all 6 to `peerDependencies` (the contract) and to `devDependencies` (workspace build/tests), matching the existing `mammoth`/`pdfjs-dist`/`sanitize-html` dev+peer pattern. `jszip`/`mongodb` move out of dev-only (were pruned in production). Pinned to CJS-compatible majors (get-stream@6, nanoid@3). Verified the built bundle has zero undeclared externals and the 3 newly-provided deps are production (non-dev) in the lockfile, so they survive `--omit=dev`.		2026-06-08 13:18:04 -04:00
..
src	🧩 feat: Enable Model Spec Subagents (#13598)	2026-06-08 11:43:08 -04:00
types
.gitignore
babel.config.cjs
jest.config.mjs	📜 feat: Improve Skill Authoring Guidance (#13517)	2026-06-04 18:36:16 -04:00
jest.setup.cjs
package.json	📦 chore: Declare runtime deps externalized by tsdown in @librechat/api (#13600)	2026-06-08 13:18:04 -04:00
tsconfig-paths-bootstrap.mjs
tsconfig.build.json
tsconfig.json
tsconfig.spec.json
tsdown.config.mjs	⚡️ refactor: Migrate @librechat/api build to tsdown (#13595)	2026-06-08 10:54:48 -04:00