You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Your library is published with "type": "module and your telnyx.node.js is built in ECMAScript module format, but it makes your library hard to use in classic node.js application that uses commonjs module import (wich is the most). It forces us to use const telnyx = await import('telnyx') syntax, which is super inconvenient. I understand your willing to build a new modern library that will work only with new applications that are built in ESM format, but the reality is different and the most node.js application still uses require syntax.
May we ask you to consider changing the package.json "type" to a more classic "commonjs" that will allow anyone to use your library comfortably?
The text was updated successfully, but these errors were encountered:
Thank you for bringing this up. We’ll review internally and assess whether it's a possible consideration for supporting CommonJS with our new SDK version. We’ll follow up with any updates as soon as they are received.
We were moving forward with "type": "module" because ECMAScript module is the default for Node. I can set it to commonjs if it’s a common request from users. We'll let you know once a new version is available
Your library is published with
"type": "module
and yourtelnyx.node.js
is built inECMAScript module
format, but it makes your library hard to use in classic node.js application that uses commonjs module import (wich is the most). It forces us to useconst telnyx = await import('telnyx')
syntax, which is super inconvenient. I understand your willing to build a new modern library that will work only with new applications that are built in ESM format, but the reality is different and the most node.js application still usesrequire
syntax.May we ask you to consider changing the package.json
"type"
to a more classic"commonjs"
that will allow anyone to use your library comfortably?The text was updated successfully, but these errors were encountered: