Maximum Call Stack Size error after migrating to v8

[FurqanAthar]

Is there an existing issue for this?

• [X] I have searched the existing issues

Describe the issue

After upgrading Automapper to v8 and fixing all the breaking changes, my application is returning error of maximum call stack size at ApplyMetaData.

My jest unit tests are also not running and returning mapping between class A and class B cannot be found error even though there are mappings present and injected as well.

See image below of the code.

The mapper returned by the createMapper is not actually the empty proxy and produces the below error when running tests.

Models/DTOs/VMs

No response

Mapping configuration

No response

Steps to reproduce

No response

Expected behavior

It should return the mapper instance and not give maximum call stack error and should get the mapping as defined.

Screenshots

No response

Minimum reproduction code

No response

Package

• [ ] I don't know.
• [X] code>@automapper/core</code
• [X] code>@automapper/classes</code
• [X] code>@automapper/nestjs</code
• [ ] code>@automapper/pojos</code
• [ ] code>@automapper/mikro</code
• [ ] code>@automapper/sequelize</code
• [ ] Other (see below)

Other package and its version

No response

AutoMapper version

8.7.7

Additional context

Linux Node v14.18.1

[brdar]

I'm observing the same behavior when upgraded to 8.7.7

[brdar]

https://github.com/nartc/mapper/issues/575#issuecomment-1772438855

[Imunal]

Anyone figure it out? I'm having the same problem, and i don't know is this library related, or i fucked something up.