Sebastian Rindom

Hi @maxpanakov! Thanks for contributing - we would be happy to accept a PR for this. Here are a couple of things to make sure are covered: - DiscountConditions on...

@maxpanakov - we place data migration scripts here: https://github.com/medusajs/medusa/tree/master/packages/medusa/src/scripts It is then the user's responsibility to run the script after they have upgraded; we will include this step in the...

@SGFGOV - would you be interested in publishing this separately from the monorepo? We are working on building out a plugins page on the website where we could feature this...

Thanks for reporting - does this happen after calling a specific endpoint or does it reach the OOM simply after running for a while?

Most of the production setups we have been involved in run on Node 14 or 16. Do you know what the max-old-space-size is set to? I believe that Node defaults...

@AlexDigital974 this is super insightful - my immediate thought is that it has something to do with `fakeredis` not being configured correctly. Will try to play around with this -...

## DoD - [ ] When `dry_run: true` ProductImportStrategy should first move BatchJob to an `awaiting_confirmation` state before importing data. ```js // pre-confirmation.json [ { operation: "create", type: "product", data:...

There is an additional reason for creating `findWithRelations`. We encountered OOM errors when the default TypeORM query, could imagine the reason being that there was an enormous amount of data...

Would this not be best handled by the infrastructure e.g. a load balancer or similar?

This is likely because there is a mismatch between installations of `medusa-interfaces`. In your Medusa project try reinstalling and restart: ``` $ yarn add medusa-interfaces $ yarn start ```