I modified the original change request from @candrews so that now the tsconfig default value is used,
which is the same as he intended to use.
This way we have less customs and have the desired outcome.

thanks for the improvement, @candrews .
looking forward to having it released in the next days.

@candrews

I got the impression, that you are running your own webpack process on the source code of this project.
If so: Could you elaborate why you are re-compiling this library downstream ? It is already in a compiled version available, right?

Or is this not because of recompiling but usage of a TypeScript code that uses import foo from 'bar'??

Some background: I want to incorporate a better SPDX license expression validation process. Therefore, I wanted to utilize a module which requires esModuleInterop to be enabled, again.

Caused by #271

Might need to reopen this, to get https://www.npmjs.com/package/spdx-expression-parse in
This package exports like module.exports = function () {}
which requires the usage like import foo from 'bar'.
And this requires to enable esModuleInterop to be enabled.

Having esModuleInterop not enabled was the purpose of this PR.

So the new code would revert this PR. :-/
any advice, @candrews

see https://github.com/CycloneDX/cyclonedx-javascript-library/pull/547/files#r1136676122

Could you elaborate why you are re-compiling this library downstream ? It is already in a compiled version available, right?

I'm using it in my fork of Snyk CLI that generates CycloneDX SBOMs: https://github.com/candrews/snyk-cli

Here's the PR to the Snyk project which shows exactly the changes in my fork: snyk/cli#3983

This library is imported using:
import * as cdx from '@cyclonedx/cyclonedx-library';

Ah, I remember. Thanks.

So all good, as long as the type declarations consumed downstream do not require esModuleInterop nor allowSyntheticDefaultImports?