ask-qwksearch-monorepo

Maps packages, apps, build commands, and troubleshooting for the QwkSearch bun/turbo monorepo.

74|11|Updated Jul 4, 2024
One-click install
npx skills add https://github.com/OpenSourceAGI/qwksearch-research-agent --skill ask-qwksearch-monorepo-opensourceagi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ask-qwksearch-monorepo
Source: https://github.com/OpenSourceAGI/qwksearch-research-agent/tree/main/skills/ask-qwksearch-monorepo
Command: npx skills add https://github.com/OpenSourceAGI/qwksearch-research-agent --skill ask-qwksearch-monorepo-opensourceagi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? In a large bun/turbo monorepo with 20+ packages and 5 apps, developers often edit the wrong layer, hit stale dist/ builds, or run tests that silently skip packages. This Skill tells you exactly which package or app owns a behaviour and which commands to run. ## Core Features & Use Cases - Ownership Map: A lookup table routing behaviours (chat UI, document editor, search, PDF extraction, YouTube transcripts, MCP server) to the correct package and its dedicated skill. - App Coverage: Documents the five apps (Next.js web, Tauri desktop, WXT browser extension, VS Code extension, LobeHub build) that have no package skill of their own, including the Hocuspocus collaboration server inside the web app. - Build & Test Guidance: Explains the workspace build-order trap, why root bun run test skips some packages, and how to add a new workspace package. - Use Case: You changed research-agent-ui but the web app shows old behaviour — the Skill explains the app imports built dist/ output and tells you to run the prebuild script. ## Quick Start Ask which package owns the search results UI in the QwkSearch monorepo and how to rebuild it so the web app picks up the change.

Frequently Asked Questions about ask-qwksearch-monorepo

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find which package owns a feature in a turborepo monorepo?

Use the ownership table mapping behaviours to packages: chat and search UI live in research-agent-ui, the document editor in reason-editor, and agent orchestration in chat-agent-toolkit. The apps mostly wire packages together rather than containing business logic.

Why doesn't my package change show up in the app that imports it?

Sibling packages are consumed as built dist/ output, not live source. Run bun run build in that package, or run node .github/scripts/build-workspace-packages.mjs to rebuild all packages in topological order.

Why does turbo build skip a local workspace dependency?

Turbo only treats a dependency as internal when the declared semver range matches the workspace version. A mismatched range like ^0.1.95 against an older workspace version makes turbo skip it, which the prebuild script covers instead.

Why doesn't the root bun run test run every package's tests?

The root vitest.config.ts lists projects explicitly, and domain-rank, extract-pdf, extract-youtube, and language-model-training are deliberately absent because they use bun test, jest, or pytest. Run each package's own test script instead.

Can I use npm or yarn instead of bun in this monorepo?

No, bun is the required package manager for the root workspace. Note that apps/qwksearch-ext and apps/qwk-in-lobe are semi-independent pnpm workspaces with their own lockfiles requiring separate installs.