fix: #63

[NguyenDuck]

Correct type declaration in package.json

[rlandav]

Thanks! One piece of feedback.

[lucyydotp]

Hi, hope you don't mind me chiming in here. We've just run into #63 at Noxcrew.

Unlike many teams, we don't bundle our scripts in most situations in order to preserve stack traces and keep output code readable and debuggable without needing to faff with source maps. This obviously means that we need to package dependencies ourselves, which we do by through a node_modules-style copy of every package in the scripts folder, and some generated shims to make exports work nicely.

Which brings me onto my question - would this make more sense as just a simple main and types combo? Using node's exports field feels counterintuitive to me, as it's not something that Minecraft itself supports, meaning that import resolution has to be done ahead-of-time by an external tool (i.e. a bundler, or in our case, a ts transformer plugin). Using exports makes that process considerably more complicated, especially so when a package has conditional exports like this one does, despite being ESM-only.