Referenced by4
Labels4

Referencing ideas

IdeaStatusTagsSummaryKatz
monorepoThe workspace is a pnpm monorepo ( `packages\*`, extension webviews, and `site` ) per ["../pnpm-workspace.yaml"] and [development_core.pnpm]. TypeScript project references build in order language → analytical → mcp → cli → extension per ["../tsconfig.build.json"]. Living requirements for the product live in this `reqlan rq` folder. Root orchestration ( Langium generate, package builds, Cursor skill sync ) lives in ["../package.json"]. Why libraries are separate packages ( and how Changesets sees them ): [package_versioning].0.040
scopeThese requirements describe the cross-package system architecture of the reqlan monorepo: language definition, language server, ideas index, editor product, and companion tools. They are distinct from [extension_scope.scope], which bounds only the VS Code extension and LSP product surface. Language concepts live in [ontology]; syntax truth lives in [syntax]; editor module contracts live under extension / module. Grouped as [workspace_packages], [language_runtime], and [product_map].0.040
scopeextension build steps for local development and CI0.040
typescript_emitdonePackage TypeScript emit goes to each package `out/` via `tsc -b` project references ( ["../../tsconfig.build.json"] ). Shared compiler options live in ["../../tsconfig.base.json"]. ["../../tsconfig.json"] is a solution file ( `files: []` ) so a plain `tsc` / VS Code " tsc: build " does not write `.js`, `.d.ts`, or `.js.map` next to sources. Webview tsconfigs are `noEmit` — Vite bundles to `packages/extension/media/webviews/`. A clean compile must generate Langium sources first ( [typescript_compile] ).0.040

Reference labels

"../../tsconfig.build.json", "../tsconfig.build.json", ../../tsconfig.build.json, ../tsconfig.build.json