-
-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: factory not found on runtime #1019
Comments
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],
} |
+1 |
Can you please provide a repository for reproduction. |
+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
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Versions
Reproduction
Additional Details
Commands:Datasource:
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?
The text was updated successfully, but these errors were encountered: