Add a way to run .ts files in Programmatic

[BetaTH]

Description

Error: Can't get migration files: /workspaces/clone-tabnews/src/infra/migrations/1718242225526_test-migration.ts:2
import { MigrationBuilder, ColumnDefinitions } from 'node-pg-migrate';
^^^^^^

SyntaxError: Cannot use import statement outside a module

I get this erro if a try to run typescript migrations files, generated by node-pg-migrate -j ts create.
Its seems a ""ESM | commonJS"" problem, but in CLI i can run .ts directly

Suggested solution

In CLI i can run node-pg-migrate up with passing tsconfig.json as a flag with compilerOptions.module: "commonjs" to directly run .ts files, it would be nice if i could do the same in the programmatic approach

Alternative

No response

Additional context

No response

[Shinigami92]

Would you like to test out this? #1187 (comment)

[BetaTH]

Would you like to test out this? #1187 (comment)

Yes, i will try

[BetaTH]

@Shinigami92
Still getting the same error

Error: Can't get migration files: /workspaces/clone-tabnews/src/infra/migrations/1718242225526_test-migration.ts:2
import { MigrationBuilder, ColumnDefinitions } from 'node-pg-migrate';
^^^^^^

SyntaxError: Cannot use import statement outside a module

[Shinigami92]

Are you able to create a minimal reproducible repository I can checkout?

[aprendendofelipe]

Could you test with node-pg-migrate-exp?

npm i node-pg-migrate-exp

import { ... } from 'node-pg-migrate-exp'

[BetaTH]

@aprendendofelipe It continues to work only in .js files with commonjs. In .ts with esm im getting the same error

[BetaTH]

@Shinigami92
you can use this repo
but go to branch test/node-pg-migrate-experimental that have your experimental version

• run npm install
• run npm run dev to up the server and database
• run npm run test:watch --- migrations to test api endpoint (or call the endpoint /api/v1/migrations in the browser)

[Shinigami92]

thx, just to set expectation, I will need to consume free-time for that, hopefully I find some time tomorrow

[Shinigami92]

looks like I did not found time "tomorrow" 😬 ...
my current plan is to go full esm only support and potentially even drop NodeJS v18 support, so I can use a feature from NodeJS v20.11+
But I even wait on something fixed in tsup... This will take a lot of time...
sry