Thanks for the idea! This is a good opportunity to initially document everything it would take to "properly" support another JS framework, in no particular order:

• Create an "adapter" package that exposes a TriggerClient on the server at /api/trigger or similar path. Next.js adapter
• If not a React framework, create an equivalent of the @trigger.dev/react package (reference) that makes it easy to get public info about jobs/runs/tasks from the frontend
• Add to the @trigger.dev/cli init command to automatically detect framework and bootstrap it with Trigger.dev code
  • If this is the first framework after Next.js, we'll need to modify the init command code to support multiple framework detection
• Add a "Quick Start" guide for the framework to the docs Next.js Quick Start
• Add a Platform guide for the framework to the docs Next.js Platform Guide
• Add the framework to the dashboard onboarding tutorial
  • If this is the first framework after Next.js, we'll need to update the onboarding tutorial to support multiple frameworks
• Add an example project to the examples repo ref

@ericallam If you need any help to add Qwik/Qwikcity support i am ready.

I'm closing this as v3 doesn't require framework specific code to run tasks and is now available in early access: https://trigger.dev/blog/v3-developer-preview-launch/