[bug] false-positive success when using named export on seeder file

Basically, when the seeder file has some export const foo = 'bar'-ish statement, the run method is not invoked and the output is this:

🌱  TypeORM Seeding v1.6.1
✔ ORM Config loaded
✔ Factories are imported
✔ Seeders are imported
⠋ Connecting to the databaseINFO: All classes found using provided glob pattern xxx
INFO: All classes found using provided glob pattern xxx
✔ Database connected
👍  Finished Seeding

I think that typeorm-seeding CLI should ignore these statements regardless of whether it is right or not to have them in a seeder file.

---

I’ve notice that this behavior is due to seedFileObject[keys[0]]

https://github.com/w3tecch/typeorm-seeding/blob/4136b0e0f58a4ec13b17c717bd026043fbdf7ddd/src/importer.ts#L3-L7

because this will return the foo variable instead of the seeder class. I’ve thought that return seedFileObject.default was enough but @hirsch88 already use this in the past with require (on 84df811)

Maybe this should work but I’m not sure:

export const importSeed = async (filePath: string): Promise<SeederConstructor> => {
  const seedFileObject: { [key: string]: SeederConstructor } = await import(filePath)
  return seedFileObject.default
}

[jorgebodega]

Yes, that could work temporary while we still work on this. I will keep this issue open to use it as a reference.

Thanks for your help!

[jorgebodega]

For me mikro-orm seeding is a very good example on how to do this. But is unreleased yet.

I’m pretty sure we should create a project and start working on next version, maybe a 2.x version, because there will be breaking changes for sure.