fix: resolve imports manually

[wellwelwel]

Resolves a common conflict when the same file has multiple import types for both ESM and CJS.

[HappyZombies]

@wellwelwel this ended up being a breaking change for how I was using the module.

version 1.0.0, I had this

const { ca: awsCa } = require('aws-ssl-profiles').default;

With version 1.1.1, I get this error now.

const { ca: awsCa } = require('aws-ssl-profiles').default; 

const {ca: awsCaBundle} = require('aws-ssl-profiles').default;
           ^

TypeError: Cannot destructure property 'ca' of 'require(...).default' as it is undefined.

[wellwelwel]

Hi @HappyZombies, thanks for the report. I'll take a look at it.

In theory, this should work:

aws-ssl-profiles/src/index.ts

Line 13 in d8f28d3

exports.default = profiles;

But unfortunately, there are several bugs when using both CSJ and ESM with different export forms in the same file.

If this can't be resolved, I think it would be better to release a v2 using only named exports.

[HappyZombies]

Ah I see, I think simply adding:

module.exports.default = profiles;

Should fix this for it to be non breaking change, no?