import error with ts-node-maintained

[klever34]

Does anyone know why running node ace migration:run --force returns this error?

node:internal/modules/esm/resolve:857
  throw new ERR_MODULE_NOT_FOUND(packageName, fileURLToPath(base), null);
        ^

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'ts-node-maintained' imported from /app/ace.js
    at packageResolve (node:internal/modules/esm/resolve:857:9)
    at moduleResolve (node:internal/modules/esm/resolve:926:18)
    at defaultResolve (node:internal/modules/esm/resolve:1056:11)
    at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:654:12)
    at #cachedDefaultResolve (node:internal/modules/esm/loader:603:25)
    at ModuleLoader.resolve (node:internal/modules/esm/loader:586:38)
    at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:242:38)
    at ModuleJob._link (node:internal/modules/esm/module_job:135:49) {
  code: 'ERR_MODULE_NOT_FOUND'
}

Node.js v22.12.0

I'm working with the latest version of AdonisJS.

[RomainLanz]

Hey @klever34! 👋🏻

Do you have ts-node-maintained installed?

[klever34]

@RomainLanz
Yes, I do.

  "devDependencies": {
    "@adonisjs/assembler": "^7.8.2",
    "@adonisjs/eslint-config": "^2.0.0-beta.6",
    "@adonisjs/prettier-config": "^1.4.0",
    "@adonisjs/tsconfig": "^1.4.0",
    "@japa/api-client": "^2.0.3",
    "@japa/assert": "^3.0.0",
    "@japa/plugin-adonisjs": "^3.0.1",
    "@japa/runner": "^3.1.4",
    "@swc/core": "1.7.26",
    "@types/luxon": "^3.4.2",
    "@types/node": "^22.7.5",
    "eslint": "^9.12.0",
    "hot-hook": "^0.3.1",
    "pino-pretty": "^11.2.2",
    "prettier": "^3.3.3",
    "ts-node-maintained": "^10.9.4",
    "typescript": "~5.6"
  },

[RomainLanz]

Are you trying to run node ace in production without having built the application?

[klever34]

@RomainLanz I am trying to deploy to Heroku. The build gets done completely. The funny thing is it either returns the ts-node-maintained error or the one below in the logs

remote: Building source:
remote: 
remote: -----> Building on the Heroku-24 stack
remote: -----> Using buildpack: heroku/nodejs
remote: -----> Node.js app detected
remote:        
remote: -----> Creating runtime environment
remote:        
remote:        NPM_CONFIG_LOGLEVEL=error
remote:        USE_YARN_CACHE=true
remote:        NODE_VERBOSE=false
remote:        NODE_ENV=production
remote:        NODE_MODULES_CACHE=true
remote:        
remote: -----> Installing binaries
remote:        engines.node (package.json):   unspecified
remote:        engines.npm (package.json):    unspecified (use default)
remote:        engines.yarn (package.json):   unspecified (use default)
remote:        
remote:        Resolving node version 22.x...
remote:        Downloading and installing node 22.12.0...
remote:        Using default npm version: 10.9.0
remote:        Resolving yarn version 1.22.x...
remote:        Downloading and installing yarn (1.22.22)
remote:        Installed yarn 1.22.22
remote:        
remote: -----> Restoring cache
remote:        - yarn cache
remote:        
remote: -----> Installing dependencies
remote:        Installing node modules (yarn.lock)
remote:        yarn install v1.22.22
remote:        [1/4] Resolving packages...
remote:        warning Resolution field "[email protected]" is incompatible with requested version "strtok3@^9.0.1"
remote:        [2/4] Fetching packages...
remote:        [3/4] Linking dependencies...
remote:        warning "@japa/assert > api-contract-validator > api-schema-builder > swagger-parser > @apidevtools/[email protected]" has unmet peer dependency "openapi-types@>=7".
remote:        [4/4] Building fresh packages...
remote:        Done in 3.29s.
remote:        
remote: -----> Build
remote:        Running build (yarn)
remote:        yarn run v1.22.22
remote:        $ node ace build
remote:        [ info ] cleaning up output directory (build)
remote:        [ info ] compiling typescript source (tsc)
remote:        [ info ] rewrited ace file (build/ace.js)
remote:        [ info ] copying meta files to the output directory
remote:        [ success ] build completed
remote:        
remote:        ╭────────────────────────────────────────────────────────────────────────╮
remote:        │    Run the following commands to start the server in production        │
remote:        │────────────────────────────────────────────────────────────────────────│
remote:        │                                                                        │
remote:        │    ❯ cd build                                                          │
remote:        │    ❯ yarn install --production                                         │
remote:        │    ❯ node bin/server.js                                                │
remote:        │                                                                        │
remote:        ╰────────────────────────────────────────────────────────────────────────╯
remote:        Done in 3.69s.
remote:        
remote: -----> Pruning devDependencies
remote:        yarn install v1.22.22
remote:        [1/4] Resolving packages...
remote:        warning Resolution field "[email protected]" is incompatible with requested version "strtok3@^9.0.1"
remote:        [2/4] Fetching packages...
remote:        [3/4] Linking dependencies...
remote:        warning "@japa/assert > api-contract-validator > api-schema-builder > swagger-parser > @apidevtools/[email protected]" has unmet peer dependency "openapi-types@>=7".
remote:        [4/4] Building fresh packages...
remote:        warning Ignored scripts due to flag.
remote:        Done in 1.22s.
remote:        
remote: -----> Caching build
remote:        - yarn cache
remote:        
remote: -----> Build succeeded!
remote:  !     Unmet dependencies don't fail yarn install but may cause runtime issues
remote:        https://github.com/npm/npm/issues/7494
remote: 
remote: -----> Discovering process types
remote:        Procfile declares types -> release, web
remote: 
remote: -----> Compressing...
remote:        Done: 107.4M
remote: -----> Launching...
remote:  !     Release command declared: this new release will not be available until the command succeeds.
remote:        Released v31
remote:        https://api-ae6.herokuapp.com/ deployed to Heroku
remote: 
remote: Verifying deploy.... done.
remote: Running release command...
remote: 
remote: 
remote: node:internal/modules/run_main:122 
remote:     triggerUncaughtException(
remote:     ^
remote: [Object: null prototype] {
remote:   [Symbol(nodejs.util.inspect.custom)]: [Function: [nodejs.util.inspect.custom]]
remote: }
remote: 
remote: Node.js v22.12.0
remote: Waiting for release... failed.

[RomainLanz]

You're missing a few steps. In your case, it looks like you’re running the command from the project's root directory, which still contains the unbuilt application.

I’m not sure how Heroku works, but you need to build the application and deploy only the build folder. After that, re-install the production dependencies from within that folder to keep your deployment as minimal as possible.

[klever34]

Let me look into your suggestion @RomainLanz
Thanks

[klever34]

@RomainLanz You're right about me not running the command in the correct folder. I only needed to CD into the build folder.
For anyone working with the current Adonis, here's theProcfile that worked for me:

web: node build/bin/server.js
release: cd build && node ace migration:run --force