Repository navigation
Console.log crashes node #42697
Description
Version
v16.13.1
Platform
Linux monster 5.13.0-39-generic #44-Ubuntu SMP Thu Mar 24 15:35:05 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Subsystem
No response
What steps will reproduce the bug?
https://github.com/Alwinator/automapper-nestjs-inject-bug
How often does it reproduce? Is there a required condition?
Simply start using npm run start:dev
What is the expected behavior?
That the mapped object is printed to console
What do you see instead?
The following exception:
[Nest] 39779 - 04/11/2022, 5:52:12 PM ERROR [ExceptionHandler] Error: Error: TypeError: Cannot read properties of undefined (reading 'properties')
at Collection.get property [as property] (/home/alwin/WebStormsProjects/node_modules/@mikro-orm/core/entity/ArrayCollection.js:119:44)
at Collection.[nodejs.util.inspect.custom] (/home/alwin/WebStormsProjects/node_modules/@mikro-orm/core/entity/ArrayCollection.js:168:55)
at formatValue (node:internal/util/inspect:763:19)
at formatProperty (node:internal/util/inspect:1681:11)
at formatRaw (node:internal/util/inspect:1006:9)
at formatValue (node:internal/util/inspect:793:10)
at formatProperty (node:internal/util/inspect:1681:11)
at formatArray (node:internal/util/inspect:1508:17)
at formatRaw (node:internal/util/inspect:1003:14)
at formatValue (node:internal/util/inspect:793:10)
This is caused by either a bug in Node.js or incorrect usage of Node.js internals.
Please open an issue with this stack trace at https://github.com/nodejs/node/issues
at new NodeError (node:internal/errors:371:5)
at Function.fail (node:internal/assert:20:9)
at handleMaxCallStackSize (node:internal/util/inspect:1370:10)
at formatRaw (node:internal/util/inspect:1013:12)
at formatValue (node:internal/util/inspect:793:10)
at formatProperty (node:internal/util/inspect:1681:11)
at formatArray (node:internal/util/inspect:1508:17)
at formatRaw (node:internal/util/inspect:1003:14)
at formatValue (node:internal/util/inspect:793:10)
at formatProperty (node:internal/util/inspect:1681:11)
Additional information
No response
Activity
mscdex commentedon Apr 11, 2022
You should raise an issue with the
@mikro-orm/coreproject instead, as its custom inspect implementation is the source of this error.Alwinator commentedon Apr 11, 2022
Moved to mikro-orm/mikro-orm#3001