this PR is giving me a surprising amount of grief, which I believe is a tsup bug 😬

• if the cjsInterop is not included in the tsup config:

  • the CJS types don't match the actual function signature (i.e., TS only types fetchHAR if the require statement is const fetchHAR = require('.').default; when the actual JS code will only run if it's const fetchHAR = require('.').default;. this is correctly getting flagged by attw:

    

• if the cjsInterop: truein the tsup config:

  • attempting to run a CJS file with the package loaded via CJS just... doesn't work at all. it seems to be an issue with how tsup is constructing the module.exports — if I comment out the last line in the CJS dist file, it works properly:

    

  • TS appears to be consistent with the typing at least, and attw agrees:

    

feels like a frustrating two-steps-forward-two-steps-back dance here, so I'm going to close this out and I might create an issue in tsup at some point.