The AdminJs team seems to be aware of this issue.

It seems it's likely caused by Nest v11. You can start your project with Nest v10 or subscribe to the issue and wait for a patch.