Why are we not generating the .medusa/types folder in production mode ?

[adevinwild]

Hi team!

I have a quick question. I was wondering why we aren't generating the types when executing the ⁠medusa build command? With ⁠medusa develop, we've been getting type inference for Custom Modules since [version 2.5.0] (https://github.com/medusajs/medusa/releases/tag/v2.5.0) (not sure about the version level though), which allows us to avoid explicitly casting custom services used elsewhere.

// ℹ️ Before V2.5.0, we were used to explicitly cast modules like this

import { BLOG_MODULE } from "../../modules/blog"
import type BlogModuleService from "../../modules/blog/service"

// ...
const blogModuleService = container.resolve<BlogModuleService>(BLOG_MODULE) 

// ✅ After V2.5.0, we can count on the `modules-bindings.d.ts` file type inference to get the right type

import { BLOG_MODULE } from "../../modules/blog"

// ...
const blogModuleService = container.resolve(BLOG_MODULE)

---

However, when building for production, if the necessary .medusa/types folder hasn't been generated beforehand, we might encounter a build error because the type won't be resolved, potentially leading to a TypeScript build error due to the unknown type returned by the container.resolve

Just wanted to know the reasoning behind this and what about having some new CLI options to generate the types, to make sure to continue to offer this improvement at the DX level without it being ultimately punished at the time of the build in prod

[thetutlage]

Hello @adevinwild

Yes, this has to be fixed. Lemme look into it in the coming days 💪

[adevinwild]

So cool! Thanks for replying so quickly, good luck with that! 💪

[mvarchdev]

Hey! Looking forward for this! Created also #12677

[mvarchdev]

@thetutlage Hello! What is the status of this? We would need this really urgently. We are currently trying to implement it by ourselves, but no luck so far...