Feature request: extract code from examples

[ext]

Add a way to extract all code examples and support running external tools on the code:

• Compile with typescript
• Lint with ESLint

It should include a mechanism to configure such tools, e.g. a way to set which eslint rules to use or the path configuration for typescript.

Given a library my-awesome-lib with a function add(a: number, b: number):

```ts
import { add } from "my-awesome-lib";

const sum = add(1);
```

This example would be compiled with a tsconfig "paths": { "my-awesome-lib": "./dist" } and thus yield an error about missing the second argument to the add function.

Similarly eslint would yield an error about unused variable sum.

If the source is temporary stored on the filesystem the filenames should be traceable to where they originates from, both which file but also which example within that file. Something automagical that does not require explicit tagging. ${basename}-${index}-${hash}.${lang}?

There should be an override to prevent examples to be extracted, e.g.:

```ts nocompile
```

Should be language agnostic but preferably configurable which langauges to extract, possibly even map them to extensions:

Hypotetical processor:

extractExamplesProcessor({
    outdir: "docs/examples",
    languages: ["ts", "vue"],
}),

Where docs/examples contains a tsconfig.json but is otherwise gitignored and a postbuild script runts tsc -b docs/examples. Eslint runs as usual.

This is a major showstopper for migration for my projects.