Keep stats as json instead of JavaScript

Gatling version: 3.13.5
Gatling flavor: java kotlin scala javascript typescript
Gatling build tool: maven gradle sbt bundle npm

I made sure I’ve update my Gatling version to the latest release
I read the guidelines and how to ask a question topics.

Statistics from the run used to be stored in stats.json but are now stored in a js file which is not parsable as JSON. We use the stats.json file as part of our automated analysis of our internal applications. This tooling is written in Java and parsing the JavaScript is way more involved than json. Is it possible to get Gatling to emit the stats as json?

Already answered here: global_stats.json is not generated any more · Issue #4615 · gatling/gatling · GitHub

Well, not really answered though. The answer is about why the Jenkins plugin is discontinued. Stated reason is that there is no maintainer for the Jenkins plugin, it got a CVE, and therefore the plugin was ditched.

That I can understand. But why does it have to mean that instead of a stats.json file that can be used from a whole range of other tooling (including in house like ours) now is a JavaScript file that requires significantly less straightforward code to consume?

Moreover, the other topic has been closed so I could not comment there.