import error with ts-node-maintained

[hackerrahul]

Ubuntu 24.04 LTS
Docker version 27.0.3, build 7d4bcd8

Running on Coolify using Dockerfile build

Dockerfile

FROM node:22.16.0-alpine3.22 AS base

# All deps stage
FROM base AS deps
WORKDIR /app
ADD package.json yarn.lock ./
RUN yarn install --frozen-lockfile

# Production only deps stage
FROM base AS production-deps
WORKDIR /app
ADD package.json yarn.lock ./
RUN yarn install --frozen-lockfile --production

# Build stage
FROM base AS build
WORKDIR /app
COPY --from=deps /app/node_modules /app/node_modules
ADD . .
RUN node ace build --ignore-ts-errors

# Production stage
FROM base
ENV NODE_ENV=production
WORKDIR /app
COPY --from=production-deps /app/node_modules /app/node_modules
COPY --from=build /app/build /app
EXPOSE 3000
CMD ["node", "./bin/server.js"]

Error

2025-Sep-20 08:06:18.256762
#14 [build 5/5] RUN node ace build --ignore-ts-errors
2025-Sep-20 08:06:18.256762
#14 0.123 node:internal/modules/package_json_reader:256
2025-Sep-20 08:06:18.256762
#14 0.123   throw new ERR_MODULE_NOT_FOUND(packageName, fileURLToPath(base), null);
2025-Sep-20 08:06:18.256762
#14 0.123         ^
2025-Sep-20 08:06:18.256762
#14 0.123
2025-Sep-20 08:06:18.256762
#14 0.123 Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'ts-node-maintained' imported from /app/ace.js
2025-Sep-20 08:06:18.256762
#14 0.123     at Object.getPackageJSONURL (node:internal/modules/package_json_reader:256:9)
2025-Sep-20 08:06:18.256762
#14 0.123     at packageResolve (node:internal/modules/esm/resolve:768:81)
2025-Sep-20 08:06:18.256762
#14 0.123     at moduleResolve (node:internal/modules/esm/resolve:854:18)
2025-Sep-20 08:06:18.256762
#14 0.123     at defaultResolve (node:internal/modules/esm/resolve:984:11)
2025-Sep-20 08:06:18.256762
#14 0.123     at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:780:12)
2025-Sep-20 08:06:18.256762
#14 0.123     at #cachedDefaultResolve (node:internal/modules/esm/loader:704:25)
2025-Sep-20 08:06:18.256762
#14 0.123     at ModuleLoader.resolve (node:internal/modules/esm/loader:687:38)
2025-Sep-20 08:06:18.256762
#14 0.123     at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:305:38)
2025-Sep-20 08:06:18.256762
#14 0.123     at ModuleJob._link (node:internal/modules/esm/module_job:137:49) {
2025-Sep-20 08:06:18.256762
#14 0.123   code: 'ERR_MODULE_NOT_FOUND'
2025-Sep-20 08:06:18.256762
#14 0.123 }
2025-Sep-20 08:06:18.256762
#14 0.123
2025-Sep-20 08:06:18.256762
#14 0.123 Node.js v22.16.0
2025-Sep-20 08:06:18.256762
#14 ERROR: process "/bin/sh -c node ace build --ignore-ts-errors" did not complete successfully: exit code: 1
2025-Sep-20 08:06:18.256762
------
2025-Sep-20 08:06:18.256762
> [build 5/5] RUN node ace build --ignore-ts-errors:
2025-Sep-20 08:06:18.256762
0.123     at defaultResolve (node:internal/modules/esm/resolve:984:11)
2025-Sep-20 08:06:18.256762
0.123     at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:780:12)
2025-Sep-20 08:06:18.256762
0.123     at #cachedDefaultResolve (node:internal/modules/esm/loader:704:25)
2025-Sep-20 08:06:18.256762
0.123     at ModuleLoader.resolve (node:internal/modules/esm/loader:687:38)
2025-Sep-20 08:06:18.256762
0.123     at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:305:38)
2025-Sep-20 08:06:18.256762
0.123     at ModuleJob._link (node:internal/modules/esm/module_job:137:49) {
2025-Sep-20 08:06:18.256762
0.123   code: 'ERR_MODULE_NOT_FOUND'
2025-Sep-20 08:06:18.256762
0.123 }
2025-Sep-20 08:06:18.256762
0.123
2025-Sep-20 08:06:18.256762
0.123 Node.js v22.16.0
2025-Sep-20 08:06:18.256762
------

I have seen couple of similar issue on other users in discussion also.

[hackerrahul]

Found the temporary fix

Change NODE_ENV=production to NODE_ENV=development

and changed/added these line in config/logger.ts file

transport: {
        targets: targets()
          .pushIf(app.inTest, targets.pretty())
          .pushIf(app.inDev, targets.file({ destination: 1 }))
          .pushIf(app.inProduction, targets.file({ destination: 1 }))
          .toArray()

      },

yet to find production issue