Closed kanadgupta closed 1 year ago
hey!
AFAIK, this is a warning right, not an actual error? This used to work for 10 years or so.
Using exports is a technically potentially breaking change, so thatโs a little bit hmmm from me.
An alternative is adding a main: "index.js"
. That should also silence the error, and not prevent anything else from being used if desired
Yes, this is more to address a warning than an actual error. Agree with this assessment โ I'll make that change. Thanks!
@wooorm okay updated!
Hi there! I'm attempting to use the JS API with the latest version (i.e.,
alex@11.0.0
) and I'm seeing the following deprecation warning:Per the docs for
DEP0151
:I figured it was safe to add an
exports
field that points to theindex.js
file, similar to the recommended approach in the Node.js docs.Thanks in advance! Big fan of this project ๐