No errors for ESM module resolution, while errors are expected about arethetypeswrong.github.io

[andrewbranch]

Here’s that file in the built package: https://unpkg.com/browse/@microlabs/[email protected]/dist/esm/instrumentation/env.d.ts

It doesn’t have any imports.

[andrewbranch]

Ah, I see you must be looking at the JavaScript: https://unpkg.com/browse/@microlabs/[email protected]/dist/esm/instrumentation/env.js

attw is built under the assumption that most immediate runtime crashes would be caught by other means; the tricky thing is getting the types right when the JS build and .d.ts build are decoupled somehow. So, these JS files are not analyzed for broken imports. Usually what we see is a .js file that works and a .d.ts file that disagrees and implies the existence of a .js file that would be broken.

It’s not totally out of the question to expand this analysis, but I’m not sure it really aligns with the goals of the project. attw is never going to be a substitute for basic runtime validation.

[oxcafedead]

I don't possess some deep knowledge in js/ts modules resolution, sorry if this is off-topic.
I've just read about mandatory extension for ESM resolution, but it relates for pure JS:
https://nodejs.org/api/esm.html#mandatory-file-extensions

So, apologies if this is not relevant for this lib. Please close this ticket if you don't see what can be done here further.