The minimum and recommended node versions, v12.x.x and v14.x.x, had reached their end-of-life date( version 14 will reach EOL at the end of this month), references Node Release Schedule. This can mean no new patches will be released and code dependent on it can be exposed to security and performance risks. In addition, the code is using currently the Optional chain operator (field?.innerFieldMightBeNullOrUndefined) that is only available in node versions 13+.
To solve this issue the node version should be upgraded to a newer release, preferably an LTS release(18+).
The minimum and recommended node versions, v12.x.x and v14.x.x, had reached their end-of-life date( version 14 will reach EOL at the end of this month), references Node Release Schedule. This can mean no new patches will be released and code dependent on it can be exposed to security and performance risks. In addition, the code is using currently the
Optional chain operator (field?.innerFieldMightBeNullOrUndefined)that is only available in node versions 13+.To solve this issue the node version should be upgraded to a newer release, preferably an LTS release(18+).