Bug: factory not found on runtime

[simon-tannai]

Versions

• Node: 20
• OS: Docker Alpine

Reproduction

Additional Details

Commands:

{
    "cli": "node ./dist/apps/cli/main",
    "cli:dev": "ts-node ./apps/cli/src/main"
}

Datasource:

private readonly options: DataSourceOptions & SeederOptions = {
    ...databaseConfig,
    factories: [join(__dirname, '..', '..', '..', '..', 'apps', 'my-app', 'src', '**', '*.factory{.ts,.js}')],
    seeds: [MainSeeder],
}

Steps to reproduce

I'm using nest-commander to create a CLI application to seed a database into a production-like environment.

In dev' env', the seeding is working well. But in production-like env' (after TS build), it's not working.

It looks typeorm-extension is not working without ts-node ?

What is Expected?

Running seeds into production-like environment without ts-node.

What is actually happening?

Error: No seeder factory is registered for the entity: MyEntity

[simon-tannai]

In the other hand, it's working well when I'm importing manually all the entities and factories:

  private readonly options: DataSourceOptions & SeederOptions = {
    ...databaseConfig,
    entities: [
      MyFirstEntity,
      [...]
      MySecondEntity,
    ],
    factories: [
      MyFirstFactory,
      [...]
      MySecondFactory,
    ],
    seeds: [MainSeeder],
  }

[IB3N]

+1

[tada5hi]

Can you please provide a repository for reproduction.

[rostoriginal]

+1

This stopped working when I updated to version 3.6.2; everything was working correctly with version 3.6.1.

Node 20.18.0
OS: Windows 11
Framework: NestJS

{
"@nestjs/common": "^10.4.4",
    "@nestjs/config": "^3.2.3",
    "@nestjs/core": "^10.4.4",
    "@nestjs/platform-express": "^10.4.4"
    "@nestjs/typeorm": "^10.0.2",
}

Sample of my code which run seeder:

function runSeeder(seeder: string) {
  try {
    console.log(`Run seeder: ${seeder}`);
    execSync(
      `ts-node ./node_modules/typeorm-extension/bin/cli.cjs seed:run -d ./src/db/data-source.ts -n ${seeder}`,
      { stdio: 'inherit' },
    );
  } catch (error) {
    console.error(`Error run seeder ${seeder}:`, error);
  }
}

[tada5hi]

Triaged and reproduced the mechanics: in a compiled environment the factory glob gets the src → dist rewrite, e.g. /app/apps/my-app/src/**/*.factory{.ts,.js} → /app/apps/my-app/dist/**/… — but a Nest monorepo build outputs to dist/apps/my-app/…, so the glob matches nothing and no factory registers. The heuristic can't guess monorepo layouts: point the factories glob at the compiled layout for production runs (or run under ts-node/tsx, which v4 auto-detects, or pass preserveFilePaths). A docs note for monorepo setups is planned.