-
Notifications
You must be signed in to change notification settings - Fork 170
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
fix: use export in package.json to reference ESM #232
base: master
Are you sure you want to change the base?
Conversation
Thank you, here's hoping this gets merged quickly! |
Hate to be the one doing the "me too" comment, much less to be the annoying one "@-ing people" but the project seems parked and this fix so easy, sorry @MeltingMosaic, @Xapphire13 Bun just launched T.T |
Commenting for visibility. Please merge! |
Please merge! :) |
Please merge! |
Please merge ! |
I fixed ESM thing in my fork: tsyringe-neo. Feel free to use |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thats ok
The
module
field ofpackage.json
has never been officially supported by Node.js (see Stackoverflow).To correctly reference the ESM version, Node.js recommends using the
export
field in thepackage.json
(refer to Node.js ESM documentation).With this change, we also ensure compatibility with bun.