rat-matheson

Angular 13 removed CommonJS outputs so libraries created with it only use ES modules. I have some custom angular libraries that I share with the backend and frontend and due...

Any idea why this PR is blocked? Is there anything that can help move it along?

As an alternative option, would it be possible to update the documentation to include a method of converting ES modules to commonjs so that they can be used by nestjs...

Thanks for considering it. We understand that maintenance is an issue and certainly appreciate all the hard work that has been done to make nestjs the wonderful tool that it...

At the time I was having the issue, I can't remember if I tried that or not so perhaps that was all I needed to do. I know I never...

For me, it was angular 13 where I first noticed it ([release notes](https://dsebastien.net/blog/2021-11-05-angular-13-in-depth)). The dropped support for commonjs and only build .mjs format. I share some logic & models between...

@rubiin > Having issues on my case as well with packages like `graphql-upload` and `nanoid`. Nanoid is not that important tbh but grapql-upload has recently moved to ESM and i...

At this point, I'm thinking it is probably better to build a control for my own needs. My plan is to just define cards and put those inside a div...

Thanks so much for taking a look at this. I've updated the nest application repository ( [nest-mikro-bug](https://github.com/rat-matheson/nest-mikro-bug/) ) to use the paths config in the tsconfig.json rather than the private...

I tried something new. I built with nest, but than did the following: * installed [module-alias](https://www.npmjs.com/package/module-alias) so I could more clearly specify which bundle I wanted to use * ran...