CI

[griff-rees]

• [x] Automate testing across both packages (see 846b6c765ac8896268344aafec7a4c2aefd6fd41)
• [x] Add some pre-commit-hooks
  • prettier-precommit suggests either husky or pre-commit)
  • Given we'll also use a python backend, thought pre-commit a better shout
  • But there are issues with prettier: https://github.com/prettier/prettier/issues/15742
• [x] Set up a github-actions (eyeing: https://github.com/marketplace/actions/setup-pnpm)
  • [x] lint checking etc.
  • [x] Run tests
  • [x] ~Maybe a deploy of an example config...?~ I think @dabreegster sorted this with .github/workflow/web.yml

[griff-rees]

@stuartlynn, @dabreegster and @yongrenjie: any preferences on husky vs pre-commit? I've used the latter a lot, but happy to give husky a go.

[griff-rees]

Hmm... maybe pre-commit isn't a viable option with prettier. See https://github.com/prettier/prettier/issues/15742

[griff-rees]

Basic pre-commit linting now works, but that currently skips prettier. I've left a config for that in. I think it may be useable now (initially just set it to markdown as a test, running on everything unsurprisingly leads to a lot of changes).

What I'm guessing is the default test generated for ua_components fails as there's no page to render so I've modified that test. The remaining fail is comes from attempting to run a rust backend (see failed run):

template_app test: [WebServer] Error: Can't find ../rust_backend/pkg, run wasm-pack build ../rust_backend --target web first
template_app test: [WebServer] x Build failed in 6ms
template_app test: [WebServer] error during build:
template_app test: Error: [vite-plugin-wasm-pack] ENOENT: no such file or directory, open '../rust_backend/pkg/rust_backend_bg.wasm'