Needing to call AbacatePay.default and not AbacatePay when using JS

[ChristoPy]

We where live with a client that was having issues integrating. Turns out they where using a pure JS nextjs backend.

In the end, we had to change the code from the snippet in our doc from:

import AbacatePay from 'abacatepay-nodejs-sdk';

// Initialize the SDK with your API key
const abacate = AbacatePay('your_api_key');

to:

import AbacatePay from 'abacatepay-nodejs-sdk';

// Initialize the SDK with your API key
const abacate = AbacatePay.default('your_api_key');

The VSCode was not showing the autocompletions correctly from the AbacatePay import, when console.log the import, this was the result:
{AbacatePayError, default}

[kayooliveira]

Hi!

I’ve created a PR that addresses the issue you're facing with the default import. The solution suggests switching to named imports instead of using the default export.

If the maintainers decide to accept this change, the updated way to use the SDK would be:

import { AbacatePay } from 'abacatepay-nodejs-sdk';

// Initialize the SDK with your API key
const abacate = AbacatePay('your_api_key');

Benefits of this change:

• Clarity: Named imports help clarify which exports are being used, which can reduce confusion, especially when a module has multiple exports.
• Autocomplete Support: Named imports provide better autocompletion in code editors like VSCode, as you’ve mentioned encountering issues with that.
• Consistency: Named imports are aligned with modern JavaScript/TypeScript practices and help make the SDK more modular and easier to use.
• Future-Proofing: By moving to named exports, the SDK will be easier to maintain and update, avoiding breaking changes related to default exports.

I hope this helps, and if any of the maintainers decide to move forward with the change, feel free to reach out for any further clarification!