JS Runtime Errors in QA — "use strict" in Bundled Output Causing Serenity Form Assignment Failures

[adarshshukla97]

Environment

"use strict" in DPWBooking.Web.js -> Local : No, QA : Yes
Errors Observed in Console -> Local : None, QA : Multiple

Issue

Suddenly in QA, multiple JS runtime errors are surfacing across dialogs. All errors are strict mode violations — code that silently fails in non-strict JS but throws TypeError in strict mode.

Errors

Uncaught TypeError: Cannot set property Consolidations of #
which has only a getter
at ShipmentsDialog.assignPackingsFromEntity

Uncaught TypeError: 'caller', 'callee', and 'arguments' properties may not be
accessed on strict mode functions
at CommonNumberFormatter.setCommonDecimalFormat

Getting JS strict mode runtime errors on QA after today's deployment — the QA bundle DPWBooking.Web.js has "use strict" at the top but our local bundle does not, even with the same code and tsconfig.json. Has anyone faced this before or know what could cause this difference? Not sure if this "use strict" is the actual issue or something else but if anyone could help in this that would be really appreciated.

[volkanceylan]

You are probably using a very very old version, and have different TypeScript versions in QA / local.