The maintenance of this project is dead, needs official fork

[davissimo]

Is your feature request related to a problem? Please describe.

Hi all,

It seems that this project is no longer maintained, and has been so for over 6 months. Last PR merges and commits end in March, and ever since all issues and PRs have remained open.

It's especially a problem with Nest 10 having been released since, adding incompatibility and bugs with the project. Furthermore, apart from @nartc no-one has permission on the repository. Unfortunately he's been gone since this post in March, which blocks merging fixes and features from the community.

There are different forks that each fix a separate issue but I propose we choose an "official" one, with multiple maintainers added, to continue and maintain the project by the community.

Describe the solution you'd like

Are there candidates in both a stable fork as a base, and maintainers that'd want to volunteer?

[brdar]

I can do some work but it should be a group effort, like foundation. It should not be on the back of one single person.

I made a fork (https://github.com/brdar/mapper-js) and new packages: https://www.npmjs.com/package/automapper-core https://www.npmjs.com/package/automapper-classes https://www.npmjs.com/package/automapper-pojos https://www.npmjs.com/package/automapper-sequelize https://www.npmjs.com/package/automapper-nestjs https://www.npmjs.com/package/automapper-mikro

All tests are passing, nestjs package has been updated for nest 10. Infinite depth bug has been fixed for circular mappings.

Also note that automapper uses some unique symbols which makes packages absolutely dependant by import, which means its not possible to use them from mixed sources. Hope this helps. If anyone wants to assist in maintaining this project please let me know and I will add you to repo.

[mattvgm]

Thanks for your work @brdar , that helps a lot. @nartc are you still around? Maybe you can merge this one? Or give permissions to someone? please