Monorepo setup with task runners, testing lib and API consistency tools

[lukasIO]

this adds a couple of things:

• turbo as a monorepo task runner
• a root package.json for easy script invocation across the monorepo
• vitest as a testrunner
• rushstack api-extractor to enable CI checks for API consistency (once we need it, too early right now in pre-release)
• eslint+prettier combined setup taken from the components-js repo

TODO:

• add changesets CLI setup (would want to tackle this in a separate PR as this one is already a monster)

[nbsp]

looks okay, a few nits

also if you could add turbo to flake.nix nativeBuildInputs

[nbsp]

is this needed? it's more verbose but i don't know if it helps readability.
either way the REUSE header should be on top

[lukasIO]

this is just a result of the prettier + eslint config applied and running pnpm format:write. REUSE header is still on top, I think?

[nbsp]

it got a bit overzealous and put it on top of REUSE

[lukasIO]

hah, now I see it!

[nbsp]

also once this is ready please give me time to try and rebase this commit history line into something more parseable

[lukasIO]

also once this is ready please give me time to try and rebase this commit history line into something more parseable

generally we do squash-merge commits across all repos AFAIK, so this shouldn't be an issue?

[nbsp]

also once this is ready please give me time to try and rebase this commit history line into something more parseable

generally we do squash-merge commits across all repos AFAIK, so this shouldn't be an issue?

this is a Very big commit to squash, it does a couple of things (parity, testing, turbo, API, general linting).

[lukasIO]

this is a Very big commit to squash, it does a couple of things (parity, testing, turbo, API, general linting).

yeah, sorry about that. It wasn't planned like that at all. It just suddenly grew out of proportion 😬

[lukasIO]

just for context: the idea behind renaming this was to have a standard way of naming agent plugins in the future, following an example of rollup plugin conventions.
There officially maintained plugins are named @rollup/plugin-official-plugin and community plugins should be named rollup-plugin-my-plugin

[lukasIO]

@nbsp do you want to rebase the commits before merging? (I can also do it, just let me know!)

[nbsp]

@lukasIO rebased the whole thing, made sure nothing was lost. let me know if these commits make sense and i'll merge

[lukasIO]

looks great, thank you 🙏