Also handle imports deep imports from libraries?

[CarsonF]

This might be my missing link to actually adopt ESM, so thank you for that.

I'm wondering if you think it's possible to also handle library imports. Something like

import { isPlainObject } from '@nestjs/common/utils/shared.utils';

Adding the extension to that import fixes it.
Maybe that's harder though logically, because there's package.json exports to consider. Or some other complication with non-local code?

[barhun]

I think it's better to not modify the default package resolution behavior for the reasons mentioned below:

Why deep imports can be a problem

Deep imports for dual packages presents a problem for transpiling for dual-packages

[CarsonF]

Yeah makes sense 👍

[barhun]

Have you considered using subpath imports instead?

[CarsonF]

Was not aware of that. Good to know. But many of these imports are only done once, so a separate mapping isn't worth it.

[barhun]

You might wanna give it a try with the latest version of the npm package. (: