What is the motivation or rationale behind making Typebox 1.x ESM only? #1392
Unanswered
shaharkedar
asked this question in
Q&A
Replies: 1 comment
-
|
@shaharkedar Hi, The main reason for going ESM only is because Node 18.x fell out of LTS this year, and 20.x (current LTS) supports ESM resolution from CJS (meaning libraries can publish ESM packages and have them consumed by CJS applications). ESM packages are generally fine consume on newer versions of Node (which is what prompted dropping CJS), but mostly my preference is to only publish for a singular module system, not two, and EcmaScript modules is the Standard, so I just want to publish for that. Hope that brings some insight. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Typebox 1.x is currently ESM only. Is there a reason why there's no dual build for Typebox? I read some issues where ESM and CJS were mentioned, but didn't manage to find a clear answer to that.
Beta Was this translation helpful? Give feedback.
All reactions