export ormconfig

[TrejGun]

I want to reopen issue #4068

in short I ask to move from old ts syntax

export = ORMConfig

to new

export default ORMConfig

[chanmathew]

Ran into this issue as well and had to solve it by using the old ts syntax to export

[TrejGun]

can you please eleborate why it is designed this way? what benefits it gives?

[Kononnable]

This feature was designed long time ago when default exports was not popular or even not possible yet.

[TrejGun]

babel 7.8.6 stopped to support this syntax and throws error

Babel compilation error SyntaxError: ~/ormconfig.ts: `export =` is not supported by @babel/plugin-transform-typescript
Please consider using `export <value>;`.

[napisani]

I was still having some problems with the mix between CommonJS (used by the CLI) and ESNext (used by the latest version of NestJS) here is what i did to get around the problem, incase it helps someone having the same problem:

ormconfig.ts

export default {
  type: 'mariadb',
  host: data.DATABASE_HOST,
  port: data.DATABASE_PORT,
  username: data.DATABASE_USER,
  password: data.DATABASE_PASS,
  database: data.DATABASE_SCHEMA,
//... etc
  }
};

in ormconfig_cli.ts

import ormconfig from './ormconfig';

// the TypeORM cli requires the modules to use CommonJS
// while the app  requires ESNext
// - this file takes the ESNext module and exports it in CommonJS format
export = ormconfig

in package.json

...
    "api:typeorm": "ts-node  -P apps/api/tsconfig.json  -O '{\"module\":\"commonjs\"}' -r tsconfig-paths/register ./node_modules/typeorm/cli.js --config apps/api/src/app/ormconfig_cli.ts",
    "api:typeorm:migrate": "npm run api:typeorm migration:generate -- -n migrations",
    "api:typeorm:run": "npm run api:typeorm migration:run"
...

in app module:

import ormconfig from './ormconfig';

[imnotjames]

This change should be live in 0.2.29 - which will be released in a few days. At that point you shouldn't need that hack 🙌 But good to know the workaround!

[TrejGun]

fixed, thanks