Root cause: Railpack builds from the app's build path (apps/web), which has no bun.lock, so it falls back to npm. npm then resolves @better-auth/core's ^1.6.22 peer to 1.7.0 (needs better-call@1.4.0) while the pinned plugins peer better-call@1.3.7 -> ERESOLVE.
Changes:
packageManager: bun@1.3.14 at root (Railpack priority #1 signal; with the Dokploy build path removed, installs run bun install --frozen-lockfile at the workspace root and root scripts build/start the web app)
npm overrides @better-auth/core 1.6.22 + better-call 1.3.7 (root + apps/web) so any npm-based build resolves too
bun.lock updated (records overrides; 1020 pkgs, no version changes)
Verified: isolated npm install resolves (698 pkgs, exit 0), bun install no-op, full next build passes.
Fixes the ERESOLVE failing production builds.
Root cause: Railpack builds from the app's build path (apps/web), which has no bun.lock, so it falls back to npm. npm then resolves @better-auth/core's ^1.6.22 peer to 1.7.0 (needs better-call@1.4.0) while the pinned plugins peer better-call@1.3.7 -> ERESOLVE.
Changes:
- packageManager: bun@1.3.14 at root (Railpack priority #1 signal; with the Dokploy build path removed, installs run `bun install --frozen-lockfile` at the workspace root and root scripts build/start the web app)
- npm overrides @better-auth/core 1.6.22 + better-call 1.3.7 (root + apps/web) so any npm-based build resolves too
- bun.lock updated (records overrides; 1020 pkgs, no version changes)
Verified: isolated npm install resolves (698 pkgs, exit 0), bun install no-op, full next build passes.
Railpack builds the Dokploy app from the app's build path, which is
apps/web — a dir with no bun.lock (it lives at the monorepo root), so
Railpack fell back to npm. npm then resolved @better-auth/core's ^1.6.22
peer to 1.7.0 while the pinned plugins peer better-call@1.3.7, causing
ERESOLVE and failing the build.
- Declare packageManager: bun@1.3.14 at the root (Railpack's
highest-priority signal; combined with removing the Dokploy build path,
installs run 'bun install --frozen-lockfile' at the workspace root).
- Add npm overrides (@better-auth/core 1.6.22, better-call 1.3.7) in
root + apps/web as a safety net so any npm-based build resolves too.
- Verified: isolated npm install resolves (698 pkgs), bun install is a
no-op (1020 pkgs, versions unchanged), full next build passes.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Fixes the ERESOLVE failing production builds.
Root cause: Railpack builds from the app's build path (apps/web), which has no bun.lock, so it falls back to npm. npm then resolves @better-auth/core's ^1.6.22 peer to 1.7.0 (needs better-call@1.4.0) while the pinned plugins peer better-call@1.3.7 -> ERESOLVE.
Changes:
bun install --frozen-lockfileat the workspace root and root scripts build/start the web app)Verified: isolated npm install resolves (698 pkgs, exit 0), bun install no-op, full next build passes.