HoseinGhanbari

this can be closed, as the same issue can be fixed by replacing the entire `` with `dbname` `MONGODB_URI_LOCAL=mongodb://localhost:27017/` `MONGODB_URI_LOCAL=mongodb://localhost:27017/dbname`

yeah this is helpful, as people like me might try `cross-env`, `env` or `dotenv` BUT everything is working out of the box in the starter; of course as I couldn't...

A fresh angular 17 project created using `@angular/cli` no longer produces this error. the initial bug report was for `"@tabler/core": "^1.0.0-beta8"` and today's test was for `"@tabler/core": "^1.0.0-beta20"` Happy Coding...

I added the `yarn.lock` which was generated by another machine and the heap error was resolved.

Now that I'm using a custom naming strategy (actually a fixed one based on table, column and field names), the issue still exists with another wired behavior which I think...

Actually found some related issues on TypeORM's official repository, which were opened 2018 and still receiving comments in 2023. Someone found the solution to use `mariadb` type for a `mysql`...

using the `DefaultNamingStrategy` will produces the following statements for the sample FK mentioned above. > migration UP ```sql ALTER TABLE `authentication_method` DROP FOREIGN KEY `FK_00cbe87bc0d4e36758d61bd31d6`; ALTER TABLE `authentication_method` ADD CONSTRAINT...

Hi, That's all right. I will keep this issue updated if found anything new & relevant. Thank you for the great Vendure project 🙏

Hi, This issue happened to me again, the scenario was exactly the same as before. I removed all products, all facets but when came to collections, selected multiple collections and...

"node_modules/angular2-persian-utils/**/*.ts", "node_modules/angular2-persian-pipes/**/*.ts"