dts-buddy

This lets a consumer fail its build when a type used in a public signature isn't importable, instead of finding out from a user (sveltejs/svelte#18648, ). In , step 2 marks everything reachable from the entry's exports as , but only the declarations traced directly from an export get . Step 3 prints the rest without a modifier and the trailing hides them (#82). That is right for private helper types and wrong when a public type was simply never exported; the output looks the same in both cases, and nothing else reports it. keeps the set of declarations traced from exports and returns the included remainder alongside ; collects them per module and resolves to . asserts the returned value through a new fixture in the harness. Touches the same loop as #134; rebases trivially in either order.

resolves #90 also fixes type-only exports (see the test) added a lot of new tests, but when following imports a bunch of weird and wonderful things can happen along the way the most important test is probably which illustrates the original issue a note on entrypoint order the order in which the entrypoints are processed will affect the output (hence the tests avoid the root index.js which always goes first). specifically, it affects which submodule a shared declaration is exported from. for config via , it's the same order as the field (from top to down), so the idea would be to put more "core" packages earlier so they can claim the export first.