Types unresolvable in `@bugsnag/electron` since v7.23.0

[mark-dr]

TypeScript fails to resolve types, causing tsc failures. Error:

Could not find a declaration file for module '@bugsnag/electron'. '[REDACTED]/node_modules/@bugsnag/electron/src/notifier.js' implicitly has an 'any' type.
There are types at '[REDACTED]/node_modules/@bugsnag/electron/types/notifier.d.ts', but this result could not be resolved when respecting package.json "exports". The '@bugsnag/electron' library may need to update its package.json or typings.

It's because you've provided an exports package.json field but it doesn't export the types file - should be a very small fix.

✔️ (7.22.7): https://arethetypeswrong.github.io/?p=%40bugsnag%2Felectron%407.22.7
❌ (7.23.0): https://arethetypeswrong.github.io/?p=%40bugsnag%2Felectron%407.23.0

EDIT: I just saw you've had a community PR to fix this since a year ago: #2184. You've published several versions since that submission - maybe it'd be worth merging it so TypeScript users can use them? (we're stuck on 7.22.7 until you fix this)

[hannah-smartbear]

Hi @mark-dr,

As my colleague Yousif mentioned, The PR with a fix highlighted some wider issues with the separate main and renderer exports for this package, particularly for projects using ESM, that are being addressed together.

I want to assure you that this is being addressed, and we recommend that you continue to keep an eye on #2184 for any communication on updates.

[mark-dr]

@hannah-smartbear, you've closed this as "completed" but the latest version of @bugsnag/electron (8.4.0) still exhibits this problem. I understand if you don't want to merge the PR I linked, but surely this issue should be kept open until your releases are TypeScript-compatible?

[mark-dr]

For context, my main concern is that you're currently using (and dangerously patching) Electron's deprecated Session.setPreloads API (see here). At some point that API will be removed, and you'll presumably publish a new version of @bugsnag/electron that uses registerPreloadScript instead, but I won't be able to update to it because of these typings issues.

At that point, my options will be:

• Patch your package locally
• Stay on an old Electron version
• Stop using Bugsnag

[hannah-smartbear]

Hi @mark-dr,

Thanks for highlighting this. Just wanted to let you know that we now have a PR that addresses both these issues: #2524

[mark-dr]

That was fast! Thank you, @hannah-smartbear and @gingerbenw!