[BUG] Using `NotificationRequest` throws a `TypeError: NotificationRequest is not a constructor`

[romulovalez]

Describe the bug
Using NotificationRequest throws a TypeError: NotificationRequest is not a constructor

It's a type issue, It seems like NotificationRequest generated type is wrong and don't support its use on ESM modules properly

To Reproduce

import NotificationRequest from '@adyen/api-library/lib/src/notification/notificationRequest';

console.log(new NotificationRequest({ live: 'false', notificationItems: [] }));

Execute it with npx tsx script.ts

Expected behavior

It should work and show { notificationItemContainers: [], live: 'false' } but it's throwing this error:

console.log(new NotificationRequest({ live: 'false', notificationItems: [] }));
            ^


TypeError: NotificationRequest is not a constructor
    at <anonymous> (/script.ts:4:13)
    at ModuleJob.run (node:internal/modules/esm/module_job:234:25)
    at async ModuleLoader.import (node:internal/modules/esm/loader:473:24)
    at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:122:5)

Node.js v20.18.1

I workaround with this:

import NotificationRequestWronglyTyped from '@adyen/api-library/lib/src/notification/notificationRequest';

// @ts-expect-error this NotificationRequest type is wrong
const NotificationRequest = NotificationRequestWronglyTyped.default as unknown as typeof NotificationRequestWronglyTyped;

console.log(new NotificationRequest({ live: 'false', notificationItems: [] }));

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: MacOS Sequoia 15.3 (24D60)
• Node Version: 20.18.1
• NPM Version: pnpm@10.0.0

Additional context
Add any other context about the problem here.

[ayodejidev]

Hi @romulovalez,

Thanks for reporting this issue. I followed the steps you provided but was unable to reproduce the error. I'm getting the expected output:
{ notificationItemContainers: [], live: 'false' }.

Could you share the version of the Node API library you're currently using?

Also, you can try cloning the repository and running this test locally to see if the issue persists on your end.

[github-actions]

This issue has been automatically marked as stale due to inactivity and will be closed in 7 days if no further activity occurs.

[github-actions]

This issue was closed due to inactivity. Please reopen if you still encounter this problem or have more information to add.

[romulovalez]

Sorry!, I was out for a bit

Tested with latest version 26.1.0 and still persists, this error depends if the file is inside an ESM workspace or not (type: "module" inside package.json),
Can't reproduce it with your jest test suite because of their bad ESM support.

Another way to test this reliably on workspaces that are not ESM is executing the example with this other command: npx tsx script.js, note that we're executing a js file, in this case it will execute it, but if you change the extension to .mjs (ESM): npx tsx script.mjs it will throw the error