add es import option in the package exports

[robertIsaac]

as suggested in angular/angular-cli#26888 (comment)

[mmghv]

This will be resolved in v4 when we move away from the default export and rework the build system.

For now you could explicitly import jspdf-autotable/es for the ESM version.

@simonbengtsson What do you think? I suggest leaving this as-is right now so we don't introduce any breaking changes in v3.

[mmghv]

Note: this seems to be an issue only for dynamic imports await import(...), for static import it works just fine import autoTable from 'jspdf-autotable'.

[robertIsaac]

For now you could explicitly import jspdf-autotable/es for the ESM version.

Unfortunately it throw an error
https://github.com/robertIsaac/jspdf-autotable-error-reprod
Here is example

You can read the discussion here
angular/angular-cli#26888 (comment)

[mmghv]

I was able to get it to work after setting module and moduleResolution TS config to nodeNext as mentioned in the thread, I also needed to add type: "module" in package.json.

But without all this, I was able to convert the dynamic import to static import and it worked fine in production, do you really need the dynamic import? this seems to be an issue with esbuild in angular and default exports for CommonJS libs transformed from ESM.

[robertIsaac]

Yeah I need the dynamic import so I don't load the package (along others) unless the user started exporting, this helps a lot with the initial build size

[mmghv]

Have you tried the TS config solution?

[robertIsaac]

Have you tried the TS config solution?

No it will probably cause even more problems but I will try it later today or tomorrow when I have time

[simonbengtsson]

Didn't know about the 'import' option. Added it now now in the v4 branch!