feat(core): remove static require calls #3814
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This pull request fixes 2 alerts when merging 0ef45f0 into be8f205 - view on LGTM.com fixed alerts:
Heads-up: LGTM.com's PR analysis will be disabled on the 5th of December, and LGTM.com will be shut down ⏻ completely on the 16th of December 2022. Please enable GitHub code scanning, which uses the same CodeQL engine ⚙️ that powers LGTM.com. For more information, please check out our post on the GitHub blog. |
Codecov ReportBase: 99.94% // Head: 99.90% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## v6 #3814 +/- ##
==========================================
- Coverage 99.94% 99.90% -0.05%
==========================================
Files 214 216 +2
Lines 13461 13429 -32
Branches 3130 3128 -2
==========================================
- Hits 13454 13416 -38
- Misses 7 13 +6
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
B4nan
force-pushed
the
remove-static-require
branch
from
0ef45f0
to
76a0e79
Compare
B4nan
changed the title
|
This pull request fixes 2 alerts when merging 76a0e79 into be8f205 - view on LGTM.com fixed alerts:
Heads-up: LGTM.com's PR analysis will be disabled on the 5th of December, and LGTM.com will be shut down ⏻ completely on the 16th of December 2022. Please enable GitHub code scanning, which uses the same CodeQL engine ⚙️ that powers LGTM.com. For more information, please check out our post on the GitHub blog. |
There were some places where we did a static `require()` call, e.g. when loading the driver implementation based on the `type` option. Those places were problematic for bundlers like webpack, as well as new school build systems like vite.
### The `type` option is removed in favour of driver exports
Instead of specifying the `type` we now have several options:
1. use `defineConfig()` helper imported from the driver package to create your ORM config:
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
export default defineConfig({ ... });
```
2. use `MikroORM.init()` on class imported from the driver package:
```ts title='app.ts'
import { MikroORM } from '@mikro-orm/mysql';
const orm = await MikroORM.init({ ... });
```
3. specify the `driver` option:
```ts title='mikro-orm.config.ts'
import { MySqlDriver } from '@mikro-orm/mysql';
export default {
driver: MySqlDriver,
...
};
```
> The `MIKRO_ORM_TYPE` is still supported, but no longer does a static require of the driver class. Its usage is rather discouraged and it might be removed in future versions too.
### ORM extensions
Similarly, we had to get rid of the `require()` calls for extensions like `Migrator`, `EntityGenerator` and `Seeder`. Those need to be registered as extensions in your ORM config. `SchemaGenerator` extension is registered automatically.
> This is required only for the shortcuts available on `MikroORM` object, e.g. `orm.migrator.up()`, alternatively you can instantiate the `Migrator` yourself explicitly.
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
import { Migrator } from '@mikro-orm/migrations';
import { EntityGenerator } from '@mikro-orm/entity-generator';
import { SeedManager } from '@mikro-orm/seeder';
export default defineConfig({
dbName: 'test',
extensions: [Migrator, EntityGenerator, SeedManager], // those would have a static `register` method
});
```
## `MikroORM.init()` no longer accepts a `Configuration` instance
The options always needs to be plain JS object now. This was always only an internal way, partially useful in tests, never meant to be a user API (while many people since the infamous Ben Awad video mistakenly complicated their typings with it).
B4nan
force-pushed
the
remove-static-require
branch
from
76a0e79
to
ae30889
Compare
B4nan
added a commit
that referenced
this pull request
Dec 3, 2022
There were some places where we did a static `require()` call, e.g. when
loading the driver implementation based on the `type` option. Those
places were problematic for bundlers like webpack, as well as new school
build systems like vite.
### The `type` option is removed in favour of driver exports
Instead of specifying the `type` we now have several options:
1. use `defineConfig()` helper imported from the driver package to
create your ORM config:
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
export default defineConfig({ ... });
```
3. use `MikroORM.init()` on class imported from the driver package:
```ts title='app.ts'
import { MikroORM } from '@mikro-orm/mysql';
const orm = await MikroORM.init({ ... });
```
5. specify the `driver` option:
```ts title='mikro-orm.config.ts'
import { MySqlDriver } from '@mikro-orm/mysql';
export default { driver: MySqlDriver, ... };
```
> The `MIKRO_ORM_TYPE` is still supported, but no longer does a static
require of the driver class. Its usage is rather discouraged and it
might be removed in future versions too.
### ORM extensions
Similarly, we had to get rid of the `require()` calls for extensions
like `Migrator`, `EntityGenerator` and `Seeder`. Those need to be
registered as extensions in your ORM config. `SchemaGenerator` extension
is registered automatically.
> This is required only for the shortcuts available on `MikroORM`
object, e.g. `orm.migrator.up()`, alternatively you can instantiate the
`Migrator` yourself explicitly.
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
import { Migrator } from '@mikro-orm/migrations';
import { EntityGenerator } from '@mikro-orm/entity-generator';
import { SeedManager } from '@mikro-orm/seeder';
export default defineConfig({
dbName: 'test',
extensions: [Migrator, EntityGenerator, SeedManager], // those would have a static `register` method
});
```
Closes #3743
|
This pull request fixes 2 alerts when merging ae30889 into 59f2e7f - view on LGTM.com fixed alerts:
Heads-up: LGTM.com's PR analysis will be disabled on the 5th of December, and LGTM.com will be shut down ⏻ completely on the 16th of December 2022. Please enable GitHub code scanning, which uses the same CodeQL engine ⚙️ that powers LGTM.com. For more information, please check out our post on the GitHub blog. |
B4nan
added a commit
that referenced
this pull request
Dec 3, 2022
There were some places where we did a static `require()` call, e.g. when
loading the driver implementation based on the `type` option. Those
places were problematic for bundlers like webpack, as well as new school
build systems like vite.
### The `type` option is removed in favour of driver exports
Instead of specifying the `type` we now have several options:
1. use `defineConfig()` helper imported from the driver package to
create your ORM config:
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
export default defineConfig({ ... });
```
3. use `MikroORM.init()` on class imported from the driver package:
```ts title='app.ts'
import { MikroORM } from '@mikro-orm/mysql';
const orm = await MikroORM.init({ ... });
```
5. specify the `driver` option:
```ts title='mikro-orm.config.ts'
import { MySqlDriver } from '@mikro-orm/mysql';
export default { driver: MySqlDriver, ... };
```
> The `MIKRO_ORM_TYPE` is still supported, but no longer does a static
require of the driver class. Its usage is rather discouraged and it
might be removed in future versions too.
### ORM extensions
Similarly, we had to get rid of the `require()` calls for extensions
like `Migrator`, `EntityGenerator` and `Seeder`. Those need to be
registered as extensions in your ORM config. `SchemaGenerator` extension
is registered automatically.
> This is required only for the shortcuts available on `MikroORM`
object, e.g. `orm.migrator.up()`, alternatively you can instantiate the
`Migrator` yourself explicitly.
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
import { Migrator } from '@mikro-orm/migrations';
import { EntityGenerator } from '@mikro-orm/entity-generator';
import { SeedManager } from '@mikro-orm/seeder';
export default defineConfig({
dbName: 'test',
extensions: [Migrator, EntityGenerator, SeedManager], // those would have a static `register` method
});
```
Closes #3743
B4nan
added a commit
that referenced
this pull request
Dec 5, 2022
There were some places where we did a static `require()` call, e.g. when
loading the driver implementation based on the `type` option. Those
places were problematic for bundlers like webpack, as well as new school
build systems like vite.
Instead of specifying the `type` we now have several options:
1. use `defineConfig()` helper imported from the driver package to
create your ORM config:
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
export default defineConfig({ ... });
```
3. use `MikroORM.init()` on class imported from the driver package:
```ts title='app.ts'
import { MikroORM } from '@mikro-orm/mysql';
const orm = await MikroORM.init({ ... });
```
5. specify the `driver` option:
```ts title='mikro-orm.config.ts'
import { MySqlDriver } from '@mikro-orm/mysql';
export default { driver: MySqlDriver, ... };
```
> The `MIKRO_ORM_TYPE` is still supported, but no longer does a static
require of the driver class. Its usage is rather discouraged and it
might be removed in future versions too.
Similarly, we had to get rid of the `require()` calls for extensions
like `Migrator`, `EntityGenerator` and `Seeder`. Those need to be
registered as extensions in your ORM config. `SchemaGenerator` extension
is registered automatically.
> This is required only for the shortcuts available on `MikroORM`
object, e.g. `orm.migrator.up()`, alternatively you can instantiate the
`Migrator` yourself explicitly.
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
import { Migrator } from '@mikro-orm/migrations';
import { EntityGenerator } from '@mikro-orm/entity-generator';
import { SeedManager } from '@mikro-orm/seeder';
export default defineConfig({
dbName: 'test',
extensions: [Migrator, EntityGenerator, SeedManager], // those would have a static `register` method
});
```
Closes #3743
B4nan
added a commit
that referenced
this pull request
Dec 6, 2022
There were some places where we did a static `require()` call, e.g. when
loading the driver implementation based on the `type` option. Those
places were problematic for bundlers like webpack, as well as new school
build systems like vite.
Instead of specifying the `type` we now have several options:
1. use `defineConfig()` helper imported from the driver package to
create your ORM config:
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
export default defineConfig({ ... });
```
3. use `MikroORM.init()` on class imported from the driver package:
```ts title='app.ts'
import { MikroORM } from '@mikro-orm/mysql';
const orm = await MikroORM.init({ ... });
```
5. specify the `driver` option:
```ts title='mikro-orm.config.ts'
import { MySqlDriver } from '@mikro-orm/mysql';
export default { driver: MySqlDriver, ... };
```
> The `MIKRO_ORM_TYPE` is still supported, but no longer does a static
require of the driver class. Its usage is rather discouraged and it
might be removed in future versions too.
Similarly, we had to get rid of the `require()` calls for extensions
like `Migrator`, `EntityGenerator` and `Seeder`. Those need to be
registered as extensions in your ORM config. `SchemaGenerator` extension
is registered automatically.
> This is required only for the shortcuts available on `MikroORM`
object, e.g. `orm.migrator.up()`, alternatively you can instantiate the
`Migrator` yourself explicitly.
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
import { Migrator } from '@mikro-orm/migrations';
import { EntityGenerator } from '@mikro-orm/entity-generator';
import { SeedManager } from '@mikro-orm/seeder';
export default defineConfig({
dbName: 'test',
extensions: [Migrator, EntityGenerator, SeedManager], // those would have a static `register` method
});
```
Closes #3743
B4nan
added a commit
that referenced
this pull request
Dec 8, 2022
There were some places where we did a static `require()` call, e.g. when
loading the driver implementation based on the `type` option. Those
places were problematic for bundlers like webpack, as well as new school
build systems like vite.
Instead of specifying the `type` we now have several options:
1. use `defineConfig()` helper imported from the driver package to
create your ORM config:
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
export default defineConfig({ ... });
```
3. use `MikroORM.init()` on class imported from the driver package:
```ts title='app.ts'
import { MikroORM } from '@mikro-orm/mysql';
const orm = await MikroORM.init({ ... });
```
5. specify the `driver` option:
```ts title='mikro-orm.config.ts'
import { MySqlDriver } from '@mikro-orm/mysql';
export default { driver: MySqlDriver, ... };
```
> The `MIKRO_ORM_TYPE` is still supported, but no longer does a static
require of the driver class. Its usage is rather discouraged and it
might be removed in future versions too.
Similarly, we had to get rid of the `require()` calls for extensions
like `Migrator`, `EntityGenerator` and `Seeder`. Those need to be
registered as extensions in your ORM config. `SchemaGenerator` extension
is registered automatically.
> This is required only for the shortcuts available on `MikroORM`
object, e.g. `orm.migrator.up()`, alternatively you can instantiate the
`Migrator` yourself explicitly.
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
import { Migrator } from '@mikro-orm/migrations';
import { EntityGenerator } from '@mikro-orm/entity-generator';
import { SeedManager } from '@mikro-orm/seeder';
export default defineConfig({
dbName: 'test',
extensions: [Migrator, EntityGenerator, SeedManager], // those would have a static `register` method
});
```
Closes #3743
B4nan
added a commit
that referenced
this pull request
Dec 12, 2022
There were some places where we did a static `require()` call, e.g. when
loading the driver implementation based on the `type` option. Those
places were problematic for bundlers like webpack, as well as new school
build systems like vite.
Instead of specifying the `type` we now have several options:
1. use `defineConfig()` helper imported from the driver package to
create your ORM config:
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
export default defineConfig({ ... });
```
3. use `MikroORM.init()` on class imported from the driver package:
```ts title='app.ts'
import { MikroORM } from '@mikro-orm/mysql';
const orm = await MikroORM.init({ ... });
```
5. specify the `driver` option:
```ts title='mikro-orm.config.ts'
import { MySqlDriver } from '@mikro-orm/mysql';
export default { driver: MySqlDriver, ... };
```
> The `MIKRO_ORM_TYPE` is still supported, but no longer does a static
require of the driver class. Its usage is rather discouraged and it
might be removed in future versions too.
Similarly, we had to get rid of the `require()` calls for extensions
like `Migrator`, `EntityGenerator` and `Seeder`. Those need to be
registered as extensions in your ORM config. `SchemaGenerator` extension
is registered automatically.
> This is required only for the shortcuts available on `MikroORM`
object, e.g. `orm.migrator.up()`, alternatively you can instantiate the
`Migrator` yourself explicitly.
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
import { Migrator } from '@mikro-orm/migrations';
import { EntityGenerator } from '@mikro-orm/entity-generator';
import { SeedManager } from '@mikro-orm/seeder';
export default defineConfig({
dbName: 'test',
extensions: [Migrator, EntityGenerator, SeedManager], // those would have a static `register` method
});
```
Closes #3743
B4nan
added a commit
that referenced
this pull request
Dec 18, 2022
There were some places where we did a static `require()` call, e.g. when
loading the driver implementation based on the `type` option. Those
places were problematic for bundlers like webpack, as well as new school
build systems like vite.
Instead of specifying the `type` we now have several options:
1. use `defineConfig()` helper imported from the driver package to
create your ORM config:
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
export default defineConfig({ ... });
```
3. use `MikroORM.init()` on class imported from the driver package:
```ts title='app.ts'
import { MikroORM } from '@mikro-orm/mysql';
const orm = await MikroORM.init({ ... });
```
5. specify the `driver` option:
```ts title='mikro-orm.config.ts'
import { MySqlDriver } from '@mikro-orm/mysql';
export default { driver: MySqlDriver, ... };
```
> The `MIKRO_ORM_TYPE` is still supported, but no longer does a static
require of the driver class. Its usage is rather discouraged and it
might be removed in future versions too.
Similarly, we had to get rid of the `require()` calls for extensions
like `Migrator`, `EntityGenerator` and `Seeder`. Those need to be
registered as extensions in your ORM config. `SchemaGenerator` extension
is registered automatically.
> This is required only for the shortcuts available on `MikroORM`
object, e.g. `orm.migrator.up()`, alternatively you can instantiate the
`Migrator` yourself explicitly.
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
import { Migrator } from '@mikro-orm/migrations';
import { EntityGenerator } from '@mikro-orm/entity-generator';
import { SeedManager } from '@mikro-orm/seeder';
export default defineConfig({
dbName: 'test',
extensions: [Migrator, EntityGenerator, SeedManager], // those would have a static `register` method
});
```
Closes #3743
B4nan
added a commit
that referenced
this pull request
Dec 27, 2022
There were some places where we did a static `require()` call, e.g. when
loading the driver implementation based on the `type` option. Those
places were problematic for bundlers like webpack, as well as new school
build systems like vite.
Instead of specifying the `type` we now have several options:
1. use `defineConfig()` helper imported from the driver package to
create your ORM config:
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
export default defineConfig({ ... });
```
3. use `MikroORM.init()` on class imported from the driver package:
```ts title='app.ts'
import { MikroORM } from '@mikro-orm/mysql';
const orm = await MikroORM.init({ ... });
```
5. specify the `driver` option:
```ts title='mikro-orm.config.ts'
import { MySqlDriver } from '@mikro-orm/mysql';
export default { driver: MySqlDriver, ... };
```
> The `MIKRO_ORM_TYPE` is still supported, but no longer does a static
require of the driver class. Its usage is rather discouraged and it
might be removed in future versions too.
Similarly, we had to get rid of the `require()` calls for extensions
like `Migrator`, `EntityGenerator` and `Seeder`. Those need to be
registered as extensions in your ORM config. `SchemaGenerator` extension
is registered automatically.
> This is required only for the shortcuts available on `MikroORM`
object, e.g. `orm.migrator.up()`, alternatively you can instantiate the
`Migrator` yourself explicitly.
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
import { Migrator } from '@mikro-orm/migrations';
import { EntityGenerator } from '@mikro-orm/entity-generator';
import { SeedManager } from '@mikro-orm/seeder';
export default defineConfig({
dbName: 'test',
extensions: [Migrator, EntityGenerator, SeedManager], // those would have a static `register` method
});
```
Closes #3743
B4nan
added a commit
that referenced
this pull request
Jan 2, 2023
There were some places where we did a static `require()` call, e.g. when
loading the driver implementation based on the `type` option. Those
places were problematic for bundlers like webpack, as well as new school
build systems like vite.
Instead of specifying the `type` we now have several options:
1. use `defineConfig()` helper imported from the driver package to
create your ORM config:
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
export default defineConfig({ ... });
```
3. use `MikroORM.init()` on class imported from the driver package:
```ts title='app.ts'
import { MikroORM } from '@mikro-orm/mysql';
const orm = await MikroORM.init({ ... });
```
5. specify the `driver` option:
```ts title='mikro-orm.config.ts'
import { MySqlDriver } from '@mikro-orm/mysql';
export default { driver: MySqlDriver, ... };
```
> The `MIKRO_ORM_TYPE` is still supported, but no longer does a static
require of the driver class. Its usage is rather discouraged and it
might be removed in future versions too.
Similarly, we had to get rid of the `require()` calls for extensions
like `Migrator`, `EntityGenerator` and `Seeder`. Those need to be
registered as extensions in your ORM config. `SchemaGenerator` extension
is registered automatically.
> This is required only for the shortcuts available on `MikroORM`
object, e.g. `orm.migrator.up()`, alternatively you can instantiate the
`Migrator` yourself explicitly.
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
import { Migrator } from '@mikro-orm/migrations';
import { EntityGenerator } from '@mikro-orm/entity-generator';
import { SeedManager } from '@mikro-orm/seeder';
export default defineConfig({
dbName: 'test',
extensions: [Migrator, EntityGenerator, SeedManager], // those would have a static `register` method
});
```
Closes #3743
B4nan
added a commit
that referenced
this pull request
Jan 4, 2023
There were some places where we did a static `require()` call, e.g. when
loading the driver implementation based on the `type` option. Those
places were problematic for bundlers like webpack, as well as new school
build systems like vite.
Instead of specifying the `type` we now have several options:
1. use `defineConfig()` helper imported from the driver package to
create your ORM config:
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
export default defineConfig({ ... });
```
3. use `MikroORM.init()` on class imported from the driver package:
```ts title='app.ts'
import { MikroORM } from '@mikro-orm/mysql';
const orm = await MikroORM.init({ ... });
```
5. specify the `driver` option:
```ts title='mikro-orm.config.ts'
import { MySqlDriver } from '@mikro-orm/mysql';
export default { driver: MySqlDriver, ... };
```
> The `MIKRO_ORM_TYPE` is still supported, but no longer does a static
require of the driver class. Its usage is rather discouraged and it
might be removed in future versions too.
Similarly, we had to get rid of the `require()` calls for extensions
like `Migrator`, `EntityGenerator` and `Seeder`. Those need to be
registered as extensions in your ORM config. `SchemaGenerator` extension
is registered automatically.
> This is required only for the shortcuts available on `MikroORM`
object, e.g. `orm.migrator.up()`, alternatively you can instantiate the
`Migrator` yourself explicitly.
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
import { Migrator } from '@mikro-orm/migrations';
import { EntityGenerator } from '@mikro-orm/entity-generator';
import { SeedManager } from '@mikro-orm/seeder';
export default defineConfig({
dbName: 'test',
extensions: [Migrator, EntityGenerator, SeedManager], // those would have a static `register` method
});
```
Closes #3743
B4nan
added a commit
that referenced
this pull request
Jan 8, 2023
There were some places where we did a static `require()` call, e.g. when
loading the driver implementation based on the `type` option. Those
places were problematic for bundlers like webpack, as well as new school
build systems like vite.
Instead of specifying the `type` we now have several options:
1. use `defineConfig()` helper imported from the driver package to
create your ORM config:
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
export default defineConfig({ ... });
```
3. use `MikroORM.init()` on class imported from the driver package:
```ts title='app.ts'
import { MikroORM } from '@mikro-orm/mysql';
const orm = await MikroORM.init({ ... });
```
5. specify the `driver` option:
```ts title='mikro-orm.config.ts'
import { MySqlDriver } from '@mikro-orm/mysql';
export default { driver: MySqlDriver, ... };
```
> The `MIKRO_ORM_TYPE` is still supported, but no longer does a static
require of the driver class. Its usage is rather discouraged and it
might be removed in future versions too.
Similarly, we had to get rid of the `require()` calls for extensions
like `Migrator`, `EntityGenerator` and `Seeder`. Those need to be
registered as extensions in your ORM config. `SchemaGenerator` extension
is registered automatically.
> This is required only for the shortcuts available on `MikroORM`
object, e.g. `orm.migrator.up()`, alternatively you can instantiate the
`Migrator` yourself explicitly.
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
import { Migrator } from '@mikro-orm/migrations';
import { EntityGenerator } from '@mikro-orm/entity-generator';
import { SeedManager } from '@mikro-orm/seeder';
export default defineConfig({
dbName: 'test',
extensions: [Migrator, EntityGenerator, SeedManager], // those would have a static `register` method
});
```
Closes #3743
B4nan
added a commit
that referenced
this pull request
Jan 13, 2023
There were some places where we did a static `require()` call, e.g. when
loading the driver implementation based on the `type` option. Those
places were problematic for bundlers like webpack, as well as new school
build systems like vite.
Instead of specifying the `type` we now have several options:
1. use `defineConfig()` helper imported from the driver package to
create your ORM config:
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
export default defineConfig({ ... });
```
3. use `MikroORM.init()` on class imported from the driver package:
```ts title='app.ts'
import { MikroORM } from '@mikro-orm/mysql';
const orm = await MikroORM.init({ ... });
```
5. specify the `driver` option:
```ts title='mikro-orm.config.ts'
import { MySqlDriver } from '@mikro-orm/mysql';
export default { driver: MySqlDriver, ... };
```
> The `MIKRO_ORM_TYPE` is still supported, but no longer does a static
require of the driver class. Its usage is rather discouraged and it
might be removed in future versions too.
Similarly, we had to get rid of the `require()` calls for extensions
like `Migrator`, `EntityGenerator` and `Seeder`. Those need to be
registered as extensions in your ORM config. `SchemaGenerator` extension
is registered automatically.
> This is required only for the shortcuts available on `MikroORM`
object, e.g. `orm.migrator.up()`, alternatively you can instantiate the
`Migrator` yourself explicitly.
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
import { Migrator } from '@mikro-orm/migrations';
import { EntityGenerator } from '@mikro-orm/entity-generator';
import { SeedManager } from '@mikro-orm/seeder';
export default defineConfig({
dbName: 'test',
extensions: [Migrator, EntityGenerator, SeedManager], // those would have a static `register` method
});
```
Closes #3743
B4nan
added a commit
that referenced
this pull request
Jan 26, 2023
There were some places where we did a static `require()` call, e.g. when
loading the driver implementation based on the `type` option. Those
places were problematic for bundlers like webpack, as well as new school
build systems like vite.
Instead of specifying the `type` we now have several options:
1. use `defineConfig()` helper imported from the driver package to
create your ORM config:
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
export default defineConfig({ ... });
```
3. use `MikroORM.init()` on class imported from the driver package:
```ts title='app.ts'
import { MikroORM } from '@mikro-orm/mysql';
const orm = await MikroORM.init({ ... });
```
5. specify the `driver` option:
```ts title='mikro-orm.config.ts'
import { MySqlDriver } from '@mikro-orm/mysql';
export default { driver: MySqlDriver, ... };
```
> The `MIKRO_ORM_TYPE` is still supported, but no longer does a static
require of the driver class. Its usage is rather discouraged and it
might be removed in future versions too.
Similarly, we had to get rid of the `require()` calls for extensions
like `Migrator`, `EntityGenerator` and `Seeder`. Those need to be
registered as extensions in your ORM config. `SchemaGenerator` extension
is registered automatically.
> This is required only for the shortcuts available on `MikroORM`
object, e.g. `orm.migrator.up()`, alternatively you can instantiate the
`Migrator` yourself explicitly.
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
import { Migrator } from '@mikro-orm/migrations';
import { EntityGenerator } from '@mikro-orm/entity-generator';
import { SeedManager } from '@mikro-orm/seeder';
export default defineConfig({
dbName: 'test',
extensions: [Migrator, EntityGenerator, SeedManager], // those would have a static `register` method
});
```
Closes #3743
B4nan
added a commit
that referenced
this pull request
Feb 5, 2023
There were some places where we did a static `require()` call, e.g. when
loading the driver implementation based on the `type` option. Those
places were problematic for bundlers like webpack, as well as new school
build systems like vite.
Instead of specifying the `type` we now have several options:
1. use `defineConfig()` helper imported from the driver package to
create your ORM config:
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
export default defineConfig({ ... });
```
3. use `MikroORM.init()` on class imported from the driver package:
```ts title='app.ts'
import { MikroORM } from '@mikro-orm/mysql';
const orm = await MikroORM.init({ ... });
```
5. specify the `driver` option:
```ts title='mikro-orm.config.ts'
import { MySqlDriver } from '@mikro-orm/mysql';
export default { driver: MySqlDriver, ... };
```
> The `MIKRO_ORM_TYPE` is still supported, but no longer does a static
require of the driver class. Its usage is rather discouraged and it
might be removed in future versions too.
Similarly, we had to get rid of the `require()` calls for extensions
like `Migrator`, `EntityGenerator` and `Seeder`. Those need to be
registered as extensions in your ORM config. `SchemaGenerator` extension
is registered automatically.
> This is required only for the shortcuts available on `MikroORM`
object, e.g. `orm.migrator.up()`, alternatively you can instantiate the
`Migrator` yourself explicitly.
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
import { Migrator } from '@mikro-orm/migrations';
import { EntityGenerator } from '@mikro-orm/entity-generator';
import { SeedManager } from '@mikro-orm/seeder';
export default defineConfig({
dbName: 'test',
extensions: [Migrator, EntityGenerator, SeedManager], // those would have a static `register` method
});
```
Closes #3743
B4nan
added a commit
that referenced
this pull request
Feb 12, 2023
There were some places where we did a static `require()` call, e.g. when
loading the driver implementation based on the `type` option. Those
places were problematic for bundlers like webpack, as well as new school
build systems like vite.
Instead of specifying the `type` we now have several options:
1. use `defineConfig()` helper imported from the driver package to
create your ORM config:
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
export default defineConfig({ ... });
```
3. use `MikroORM.init()` on class imported from the driver package:
```ts title='app.ts'
import { MikroORM } from '@mikro-orm/mysql';
const orm = await MikroORM.init({ ... });
```
5. specify the `driver` option:
```ts title='mikro-orm.config.ts'
import { MySqlDriver } from '@mikro-orm/mysql';
export default { driver: MySqlDriver, ... };
```
> The `MIKRO_ORM_TYPE` is still supported, but no longer does a static
require of the driver class. Its usage is rather discouraged and it
might be removed in future versions too.
Similarly, we had to get rid of the `require()` calls for extensions
like `Migrator`, `EntityGenerator` and `Seeder`. Those need to be
registered as extensions in your ORM config. `SchemaGenerator` extension
is registered automatically.
> This is required only for the shortcuts available on `MikroORM`
object, e.g. `orm.migrator.up()`, alternatively you can instantiate the
`Migrator` yourself explicitly.
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
import { Migrator } from '@mikro-orm/migrations';
import { EntityGenerator } from '@mikro-orm/entity-generator';
import { SeedManager } from '@mikro-orm/seeder';
export default defineConfig({
dbName: 'test',
extensions: [Migrator, EntityGenerator, SeedManager], // those would have a static `register` method
});
```
Closes #3743
B4nan
added a commit
that referenced
this pull request
Feb 17, 2023
There were some places where we did a static `require()` call, e.g. when
loading the driver implementation based on the `type` option. Those
places were problematic for bundlers like webpack, as well as new school
build systems like vite.
Instead of specifying the `type` we now have several options:
1. use `defineConfig()` helper imported from the driver package to
create your ORM config:
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
export default defineConfig({ ... });
```
3. use `MikroORM.init()` on class imported from the driver package:
```ts title='app.ts'
import { MikroORM } from '@mikro-orm/mysql';
const orm = await MikroORM.init({ ... });
```
5. specify the `driver` option:
```ts title='mikro-orm.config.ts'
import { MySqlDriver } from '@mikro-orm/mysql';
export default { driver: MySqlDriver, ... };
```
> The `MIKRO_ORM_TYPE` is still supported, but no longer does a static
require of the driver class. Its usage is rather discouraged and it
might be removed in future versions too.
Similarly, we had to get rid of the `require()` calls for extensions
like `Migrator`, `EntityGenerator` and `Seeder`. Those need to be
registered as extensions in your ORM config. `SchemaGenerator` extension
is registered automatically.
> This is required only for the shortcuts available on `MikroORM`
object, e.g. `orm.migrator.up()`, alternatively you can instantiate the
`Migrator` yourself explicitly.
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
import { Migrator } from '@mikro-orm/migrations';
import { EntityGenerator } from '@mikro-orm/entity-generator';
import { SeedManager } from '@mikro-orm/seeder';
export default defineConfig({
dbName: 'test',
extensions: [Migrator, EntityGenerator, SeedManager], // those would have a static `register` method
});
```
Closes #3743
B4nan
added a commit
that referenced
this pull request
Feb 17, 2023
There were some places where we did a static `require()` call, e.g. when
loading the driver implementation based on the `type` option. Those
places were problematic for bundlers like webpack, as well as new school
build systems like vite.
Instead of specifying the `type` we now have several options:
1. use `defineConfig()` helper imported from the driver package to
create your ORM config:
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
export default defineConfig({ ... });
```
3. use `MikroORM.init()` on class imported from the driver package:
```ts title='app.ts'
import { MikroORM } from '@mikro-orm/mysql';
const orm = await MikroORM.init({ ... });
```
5. specify the `driver` option:
```ts title='mikro-orm.config.ts'
import { MySqlDriver } from '@mikro-orm/mysql';
export default { driver: MySqlDriver, ... };
```
> The `MIKRO_ORM_TYPE` is still supported, but no longer does a static
require of the driver class. Its usage is rather discouraged and it
might be removed in future versions too.
Similarly, we had to get rid of the `require()` calls for extensions
like `Migrator`, `EntityGenerator` and `Seeder`. Those need to be
registered as extensions in your ORM config. `SchemaGenerator` extension
is registered automatically.
> This is required only for the shortcuts available on `MikroORM`
object, e.g. `orm.migrator.up()`, alternatively you can instantiate the
`Migrator` yourself explicitly.
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
import { Migrator } from '@mikro-orm/migrations';
import { EntityGenerator } from '@mikro-orm/entity-generator';
import { SeedManager } from '@mikro-orm/seeder';
export default defineConfig({
dbName: 'test',
extensions: [Migrator, EntityGenerator, SeedManager], // those would have a static `register` method
});
```
Closes #3743
B4nan
added a commit
that referenced
this pull request
Feb 26, 2023
There were some places where we did a static `require()` call, e.g. when
loading the driver implementation based on the `type` option. Those
places were problematic for bundlers like webpack, as well as new school
build systems like vite.
Instead of specifying the `type` we now have several options:
1. use `defineConfig()` helper imported from the driver package to
create your ORM config:
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
export default defineConfig({ ... });
```
3. use `MikroORM.init()` on class imported from the driver package:
```ts title='app.ts'
import { MikroORM } from '@mikro-orm/mysql';
const orm = await MikroORM.init({ ... });
```
5. specify the `driver` option:
```ts title='mikro-orm.config.ts'
import { MySqlDriver } from '@mikro-orm/mysql';
export default { driver: MySqlDriver, ... };
```
> The `MIKRO_ORM_TYPE` is still supported, but no longer does a static
require of the driver class. Its usage is rather discouraged and it
might be removed in future versions too.
Similarly, we had to get rid of the `require()` calls for extensions
like `Migrator`, `EntityGenerator` and `Seeder`. Those need to be
registered as extensions in your ORM config. `SchemaGenerator` extension
is registered automatically.
> This is required only for the shortcuts available on `MikroORM`
object, e.g. `orm.migrator.up()`, alternatively you can instantiate the
`Migrator` yourself explicitly.
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
import { Migrator } from '@mikro-orm/migrations';
import { EntityGenerator } from '@mikro-orm/entity-generator';
import { SeedManager } from '@mikro-orm/seeder';
export default defineConfig({
dbName: 'test',
extensions: [Migrator, EntityGenerator, SeedManager], // those would have a static `register` method
});
```
Closes #3743
B4nan
added a commit
that referenced
this pull request
Mar 19, 2023
There were some places where we did a static `require()` call, e.g. when
loading the driver implementation based on the `type` option. Those
places were problematic for bundlers like webpack, as well as new school
build systems like vite.
Instead of specifying the `type` we now have several options:
1. use `defineConfig()` helper imported from the driver package to
create your ORM config:
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
export default defineConfig({ ... });
```
3. use `MikroORM.init()` on class imported from the driver package:
```ts title='app.ts'
import { MikroORM } from '@mikro-orm/mysql';
const orm = await MikroORM.init({ ... });
```
5. specify the `driver` option:
```ts title='mikro-orm.config.ts'
import { MySqlDriver } from '@mikro-orm/mysql';
export default { driver: MySqlDriver, ... };
```
> The `MIKRO_ORM_TYPE` is still supported, but no longer does a static
require of the driver class. Its usage is rather discouraged and it
might be removed in future versions too.
Similarly, we had to get rid of the `require()` calls for extensions
like `Migrator`, `EntityGenerator` and `Seeder`. Those need to be
registered as extensions in your ORM config. `SchemaGenerator` extension
is registered automatically.
> This is required only for the shortcuts available on `MikroORM`
object, e.g. `orm.migrator.up()`, alternatively you can instantiate the
`Migrator` yourself explicitly.
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
import { Migrator } from '@mikro-orm/migrations';
import { EntityGenerator } from '@mikro-orm/entity-generator';
import { SeedManager } from '@mikro-orm/seeder';
export default defineConfig({
dbName: 'test',
extensions: [Migrator, EntityGenerator, SeedManager], // those would have a static `register` method
});
```
Closes #3743
B4nan
added a commit
that referenced
this pull request
Apr 6, 2023
There were some places where we did a static `require()` call, e.g. when
loading the driver implementation based on the `type` option. Those
places were problematic for bundlers like webpack, as well as new school
build systems like vite.
Instead of specifying the `type` we now have several options:
1. use `defineConfig()` helper imported from the driver package to
create your ORM config:
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
export default defineConfig({ ... });
```
3. use `MikroORM.init()` on class imported from the driver package:
```ts title='app.ts'
import { MikroORM } from '@mikro-orm/mysql';
const orm = await MikroORM.init({ ... });
```
5. specify the `driver` option:
```ts title='mikro-orm.config.ts'
import { MySqlDriver } from '@mikro-orm/mysql';
export default { driver: MySqlDriver, ... };
```
> The `MIKRO_ORM_TYPE` is still supported, but no longer does a static
require of the driver class. Its usage is rather discouraged and it
might be removed in future versions too.
Similarly, we had to get rid of the `require()` calls for extensions
like `Migrator`, `EntityGenerator` and `Seeder`. Those need to be
registered as extensions in your ORM config. `SchemaGenerator` extension
is registered automatically.
> This is required only for the shortcuts available on `MikroORM`
object, e.g. `orm.migrator.up()`, alternatively you can instantiate the
`Migrator` yourself explicitly.
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
import { Migrator } from '@mikro-orm/migrations';
import { EntityGenerator } from '@mikro-orm/entity-generator';
import { SeedManager } from '@mikro-orm/seeder';
export default defineConfig({
dbName: 'test',
extensions: [Migrator, EntityGenerator, SeedManager], // those would have a static `register` method
});
```
Closes #3743
B4nan
added a commit
that referenced
this pull request
Apr 10, 2023
There were some places where we did a static `require()` call, e.g. when
loading the driver implementation based on the `type` option. Those
places were problematic for bundlers like webpack, as well as new school
build systems like vite.
Instead of specifying the `type` we now have several options:
1. use `defineConfig()` helper imported from the driver package to
create your ORM config:
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
export default defineConfig({ ... });
```
3. use `MikroORM.init()` on class imported from the driver package:
```ts title='app.ts'
import { MikroORM } from '@mikro-orm/mysql';
const orm = await MikroORM.init({ ... });
```
5. specify the `driver` option:
```ts title='mikro-orm.config.ts'
import { MySqlDriver } from '@mikro-orm/mysql';
export default { driver: MySqlDriver, ... };
```
> The `MIKRO_ORM_TYPE` is still supported, but no longer does a static
require of the driver class. Its usage is rather discouraged and it
might be removed in future versions too.
Similarly, we had to get rid of the `require()` calls for extensions
like `Migrator`, `EntityGenerator` and `Seeder`. Those need to be
registered as extensions in your ORM config. `SchemaGenerator` extension
is registered automatically.
> This is required only for the shortcuts available on `MikroORM`
object, e.g. `orm.migrator.up()`, alternatively you can instantiate the
`Migrator` yourself explicitly.
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
import { Migrator } from '@mikro-orm/migrations';
import { EntityGenerator } from '@mikro-orm/entity-generator';
import { SeedManager } from '@mikro-orm/seeder';
export default defineConfig({
dbName: 'test',
extensions: [Migrator, EntityGenerator, SeedManager], // those would have a static `register` method
});
```
Closes #3743
B4nan
added a commit
that referenced
this pull request
Apr 12, 2023
There were some places where we did a static `require()` call, e.g. when
loading the driver implementation based on the `type` option. Those
places were problematic for bundlers like webpack, as well as new school
build systems like vite.
Instead of specifying the `type` we now have several options:
1. use `defineConfig()` helper imported from the driver package to
create your ORM config:
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
export default defineConfig({ ... });
```
3. use `MikroORM.init()` on class imported from the driver package:
```ts title='app.ts'
import { MikroORM } from '@mikro-orm/mysql';
const orm = await MikroORM.init({ ... });
```
5. specify the `driver` option:
```ts title='mikro-orm.config.ts'
import { MySqlDriver } from '@mikro-orm/mysql';
export default { driver: MySqlDriver, ... };
```
> The `MIKRO_ORM_TYPE` is still supported, but no longer does a static
require of the driver class. Its usage is rather discouraged and it
might be removed in future versions too.
Similarly, we had to get rid of the `require()` calls for extensions
like `Migrator`, `EntityGenerator` and `Seeder`. Those need to be
registered as extensions in your ORM config. `SchemaGenerator` extension
is registered automatically.
> This is required only for the shortcuts available on `MikroORM`
object, e.g. `orm.migrator.up()`, alternatively you can instantiate the
`Migrator` yourself explicitly.
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
import { Migrator } from '@mikro-orm/migrations';
import { EntityGenerator } from '@mikro-orm/entity-generator';
import { SeedManager } from '@mikro-orm/seeder';
export default defineConfig({
dbName: 'test',
extensions: [Migrator, EntityGenerator, SeedManager], // those would have a static `register` method
});
```
Closes #3743
B4nan
added a commit
that referenced
this pull request
Apr 26, 2023
There were some places where we did a static `require()` call, e.g. when
loading the driver implementation based on the `type` option. Those
places were problematic for bundlers like webpack, as well as new school
build systems like vite.
Instead of specifying the `type` we now have several options:
1. use `defineConfig()` helper imported from the driver package to
create your ORM config:
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
export default defineConfig({ ... });
```
3. use `MikroORM.init()` on class imported from the driver package:
```ts title='app.ts'
import { MikroORM } from '@mikro-orm/mysql';
const orm = await MikroORM.init({ ... });
```
5. specify the `driver` option:
```ts title='mikro-orm.config.ts'
import { MySqlDriver } from '@mikro-orm/mysql';
export default { driver: MySqlDriver, ... };
```
> The `MIKRO_ORM_TYPE` is still supported, but no longer does a static
require of the driver class. Its usage is rather discouraged and it
might be removed in future versions too.
Similarly, we had to get rid of the `require()` calls for extensions
like `Migrator`, `EntityGenerator` and `Seeder`. Those need to be
registered as extensions in your ORM config. `SchemaGenerator` extension
is registered automatically.
> This is required only for the shortcuts available on `MikroORM`
object, e.g. `orm.migrator.up()`, alternatively you can instantiate the
`Migrator` yourself explicitly.
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
import { Migrator } from '@mikro-orm/migrations';
import { EntityGenerator } from '@mikro-orm/entity-generator';
import { SeedManager } from '@mikro-orm/seeder';
export default defineConfig({
dbName: 'test',
extensions: [Migrator, EntityGenerator, SeedManager], // those would have a static `register` method
});
```
Closes #3743
B4nan
added a commit
that referenced
this pull request
May 14, 2023
There were some places where we did a static `require()` call, e.g. when
loading the driver implementation based on the `type` option. Those
places were problematic for bundlers like webpack, as well as new school
build systems like vite.
Instead of specifying the `type` we now have several options:
1. use `defineConfig()` helper imported from the driver package to
create your ORM config:
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
export default defineConfig({ ... });
```
3. use `MikroORM.init()` on class imported from the driver package:
```ts title='app.ts'
import { MikroORM } from '@mikro-orm/mysql';
const orm = await MikroORM.init({ ... });
```
5. specify the `driver` option:
```ts title='mikro-orm.config.ts'
import { MySqlDriver } from '@mikro-orm/mysql';
export default { driver: MySqlDriver, ... };
```
> The `MIKRO_ORM_TYPE` is still supported, but no longer does a static
require of the driver class. Its usage is rather discouraged and it
might be removed in future versions too.
Similarly, we had to get rid of the `require()` calls for extensions
like `Migrator`, `EntityGenerator` and `Seeder`. Those need to be
registered as extensions in your ORM config. `SchemaGenerator` extension
is registered automatically.
> This is required only for the shortcuts available on `MikroORM`
object, e.g. `orm.migrator.up()`, alternatively you can instantiate the
`Migrator` yourself explicitly.
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
import { Migrator } from '@mikro-orm/migrations';
import { EntityGenerator } from '@mikro-orm/entity-generator';
import { SeedManager } from '@mikro-orm/seeder';
export default defineConfig({
dbName: 'test',
extensions: [Migrator, EntityGenerator, SeedManager], // those would have a static `register` method
});
```
Closes #3743
B4nan
added a commit
that referenced
this pull request
May 14, 2023
There were some places where we did a static `require()` call, e.g. when
loading the driver implementation based on the `type` option. Those
places were problematic for bundlers like webpack, as well as new school
build systems like vite.
Instead of specifying the `type` we now have several options:
1. use `defineConfig()` helper imported from the driver package to
create your ORM config:
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
export default defineConfig({ ... });
```
3. use `MikroORM.init()` on class imported from the driver package:
```ts title='app.ts'
import { MikroORM } from '@mikro-orm/mysql';
const orm = await MikroORM.init({ ... });
```
5. specify the `driver` option:
```ts title='mikro-orm.config.ts'
import { MySqlDriver } from '@mikro-orm/mysql';
export default { driver: MySqlDriver, ... };
```
> The `MIKRO_ORM_TYPE` is still supported, but no longer does a static
require of the driver class. Its usage is rather discouraged and it
might be removed in future versions too.
Similarly, we had to get rid of the `require()` calls for extensions
like `Migrator`, `EntityGenerator` and `Seeder`. Those need to be
registered as extensions in your ORM config. `SchemaGenerator` extension
is registered automatically.
> This is required only for the shortcuts available on `MikroORM`
object, e.g. `orm.migrator.up()`, alternatively you can instantiate the
`Migrator` yourself explicitly.
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
import { Migrator } from '@mikro-orm/migrations';
import { EntityGenerator } from '@mikro-orm/entity-generator';
import { SeedManager } from '@mikro-orm/seeder';
export default defineConfig({
dbName: 'test',
extensions: [Migrator, EntityGenerator, SeedManager], // those would have a static `register` method
});
```
Closes #3743
B4nan
added a commit
that referenced
this pull request
May 24, 2023
There were some places where we did a static `require()` call, e.g. when
loading the driver implementation based on the `type` option. Those
places were problematic for bundlers like webpack, as well as new school
build systems like vite.
Instead of specifying the `type` we now have several options:
1. use `defineConfig()` helper imported from the driver package to
create your ORM config:
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
export default defineConfig({ ... });
```
3. use `MikroORM.init()` on class imported from the driver package:
```ts title='app.ts'
import { MikroORM } from '@mikro-orm/mysql';
const orm = await MikroORM.init({ ... });
```
5. specify the `driver` option:
```ts title='mikro-orm.config.ts'
import { MySqlDriver } from '@mikro-orm/mysql';
export default { driver: MySqlDriver, ... };
```
> The `MIKRO_ORM_TYPE` is still supported, but no longer does a static
require of the driver class. Its usage is rather discouraged and it
might be removed in future versions too.
Similarly, we had to get rid of the `require()` calls for extensions
like `Migrator`, `EntityGenerator` and `Seeder`. Those need to be
registered as extensions in your ORM config. `SchemaGenerator` extension
is registered automatically.
> This is required only for the shortcuts available on `MikroORM`
object, e.g. `orm.migrator.up()`, alternatively you can instantiate the
`Migrator` yourself explicitly.
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
import { Migrator } from '@mikro-orm/migrations';
import { EntityGenerator } from '@mikro-orm/entity-generator';
import { SeedManager } from '@mikro-orm/seeder';
export default defineConfig({
dbName: 'test',
extensions: [Migrator, EntityGenerator, SeedManager], // those would have a static `register` method
});
```
Closes #3743
B4nan
added a commit
that referenced
this pull request
May 26, 2023
There were some places where we did a static `require()` call, e.g. when
loading the driver implementation based on the `type` option. Those
places were problematic for bundlers like webpack, as well as new school
build systems like vite.
Instead of specifying the `type` we now have several options:
1. use `defineConfig()` helper imported from the driver package to
create your ORM config:
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
export default defineConfig({ ... });
```
3. use `MikroORM.init()` on class imported from the driver package:
```ts title='app.ts'
import { MikroORM } from '@mikro-orm/mysql';
const orm = await MikroORM.init({ ... });
```
5. specify the `driver` option:
```ts title='mikro-orm.config.ts'
import { MySqlDriver } from '@mikro-orm/mysql';
export default { driver: MySqlDriver, ... };
```
> The `MIKRO_ORM_TYPE` is still supported, but no longer does a static
require of the driver class. Its usage is rather discouraged and it
might be removed in future versions too.
Similarly, we had to get rid of the `require()` calls for extensions
like `Migrator`, `EntityGenerator` and `Seeder`. Those need to be
registered as extensions in your ORM config. `SchemaGenerator` extension
is registered automatically.
> This is required only for the shortcuts available on `MikroORM`
object, e.g. `orm.migrator.up()`, alternatively you can instantiate the
`Migrator` yourself explicitly.
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
import { Migrator } from '@mikro-orm/migrations';
import { EntityGenerator } from '@mikro-orm/entity-generator';
import { SeedManager } from '@mikro-orm/seeder';
export default defineConfig({
dbName: 'test',
extensions: [Migrator, EntityGenerator, SeedManager], // those would have a static `register` method
});
```
Closes #3743
B4nan
added a commit
that referenced
this pull request
Jun 11, 2023
There were some places where we did a static `require()` call, e.g. when
loading the driver implementation based on the `type` option. Those
places were problematic for bundlers like webpack, as well as new school
build systems like vite.
Instead of specifying the `type` we now have several options:
1. use `defineConfig()` helper imported from the driver package to
create your ORM config:
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
export default defineConfig({ ... });
```
3. use `MikroORM.init()` on class imported from the driver package:
```ts title='app.ts'
import { MikroORM } from '@mikro-orm/mysql';
const orm = await MikroORM.init({ ... });
```
5. specify the `driver` option:
```ts title='mikro-orm.config.ts'
import { MySqlDriver } from '@mikro-orm/mysql';
export default { driver: MySqlDriver, ... };
```
> The `MIKRO_ORM_TYPE` is still supported, but no longer does a static
require of the driver class. Its usage is rather discouraged and it
might be removed in future versions too.
Similarly, we had to get rid of the `require()` calls for extensions
like `Migrator`, `EntityGenerator` and `Seeder`. Those need to be
registered as extensions in your ORM config. `SchemaGenerator` extension
is registered automatically.
> This is required only for the shortcuts available on `MikroORM`
object, e.g. `orm.migrator.up()`, alternatively you can instantiate the
`Migrator` yourself explicitly.
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
import { Migrator } from '@mikro-orm/migrations';
import { EntityGenerator } from '@mikro-orm/entity-generator';
import { SeedManager } from '@mikro-orm/seeder';
export default defineConfig({
dbName: 'test',
extensions: [Migrator, EntityGenerator, SeedManager], // those would have a static `register` method
});
```
Closes #3743
B4nan
added a commit
that referenced
this pull request
Sep 10, 2023
There were some places where we did a static `require()` call, e.g. when
loading the driver implementation based on the `type` option. Those
places were problematic for bundlers like webpack, as well as new school
build systems like vite.
Instead of specifying the `type` we now have several options:
1. use `defineConfig()` helper imported from the driver package to
create your ORM config:
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
export default defineConfig({ ... });
```
3. use `MikroORM.init()` on class imported from the driver package:
```ts title='app.ts'
import { MikroORM } from '@mikro-orm/mysql';
const orm = await MikroORM.init({ ... });
```
5. specify the `driver` option:
```ts title='mikro-orm.config.ts'
import { MySqlDriver } from '@mikro-orm/mysql';
export default { driver: MySqlDriver, ... };
```
> The `MIKRO_ORM_TYPE` is still supported, but no longer does a static
require of the driver class. Its usage is rather discouraged and it
might be removed in future versions too.
Similarly, we had to get rid of the `require()` calls for extensions
like `Migrator`, `EntityGenerator` and `Seeder`. Those need to be
registered as extensions in your ORM config. `SchemaGenerator` extension
is registered automatically.
> This is required only for the shortcuts available on `MikroORM`
object, e.g. `orm.migrator.up()`, alternatively you can instantiate the
`Migrator` yourself explicitly.
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
import { Migrator } from '@mikro-orm/migrations';
import { EntityGenerator } from '@mikro-orm/entity-generator';
import { SeedManager } from '@mikro-orm/seeder';
export default defineConfig({
dbName: 'test',
extensions: [Migrator, EntityGenerator, SeedManager], // those would have a static `register` method
});
```
Closes #3743
B4nan
added a commit
that referenced
this pull request
Sep 20, 2023
There were some places where we did a static `require()` call, e.g. when
loading the driver implementation based on the `type` option. Those
places were problematic for bundlers like webpack, as well as new school
build systems like vite.
Instead of specifying the `type` we now have several options:
1. use `defineConfig()` helper imported from the driver package to
create your ORM config:
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
export default defineConfig({ ... });
```
3. use `MikroORM.init()` on class imported from the driver package:
```ts title='app.ts'
import { MikroORM } from '@mikro-orm/mysql';
const orm = await MikroORM.init({ ... });
```
5. specify the `driver` option:
```ts title='mikro-orm.config.ts'
import { MySqlDriver } from '@mikro-orm/mysql';
export default { driver: MySqlDriver, ... };
```
> The `MIKRO_ORM_TYPE` is still supported, but no longer does a static
require of the driver class. Its usage is rather discouraged and it
might be removed in future versions too.
Similarly, we had to get rid of the `require()` calls for extensions
like `Migrator`, `EntityGenerator` and `Seeder`. Those need to be
registered as extensions in your ORM config. `SchemaGenerator` extension
is registered automatically.
> This is required only for the shortcuts available on `MikroORM`
object, e.g. `orm.migrator.up()`, alternatively you can instantiate the
`Migrator` yourself explicitly.
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
import { Migrator } from '@mikro-orm/migrations';
import { EntityGenerator } from '@mikro-orm/entity-generator';
import { SeedManager } from '@mikro-orm/seeder';
export default defineConfig({
dbName: 'test',
extensions: [Migrator, EntityGenerator, SeedManager], // those would have a static `register` method
});
```
Closes #3743
B4nan
added a commit
that referenced
this pull request
Sep 24, 2023
There were some places where we did a static `require()` call, e.g. when
loading the driver implementation based on the `type` option. Those
places were problematic for bundlers like webpack, as well as new school
build systems like vite.
Instead of specifying the `type` we now have several options:
1. use `defineConfig()` helper imported from the driver package to
create your ORM config:
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
export default defineConfig({ ... });
```
3. use `MikroORM.init()` on class imported from the driver package:
```ts title='app.ts'
import { MikroORM } from '@mikro-orm/mysql';
const orm = await MikroORM.init({ ... });
```
5. specify the `driver` option:
```ts title='mikro-orm.config.ts'
import { MySqlDriver } from '@mikro-orm/mysql';
export default { driver: MySqlDriver, ... };
```
> The `MIKRO_ORM_TYPE` is still supported, but no longer does a static
require of the driver class. Its usage is rather discouraged and it
might be removed in future versions too.
Similarly, we had to get rid of the `require()` calls for extensions
like `Migrator`, `EntityGenerator` and `Seeder`. Those need to be
registered as extensions in your ORM config. `SchemaGenerator` extension
is registered automatically.
> This is required only for the shortcuts available on `MikroORM`
object, e.g. `orm.migrator.up()`, alternatively you can instantiate the
`Migrator` yourself explicitly.
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
import { Migrator } from '@mikro-orm/migrations';
import { EntityGenerator } from '@mikro-orm/entity-generator';
import { SeedManager } from '@mikro-orm/seeder';
export default defineConfig({
dbName: 'test',
extensions: [Migrator, EntityGenerator, SeedManager], // those would have a static `register` method
});
```
Closes #3743
B4nan
added a commit
that referenced
this pull request
Sep 30, 2023
There were some places where we did a static `require()` call, e.g. when
loading the driver implementation based on the `type` option. Those
places were problematic for bundlers like webpack, as well as new school
build systems like vite.
Instead of specifying the `type` we now have several options:
1. use `defineConfig()` helper imported from the driver package to
create your ORM config:
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
export default defineConfig({ ... });
```
3. use `MikroORM.init()` on class imported from the driver package:
```ts title='app.ts'
import { MikroORM } from '@mikro-orm/mysql';
const orm = await MikroORM.init({ ... });
```
5. specify the `driver` option:
```ts title='mikro-orm.config.ts'
import { MySqlDriver } from '@mikro-orm/mysql';
export default { driver: MySqlDriver, ... };
```
> The `MIKRO_ORM_TYPE` is still supported, but no longer does a static
require of the driver class. Its usage is rather discouraged and it
might be removed in future versions too.
Similarly, we had to get rid of the `require()` calls for extensions
like `Migrator`, `EntityGenerator` and `Seeder`. Those need to be
registered as extensions in your ORM config. `SchemaGenerator` extension
is registered automatically.
> This is required only for the shortcuts available on `MikroORM`
object, e.g. `orm.migrator.up()`, alternatively you can instantiate the
`Migrator` yourself explicitly.
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
import { Migrator } from '@mikro-orm/migrations';
import { EntityGenerator } from '@mikro-orm/entity-generator';
import { SeedManager } from '@mikro-orm/seeder';
export default defineConfig({
dbName: 'test',
extensions: [Migrator, EntityGenerator, SeedManager], // those would have a static `register` method
});
```
Closes #3743
B4nan
added a commit
that referenced
this pull request
Oct 2, 2023
There were some places where we did a static `require()` call, e.g. when
loading the driver implementation based on the `type` option. Those
places were problematic for bundlers like webpack, as well as new school
build systems like vite.
Instead of specifying the `type` we now have several options:
1. use `defineConfig()` helper imported from the driver package to
create your ORM config:
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
export default defineConfig({ ... });
```
3. use `MikroORM.init()` on class imported from the driver package:
```ts title='app.ts'
import { MikroORM } from '@mikro-orm/mysql';
const orm = await MikroORM.init({ ... });
```
5. specify the `driver` option:
```ts title='mikro-orm.config.ts'
import { MySqlDriver } from '@mikro-orm/mysql';
export default { driver: MySqlDriver, ... };
```
> The `MIKRO_ORM_TYPE` is still supported, but no longer does a static
require of the driver class. Its usage is rather discouraged and it
might be removed in future versions too.
Similarly, we had to get rid of the `require()` calls for extensions
like `Migrator`, `EntityGenerator` and `Seeder`. Those need to be
registered as extensions in your ORM config. `SchemaGenerator` extension
is registered automatically.
> This is required only for the shortcuts available on `MikroORM`
object, e.g. `orm.migrator.up()`, alternatively you can instantiate the
`Migrator` yourself explicitly.
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
import { Migrator } from '@mikro-orm/migrations';
import { EntityGenerator } from '@mikro-orm/entity-generator';
import { SeedManager } from '@mikro-orm/seeder';
export default defineConfig({
dbName: 'test',
extensions: [Migrator, EntityGenerator, SeedManager], // those would have a static `register` method
});
```
Closes #3743
B4nan
added a commit
that referenced
this pull request
Oct 17, 2023
There were some places where we did a static `require()` call, e.g. when
loading the driver implementation based on the `type` option. Those
places were problematic for bundlers like webpack, as well as new school
build systems like vite.
Instead of specifying the `type` we now have several options:
1. use `defineConfig()` helper imported from the driver package to
create your ORM config:
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
export default defineConfig({ ... });
```
3. use `MikroORM.init()` on class imported from the driver package:
```ts title='app.ts'
import { MikroORM } from '@mikro-orm/mysql';
const orm = await MikroORM.init({ ... });
```
5. specify the `driver` option:
```ts title='mikro-orm.config.ts'
import { MySqlDriver } from '@mikro-orm/mysql';
export default { driver: MySqlDriver, ... };
```
> The `MIKRO_ORM_TYPE` is still supported, but no longer does a static
require of the driver class. Its usage is rather discouraged and it
might be removed in future versions too.
Similarly, we had to get rid of the `require()` calls for extensions
like `Migrator`, `EntityGenerator` and `Seeder`. Those need to be
registered as extensions in your ORM config. `SchemaGenerator` extension
is registered automatically.
> This is required only for the shortcuts available on `MikroORM`
object, e.g. `orm.migrator.up()`, alternatively you can instantiate the
`Migrator` yourself explicitly.
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
import { Migrator } from '@mikro-orm/migrations';
import { EntityGenerator } from '@mikro-orm/entity-generator';
import { SeedManager } from '@mikro-orm/seeder';
export default defineConfig({
dbName: 'test',
extensions: [Migrator, EntityGenerator, SeedManager], // those would have a static `register` method
});
```
Closes #3743
B4nan
added a commit
that referenced
this pull request
Oct 21, 2023
There were some places where we did a static `require()` call, e.g. when
loading the driver implementation based on the `type` option. Those
places were problematic for bundlers like webpack, as well as new school
build systems like vite.
Instead of specifying the `type` we now have several options:
1. use `defineConfig()` helper imported from the driver package to
create your ORM config:
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
export default defineConfig({ ... });
```
3. use `MikroORM.init()` on class imported from the driver package:
```ts title='app.ts'
import { MikroORM } from '@mikro-orm/mysql';
const orm = await MikroORM.init({ ... });
```
5. specify the `driver` option:
```ts title='mikro-orm.config.ts'
import { MySqlDriver } from '@mikro-orm/mysql';
export default { driver: MySqlDriver, ... };
```
> The `MIKRO_ORM_TYPE` is still supported, but no longer does a static
require of the driver class. Its usage is rather discouraged and it
might be removed in future versions too.
Similarly, we had to get rid of the `require()` calls for extensions
like `Migrator`, `EntityGenerator` and `Seeder`. Those need to be
registered as extensions in your ORM config. `SchemaGenerator` extension
is registered automatically.
> This is required only for the shortcuts available on `MikroORM`
object, e.g. `orm.migrator.up()`, alternatively you can instantiate the
`Migrator` yourself explicitly.
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
import { Migrator } from '@mikro-orm/migrations';
import { EntityGenerator } from '@mikro-orm/entity-generator';
import { SeedManager } from '@mikro-orm/seeder';
export default defineConfig({
dbName: 'test',
extensions: [Migrator, EntityGenerator, SeedManager], // those would have a static `register` method
});
```
Closes #3743
B4nan
added a commit
that referenced
this pull request
Oct 25, 2023
There were some places where we did a static `require()` call, e.g. when
loading the driver implementation based on the `type` option. Those
places were problematic for bundlers like webpack, as well as new school
build systems like vite.
Instead of specifying the `type` we now have several options:
1. use `defineConfig()` helper imported from the driver package to
create your ORM config:
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
export default defineConfig({ ... });
```
3. use `MikroORM.init()` on class imported from the driver package:
```ts title='app.ts'
import { MikroORM } from '@mikro-orm/mysql';
const orm = await MikroORM.init({ ... });
```
5. specify the `driver` option:
```ts title='mikro-orm.config.ts'
import { MySqlDriver } from '@mikro-orm/mysql';
export default { driver: MySqlDriver, ... };
```
> The `MIKRO_ORM_TYPE` is still supported, but no longer does a static
require of the driver class. Its usage is rather discouraged and it
might be removed in future versions too.
Similarly, we had to get rid of the `require()` calls for extensions
like `Migrator`, `EntityGenerator` and `Seeder`. Those need to be
registered as extensions in your ORM config. `SchemaGenerator` extension
is registered automatically.
> This is required only for the shortcuts available on `MikroORM`
object, e.g. `orm.migrator.up()`, alternatively you can instantiate the
`Migrator` yourself explicitly.
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
import { Migrator } from '@mikro-orm/migrations';
import { EntityGenerator } from '@mikro-orm/entity-generator';
import { SeedManager } from '@mikro-orm/seeder';
export default defineConfig({
dbName: 'test',
extensions: [Migrator, EntityGenerator, SeedManager], // those would have a static `register` method
});
```
Closes #3743
B4nan
added a commit
that referenced
this pull request
Nov 2, 2023
There were some places where we did a static `require()` call, e.g. when
loading the driver implementation based on the `type` option. Those
places were problematic for bundlers like webpack, as well as new school
build systems like vite.
Instead of specifying the `type` we now have several options:
1. use `defineConfig()` helper imported from the driver package to
create your ORM config:
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
export default defineConfig({ ... });
```
3. use `MikroORM.init()` on class imported from the driver package:
```ts title='app.ts'
import { MikroORM } from '@mikro-orm/mysql';
const orm = await MikroORM.init({ ... });
```
5. specify the `driver` option:
```ts title='mikro-orm.config.ts'
import { MySqlDriver } from '@mikro-orm/mysql';
export default { driver: MySqlDriver, ... };
```
> The `MIKRO_ORM_TYPE` is still supported, but no longer does a static
require of the driver class. Its usage is rather discouraged and it
might be removed in future versions too.
Similarly, we had to get rid of the `require()` calls for extensions
like `Migrator`, `EntityGenerator` and `Seeder`. Those need to be
registered as extensions in your ORM config. `SchemaGenerator` extension
is registered automatically.
> This is required only for the shortcuts available on `MikroORM`
object, e.g. `orm.migrator.up()`, alternatively you can instantiate the
`Migrator` yourself explicitly.
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
import { Migrator } from '@mikro-orm/migrations';
import { EntityGenerator } from '@mikro-orm/entity-generator';
import { SeedManager } from '@mikro-orm/seeder';
export default defineConfig({
dbName: 'test',
extensions: [Migrator, EntityGenerator, SeedManager], // those would have a static `register` method
});
```
Closes #3743
B4nan
added a commit
that referenced
this pull request
Nov 5, 2023
There were some places where we did a static `require()` call, e.g. when
loading the driver implementation based on the `type` option. Those
places were problematic for bundlers like webpack, as well as new school
build systems like vite.
Instead of specifying the `type` we now have several options:
1. use `defineConfig()` helper imported from the driver package to
create your ORM config:
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
export default defineConfig({ ... });
```
3. use `MikroORM.init()` on class imported from the driver package:
```ts title='app.ts'
import { MikroORM } from '@mikro-orm/mysql';
const orm = await MikroORM.init({ ... });
```
5. specify the `driver` option:
```ts title='mikro-orm.config.ts'
import { MySqlDriver } from '@mikro-orm/mysql';
export default { driver: MySqlDriver, ... };
```
> The `MIKRO_ORM_TYPE` is still supported, but no longer does a static
require of the driver class. Its usage is rather discouraged and it
might be removed in future versions too.
Similarly, we had to get rid of the `require()` calls for extensions
like `Migrator`, `EntityGenerator` and `Seeder`. Those need to be
registered as extensions in your ORM config. `SchemaGenerator` extension
is registered automatically.
> This is required only for the shortcuts available on `MikroORM`
object, e.g. `orm.migrator.up()`, alternatively you can instantiate the
`Migrator` yourself explicitly.
```ts title='mikro-orm.config.ts'
import { defineConfig } from '@mikro-orm/mysql';
import { Migrator } from '@mikro-orm/migrations';
import { EntityGenerator } from '@mikro-orm/entity-generator';
import { SeedManager } from '@mikro-orm/seeder';
export default defineConfig({
dbName: 'test',
extensions: [Migrator, EntityGenerator, SeedManager], // those would have a static `register` method
});
```
Closes #3743
B4nan
added a commit
that referenced
this pull request
Nov 26, 2023
This was reintroduced on some bad merge probably, it's no longer needed after #3814.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There were some places where we did a static
require()call, e.g. when loading the driver implementation based on thetypeoption. Those places were problematic for bundlers like webpack, as well as new school build systems like vite.The
typeoption is removed in favour of driver exportsInstead of specifying the
typewe now have several options:defineConfig()helper imported from the driver package to create your ORM config:MikroORM.init()on class imported from the driver package:driveroption:ORM extensions
Similarly, we had to get rid of the
require()calls for extensions likeMigrator,EntityGeneratorandSeeder. Those need to be registered as extensions in your ORM config.SchemaGeneratorextension is registered automatically.Closes #3743