Not sure if there has been much talk about this amongst the bsky team, but I'm wondering if people are open to using ES Module resolution over CommonJs?
From my (limited) understanding, ES Modules are the official standard, they are now supported by Node.js, and newer libraries are dropping support for CommonJs.
It's not difficult to make the switch in my own fork, but I do find myself updating the imports in all of the auto-generated files and it feels wrong.
This would also be less of an issue of the lexicon was a published package rather than a copy and paste.
Not sure if there has been much talk about this amongst the bsky team, but I'm wondering if people are open to using ES Module resolution over CommonJs?
From my (limited) understanding, ES Modules are the official standard, they are now supported by Node.js, and newer libraries are dropping support for CommonJs.
It's not difficult to make the switch in my own fork, but I do find myself updating the imports in all of the auto-generated files and it feels wrong.
This would also be less of an issue of the lexicon was a published package rather than a copy and paste.