Maksim Sinik

Oh. This could be a problem, and we should find a solution. @brettwillis, we export default (and map it in JS code) to support every environment, bundler, and compiler out...

@climba03003 I am starting to think that the era of the "famous triplet" is over. If so, we should update all of our types accordingly. As far as I understood...

After further discussion with @climba03003 and basic repro on my machine, I would not like to make these types CJS (aka using `export =` syntax with the namespace). We should...

P.S. I still want to see a repro repo here because I am unsure about the fix. @brettwillis would you mind providing it, please?

@mcollina yes, this was the playground that allowed us to discover that triplet https://github.com/fox1t/modules-playground I am updating it with the new information, replacing the part that says to use `export...

@mcollina and @climba03003 I've updated the playground https://github.com/fox1t/modules-playground We have the winner, the "infamous triplet with namespace types". ```js fastify.fastify = fastify; fastify.default = fastify; module.exports = fastify ``` ```ts...

I agree that introducing them would be awesome! I'll be glad to review the related PR in the future!

I think this is a really nice feature, however we are going to implement it in a second phase. Do you have any experience working on this?

OK. The one and only thing that bothers me now is the fact that this feature needs provide a custom skeleton for wide range of content: list vs details vs...

For sure! We are going to leave this issue here as a reminder