Dan Vanderkam

I'm not exactly sure how this would work (it would have to be an input but not an output). But it would make it more pleasant to use!

If localturk stuck all its HTML and the first line of the template HTML on the first line of the output, then the line numbers would match up between the...

There's currently an `ALL_TESTS` variable in `checker-logic.ts` that lists the file we want to type check. Better would be to have a directive in the Asciidoc files themselves saying "check...

There's currently some wiggle room to accommodate this pattern: ```ts { longname = 12; // ~~~~~ Cannot find name 'longname'. } ``` That's done by only requiring the end of...

The contents of the `extract.yaml` baselines just include the extracted code samples. They'd be more useful if they also included the extracted error expectations and type assertions.

I make this mistake almost every time I run literate-ts with this flag.

The final "matched 3/3 errors" looks suspicious! ``` matched errors: expected: actual: Object literal may only specify known properties, but 'capitol' does not exist in type 'State'. Did you mean...

If you add or remove a line, you shift the generated IDs of all subsequent code samples. Maybe a content-based hash would work better for literate-ts.

This text in the preface of _Effective TypeScript_ could be checked: ```asciidoc All samples were verified with https://github.com/danvk/literate-ts[literate-ts] using TypeScript 5.3 beta. ``` Maybe something like: ```asciidoc All samples were...

Results of running npx create-typescript-app Fixes #88 Fixes #236 Fixes #242 Issues: - [ ] Deleted Jest config but did not migrate tests - [ ] My [node module resolution...