Bug: unsupported ts-node-dev package in CLI command approach
jzfre opened this issue · 2 comments
jzfre commented
Versions
- Node:
- OS:
Reproduction
Somehow CLI command approach overwrites "src" -> "dist" in paths set by ENV variable
Steps to reproduce
- Install the project
- Set "TYPEORM_SEEDING_SEEDS" to "src/data/seeds/*.ts"
- Run the CLI with "ts-node-dev"
What is Expected?
It should work
What is actually happening?
Seeder files are not found
tada5hi commented
@jzfre yes, this is the default behavior. The library tries to resolve the outDir in the tsconfig.json, and then replaces the src with the dist path, depending on whether the execution is done in transpiled state or with ts-node.
But this will be obsolulet soon, because I am working on a refactor of the locter library so that not only the import of cjs but also of esm modules should be possible. Furthermore the script execution should take place in the transpiled state and if you try to load a typescript file, it will be transpiled on the fly.
tada5hi commented
can you give a bit more details, why this approach aka. current implementation is not working for you?