Open HaTiIn opened 4 months ago
We have decided to do ES-module javascript only on this library.
What is your use case?
That is a pity. I have already tried to migrate my application to ESM. After several days I gave up because there were so many hurdles for which I could not find a solution. Many other developers seem to have had the same experience if you look at the daily downloads of “ESM”-only modules. From my point of view, CommonJS is the standard used in NodeJS.
and the support for using dynamic import to load es-modules from commonjs will not help you here?
I tried several fixes, but it ends in ERR_REQUIRE_ESM. If I manage to load the qlik-ap-ts module, then it fails with one of its dependencies: nanoid.
@HaTiIn .. coming back to this. In your ES-module update journey. Was it only @qlik/api
that gave you these issues?
The nano-id issue can be fixed by bundling the code from that specific dependency.
Was it only @qlik/api that gave you these issues?
Yes. I solved it by forking your project and babel it to CommonJS with nano-id 3.
so would it help you to have the nano-id code bundled inside @qlik/api
?
no
Hi,
could you please release this module as a CommonJS module, i.e. with the help of "dual-publish" ?
Best regards, Hans