I've just made a fix in my fork: esm-js@8934d33
You can try it with @esm-js/jira.js:

You've made a change in package.json with type: module, but it made your whole package not completely supported by a native CommonJS runtime, I've reverted it

Hey @Arilas! Can you give an example of when this failed? A playground demo would be ideal

@MrRefactoring The easiest way is to:

1. Create a new project
2. set "type": "module" in package.json.
3. Init TypeScript
4. Add jira.js
5. Set in tsconfig.json:

"module": "Node16"

6. Create a new file like "index.ts" and add an import like:

import { Version3Client } from 'jira.js'

7. Observe error from TypeScript.

You can also check the docs about ESM in TypeScript - https://www.typescriptlang.org/tsconfig/#node16node18nodenext
Or from their blog post long ago - https://devblogs.microsoft.com/typescript/announcing-typescript-4-7/#esm-nodejs

@MrRefactoring I've made a very simple demo repository. https://github.com/Arilas/jira-bug-example

You can clone and see the error in IDE or run tsc

Btw, neighbour issue is related to a type: module in your package.json. It thinks that your package is ESM even when trying to load CommonJS bundle. My fix will also will fix this issue, because you will have a separate entries into package for ESM and CommonJS.

@Arilas, could you please test the 5.1.1-dev20250506193213 dev tag?

npm i jira.js@5.1.1-dev20250506193213

@Arilas, could you please test the 5.1.1-dev20250506193213 dev tag?

npm i jira.js@5.1.1-dev20250506193213

FWIW, I ran across this same issue when I tried out version 5.0.0. The 5.1.1-dev20250506193213 tag fixes it for me and allows me to use ESM typings.