Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for ES Module Resolution #22

Open
joelghill opened this issue May 18, 2023 · 0 comments
Open

Support for ES Module Resolution #22

joelghill opened this issue May 18, 2023 · 0 comments

Comments

@joelghill
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant