dnt

A test-only dependency that ships a declaration file (ex. a prebuilt package published to JSR that provides ) was leaking into the published npm package because its was never listed in . The ignore paths were computed with /, whose regex only handles regular source files, so a input produced nonsense paths (, ) that never matched the file the compiler actually emitted. Declaration files aren't compiled to a + pair — the compiler copies them as-is, and only where declarations are emitted (beside the code when inlined, or the directory when separate). Detect declaration test files and emit the correct ignore entries for them. Closes #522

A mapped specifier gets its version requirement from the specifier instead of the mapping, so a dependency requiring another range of the same package looked like two versions of the same package and errored: ...which happened with: Deno resolves both requirements to one version, so use the most restrictive requirement when they overlap. Requirements that don't overlap are different versions of the package, so they still error for the mapping to disambiguate with a of its own—but without leaking the internal scheme into the message.

The dependency sources are being ignored, but not their source maps. There's also: Which is a dev-dependency and were not supposed to be included either. The content: