more details on .swcrc configuration module.lazy property?

[StefanZivkovic]

@swc/core: 1.3.52
@swc/jest: 0.2.26

I am testing @swc with jest tests, instead of ts-jest. While passing with ts-jest, some tests fail with @swc/jest.
I noticed that .swcrc module property values "lazy": true and "lazy": false produce different output in some cases.

"lazy": true

One of the failures is TypeError: Reflect.getMetadata is not a function.
The issue is with decorator usage @Type(()=>Number).

import { Type } from 'class-transformer';
export class ClassDto {
  @Type(() => Number)
  tenantId: number;
}

I have multiple classes having this usage, but it fails on only few places, and not on all class with same/similar usage of @Type decorator - it is something which bothers / confuses me.
I do not have import 'reflect-metadata'; anywhere in my code base.

"lazy": false

This time, previous error Reflect.getMetadata is not a function disappears, while reported issue is ReferenceError: Cannot access 'Product' before initialization. And while this is because of circular dependencies between two entities, it is fine with details how to work-around it in #5047.

Questions / Concerns:

What value is way to go for lazy property in .swcrc configuration? Or maybe better question is: which value should be avoided in most of the cases? Or it depends?

What is best combination to stick with - "lazy": false and use typeorm Relation work-around circular dependencies?

.swcrc

{
    "jsc": {
      "target": "es2017",
      "parser": {
        "syntax": "typescript",
        "decorators": true,
        "dynamicImport": true
      },
      "transform": {
        "legacyDecorator": true,
        "decoratorMetadata": true
      }
    },
    "module": {
	"type": "commonjs",
	"strict": true,
	"strictMode": false,
	"lazy": true,
	"noInterop": false
     },
    "sourceMaps": true
}