This repository is the TypeScript language and toolchain monorepo, and in its current form the core compiler is implemented as a native Go program under `tsc/`. It provides the `tsc` command-line compiler (`tsc/cmd/tsc/main.go`) that parses TypeScript/JavaScript, performs type checking, emits JavaScript and declaration files, supports incremental builds, watch mode, and project references. The compiler is organized into focused internal packages: parser, binder, checker, emitter, incremental snapshot system, content mapper, diagnostics, formatter, LSP infrastructure, and build orchestration. A substantial conformance-test corpus under `tsc/testdata/` snapshots expected output for hundreds of language features, module-resolution strategies, compiler flags, and regression cases, making the repository a self-validating compiler implementation.
Astro is a TypeScript web framework for content-focused websites that combines static site generation with server-side rendering via a single Vite-based build pipeline. It compiles .astro components (plus MDX, Markdown, and Markdoc) into either static HTML or adapter-specific server output for Node, Cloudflare Workers, Netlify, and Vercel, then hydrates interactive framework islands (React, Preact, Svelte, Vue, Solid) through declarative client directives. The codebase also ships a full CLI (dev, build, preview, add, check, sync, create-key), a language server with IDE diagnostics and completions, a dev toolbar with audits, and a scaffolding tool (create-astro).
This repository is a Go reimplementation of the TypeScript compiler, including a full type checker, emitter, parser, and language server (LSP). It provides a CLI tool `tsgo` for compilation, watch mode, and build mode, and a native-preview npm package that wraps the Go binary for Node.js integration. The architecture is a monolith with well-organized internal packages (e.g., `internal/compiler`, `internal/checker`, `internal/ast`, `internal/lsp`). The codebase demonstrates high craftsmanship with clean abstractions, generic utilities, and extensive test coverage using a custom fourslash testing framework. It is actively maintained but explicitly slated for permanent archiving in September 2026, as development will continue in the main TypeScript repository. The repo is a staging ground for the TypeScript 7.0 native port and is not yet feature-complete (language service is in progress).
Civet is a full-featured compiler and language server for a CoffeeScript-like language that transpiles to TypeScript/JavaScript. It provides a CLI, bundler plugins (Vite, Webpack, esbuild, Rollup, etc.), Babel plugin, ESLint plugin, ESM loader, and browser script runner. The core compiler implements advanced features like pattern matching, pipe operators, JSX enhancements, and compile-time evaluation. The language server (LSP) delivers IDE features including diagnostics, completions, go-to-definition, hover, and rename across VS Code, Sublime Text, Zed, and Monaco. The repository is structured as a monorepo with the compiler in `source/`, a standalone LSP server in `lsp/server/`, editor extensions, tree-sitter grammars, and a documentation site at civet.dev. Notable architecture includes a PEG grammar parser (Hera), source map composition utilities, an in-memory TypeScript service host, and a worker pool for parallel compilation. The test suite enforces 100% coverage gates, ensuring high reliability. Civet demonstrates strong engineering practices: self-hosting compiler, comprehensive golden tests, CI/CD pipelines, and a modular plugin system for bundlers. While complexity arises from supporting many editor integrations and bundler adapters, the core compiler and LSP are cleanly separated. The project is actively maintained with frequent releases and community contributions.
This repository is the primary implementation of the Sway programming language and its toolchain, targeting the Fuel blockchain. It contains a full compiler pipeline (lexer, parser, AST, semantic analysis, IR with optimization passes, and code generation for the FuelVM), a package manager CLI (`forc`), a language server (`sway-lsp`), a code formatter (`swayfmt`), a debugger (`forc-debug`), a documentation generator (`forc-doc`), and a migration tool (`forc-migrate`). The standard library (`sway-lib-std`) provides essential blockchain primitives (assets, storage, crypto, etc.). The architecture is modular, with separate crates for the AST (`sway-ast`), IR (`sway-ir`), parsing (`sway-parse`), core compiler logic (`sway-core`), and error handling (`sway-error`). In production, developers use `forc` to build, test, and deploy Sway smart contracts, scripts, and predicates to the Fuel network. The LSP provides IDE features like completions, go-to-definition, and inlay hints. The formatter ensures consistent code style. The debugger enables step-through debugging of on-chain logic. The compiler supports multiple backends (FuelVM primary, EVM experimental) and includes advanced optimizations such as constant folding, dead code elimination, common subexpression elimination, and register allocation. Key entry points include `forc/src/main.rs` (CLI dispatcher), `sway-core/src/lib.rs` (compiler core), `sway-lsp/src/server.rs` (LSP server), and `swayfmt/src/lib.rs` (formatter). External dependencies include the Fuel protocol libraries (`fuel-core`, `fuel-vm`, `fuels-rs`), IPFS for package resolution, and standard Rust ecosystem crates. The repository is production-grade with extensive end-to-end tests, benchmarking infrastructure, and CI workflows.
TexLab is a Rust-implemented Language Server Protocol (LSP) server for LaTeX and BibTeX. It provides rich IDE features including code completion, diagnostics (grammar, build errors, chktex), definitions, references, hover information, renaming, folding, document symbols, inlay hints, links, formatting, and build/forward-search commands. The architecture is a modular monolith with 20+ internal crates, each encapsulating a specific concern (parsing, syntax definitions, completion, diagnostics, etc.). The core relies on a custom recursive-descent parser using `logos` for lexing and `rowan` for a lossless concrete syntax tree, enabling precise source mappings. External dependencies include `latexmk`, `chktex`, `kpsewhich`, `latexindent`, and `tex-fmt` for build and formatting. Entry points are the binary `texlab` (CLI) and the LSP server loop in `crates/texlab/src/server.rs`. The data flow involves file system watching, parsing, semantic analysis (labels, citations, environments), and incremental updates via a workspace database.
This repository is a Visual Studio Code extension that provides comprehensive language support for Terraform, including syntax highlighting, completions, diagnostics, and integration with the Terraform Language Server. It also offers deep integration with HCP Terraform for managing workspaces, runs, and state, along with features like module and provider exploration, telemetry collection, and bug report generation. The extension follows a modular architecture with separate modules for features, commands, and providers, and uses patterns such as dependency injection and static feature classes to maintain separation of concerns. Key entry points include the main activation function in src/extension.ts and various commands in src/commands/. The extension relies on external dependencies such as vscode-languageclient, axios, and the terraform-ls binary.
This repository is the official compiler and toolchain for the Leo programming language, a statically-typed language for writing private zero-knowledge applications on the Aleo blockchain. The codebase implements a full compilation pipeline from Leo source to Aleo bytecode, including parsing (with a lossless rowan-based parser), type checking, static analysis, multiple optimization passes (constant propagation, loop unrolling, dead code elimination, common subexpression elimination, SSA formation, function inlining, flattening, destructuring, storage lowering, option lowering, peephole optimization), and code generation targeting snarkVM. Beyond the compiler, it provides a complete development environment: a CLI with commands for building, testing, deploying, executing, and querying the Aleo network; a Language Server Protocol (LSP) implementation with diagnostics, goto-definition, references, rename, and semantic tokens; a standalone formatter; a package manager supporting local, git, network, and workspace dependencies with lock files; and an ABI generation and compatibility checker. The architecture is a multi-crate Rust workspace with clear separation of concerns, extensive test coverage (unit, integration, and expectation-based compiler tests), and CI/CD pipelines. The codebase demonstrates high craftsmanship with reusable patterns such as a generic directed graph with cycle detection, a canonicalization trait for structural equality, an intern-based type system, and a pass-based compiler architecture.
hcc is a compiler for the HolyC language, a derivative of TempleOS HolyC. It supports both ahead-of-time (AOT) compilation to x86_64 and AArch64 assembly and just-in-time (JIT) compilation for in-memory execution. The system includes a full front-end (lexer, parser, AST, SSA-based IR), optimization passes, register allocation, and backends for x86_64 and AArch64. Additionally, it provides a REPL, a Language Server Protocol (LSP) server, an inline assembler (TempleOS-style), a disassembler, and a control-flow graph visualizer. The standard library is written in HolyC and offers data structures (lists, vectors, hash maps, red-black trees), JSON/CSV parsers, SQLite bindings, networking, threading, coroutines, and system call wrappers. The project is a self-contained, well-structured compiler toolchain with extensive tests and active development.
Master CSS is a comprehensive CSS framework and toolchain that enables writing CSS directly in class attributes using a concise utility syntax. The system supports multiple rendering modes: a runtime engine that dynamically generates and injects CSS in the browser, a static build-time compilation mode for zero-runtime production output, and progressive hybrid modes that pre-generate critical CSS and hydrate on the client. It includes a fully modular architecture with over 30 packages covering a core engine, compiler, scanner for class extraction, validator, language server, ESLint plugin, CLI, MCP server, and first-class integration plugins for Vite, Next.js, Nuxt, Astro, Svelte, Webpack, and more. The codebase is production-grade with extensive unit and e2e tests, a dedicated benchmarking suite measuring CSS output sizes, build timings, and browser lifecycle performance, and a documentation site with interactive playground. While primarily a JavaScript/TypeScript application library, it also contains benchmark infrastructure that produces analytical metrics. The architecture is strongly layered with well-defined schema contracts (manifest JSON) enabling loose coupling between packages.
XGo (formerly Go+) is a Go-superset programming language delivered as a complete compiler toolchain. The repository implements the full language pipeline: a custom scanner (scanner/), parser (parser/), extended AST (ast/), semantic compiler (cl/), and code generator that lowers XGo source to standard Go via the gogen code builder. The xgo CLI (cmd/xgo) exposes subcommands for build, run, test, fmt, go, install, mod, pack, serve, watch, and version, wrapping the Go toolchain after transpilation. The language extends Go with command-style calls, keyword arguments, tuples, list/map/select comprehensions, error-wrapping operators (expr!, expr?), overloaded functions and operators, enums, domain-text literals, and classfile frameworks for domain-specific applications (spx games, MCP servers, shell scripts). The architecture follows a classic compiler design: XGo source → scanner → parser → AST → cl semantic analysis/code generation → gogen → Go source → standard Go toolchain. The tool/ package orchestrates module loading, go.mod management, and delegation to go build/run/test. A language server (x/langserver) with a bundled JSON-RPC2 library (x/jsonrpc2) supports editor tooling. Two notable sub-systems ship alongside the compiler: DQL (dql/), a unified query language over HTML/XML/JSON/YAML/Go AST trees, and TPL (tpl/), a grammar-based DSL parser generator used for domain-text literals. Hundreds of golden-test pairs (in.xgo/out.go) validate compiler output across Go versions 1.18-1.27. External dependencies include github.com/goplus/gogen (code builder), github.com/goplus/mod (module handling), github.com/qiniu/x (errors/streams), and cobra for CLI construction. The codebase forks several Go standard library internals (scanner, printer, ast) to support extended syntax, creating ongoing maintenance burden as Go evolves. Some features remain incomplete (panic("TODO") in matrix literal compilation, fully commented-out ast/resolve.go), and legacy naming aliases (gop vs xgo, gop.mod vs gox.mod) coexist throughout.
This repository contains a VS Code extension that acts as a bridge between the Antigravity IDE and a mobile device, enabling remote interaction via a local HTTPS server. The extension starts a self-signed HTTPS server on the LAN, uses the Chrome DevTools Protocol (CDP) to inspect and manipulate Antigravity IDE instances, and leverages the Language Server Protocol (LSP) to monitor and control code generation processes. A companion mobile web interface, served by the local server, provides real-time chat mirroring, message sending, file uploads, voice input, and generation control through a WebSocket connection. The architecture consists of three main parts: the VS Code extension (managing the server lifecycle and IDE integrations), the Express/WebSocket server (handling API requests, real-time communication, and static file serving), and the mobile SPA (rendering the IDE state and forwarding user interactions). Key capabilities include QR-code based pairing, end-to-end encrypted local communication, multi-instance switching, and programmatic control via an MCP server that exposes the API over stdio JSON-RPC. The extension demonstrates solid engineering practices with TypeScript, modular service layers, middleware for authentication and security, and a test suite covering core functionality. While tightly coupled to Antigravity's UI and protocols by necessity, it isolates concerns through well-defined services (CDP, LSP, antigravity interactions) and reusable patterns such as the CSP middleware, CDP wrapper, and stdio JSON-RPC proxy. Ongoing maintenance addresses selector fragility and API updates, ensuring compatibility with evolving IDE and VS Code versions.
Serena is a production-grade MCP (Model Context Protocol) server that provides AI coding agents with deep code intelligence across 40+ programming languages. It acts as an 'IDE for your agent', offering symbol-level retrieval, editing, refactoring, and debugging capabilities by orchestrating Language Server Protocol (LSP) backends. The system is designed to integrate with AI clients like Claude Code, Codex, Copilot, and Grok, exposing a rich set of tools for file manipulation, symbol navigation, memory persistence, and project configuration. Architecturally, Serena is a Python application with a CLI entry point that starts an MCP server, a Flask-based web dashboard for monitoring and configuration, and a hooks system for client-side pre-tool-use events. Its core is the `solidlsp` package, a custom synchronous LSP abstraction layer that manages the lifecycle of 40+ language servers (Python, TypeScript, Rust, Go, Java, etc.), handling initialization, capability negotiation, and request/response framing. The `interprompt` library provides a sandboxed Jinja templating engine for prompt generation, and the memory manager persists project-specific context across sessions. Key features include: multi-language symbol search, references, definitions, hover, rename, and diagnostics; a code editor abstraction supporting both LSP and JetBrains backends; a configurable tool registry with automatic discovery; and a comprehensive test suite with per-language integration tests. The project emphasizes reproducibility through pinned dependency versions and SHA256 verification for downloaded language server binaries, though this creates a maintenance burden as versions must be manually updated.
This repository implements a Build Server Protocol (BSP) server that integrates Xcode builds with language servers like sourcekit-lsp. It parses Xcode build logs (either from IDE builds or xcodebuild) to extract compiler flags and serves them via BSP to provide accurate code completion, navigation, and other language features for Swift, C, C++, Objective-C, and Objective-C++ projects. The server operates in two modes: 'xcode' mode automatically monitors build logs via a post-build script or file watching, and 'manual' mode processes build logs on demand. Key components include a robust compilation database handler, a parser for Xcode's proprietary xcactivitylog binary format, and a log parser that handles various Xcode build output formats. The project is actively maintained with recent commits and shows no significant technical debt.
ZLS (Zig Language Server) is a comprehensive implementation of the Language Server Protocol (LSP) for the Zig programming language. Written entirely in Zig, it provides rich IDE features including code completion, go-to-definition, hover information, semantic tokens, inlay hints, code actions, diagnostics, document symbols, folding ranges, signature help, and workspace symbol search. The server integrates with Zig's build system via the Build System Protocol (BSP) and can run `zig ast-check` for diagnostics, or use its own built-in semantic analysis engine. Architecturally, ZLS is a monolithic LSP server with a modular design. The core `Server` struct manages workspaces, document stores (`DocumentStore`), configuration (`Config`), and dispatches requests to feature modules under `src/features/`. The `Analyser` struct in `src/analysis.zig` provides type inference and symbol resolution using an `InternPool` for deduplicated type/value storage. A newer analysis backend under `src/analyser/` (InternPool, StringPool, degibberish) is partly implemented but not yet fully integrated. The test suite is extensive, with over 9,000 lines of completion tests alone, using a custom testing framework and placeholder-based assertions. Key dependencies include `known-folders` for platform-specific directory discovery, `diffz` for text diffing, `lsp_kit` for LSP protocol types, and `tracy` for profiling. The build system is managed via `build.zig` with dependency definitions in `build.zig.zon`. ZLS is highly configurable through a JSON configuration file, with options for snippets, inlay hints, build-on-save, and more. It is actively maintained, targets Zig master, and has a strong focus on correctness and performance, though some areas (like generic resolution and combinatorial types) remain heuristic-based.
GritQL is a declarative query language and CLI tool for searching, linting, and transforming source code across many programming languages (JS/TS, Python, Java, Go, Rust, Ruby, PHP, SQL, etc.). The repository implements a Rust workspace comprising a pattern-matching engine (grit-pattern-matcher) that compiles GritQL patterns into executable AST-based matchers, a CLI client (grit) with commands like `apply`, `check`, `list`, `patterns`, and `lsp`, an LSP server for IDE integration, WebAssembly bindings for browser use (playground), and Node.js NAPI bindings for programmatic access. Patterns are authored in `.grit` files or embedded in Markdown with sample-based testing. The system uses tree-sitter parsers (vendored grammars) to parse source files, supports pattern caching for performance, and includes authentication, analytics, and remote module resolution. The architecture is modular: core pattern matching is isolated in `crates/grit-pattern-matcher`, pattern compilation in `crates/core`, language support in `crates/language`, and UX in `crates/cli`. The documentation site (Next.js with Markdoc) provides an interactive playground. External dependencies include tree-sitter parsers, NAPI-RS, WebAssembly tooling, and optional LLM APIs for AI-assisted patterns.
The Ada Language Server (ALS) is a Language Server Protocol implementation providing IDE features for Ada and SPARK programming languages. It consists of a core server written in Ada that handles language intelligence features (completion, diagnostics, refactoring, etc.) and a VS Code extension written in TypeScript that integrates with the editor. The architecture follows a client-server model where the language server communicates with editor clients via JSON-RPC. Key components include the Ada-based LSP server implementing standard LSP capabilities plus Ada-specific extensions, the VS Code extension providing editor integration, and a comprehensive test suite validating LSP compliance. The project shows active maintenance with regular commits, clear build systems, and dependency management through Alire.
This repository implements a Language Server Protocol (LSP) server for PureScript. It provides editing assistance features like code completion, go-to-definition, diagnostics, code actions, formatting, and refactoring by wrapping the PureScript IDE server (purs ide server). The architecture is modular with clear separation between core LSP logic, PureScript-specific integrations, and protocol implementations. Key entry points include main.js and src/LanguageServer/IdePurescript/Main.purs. The server communicates with editors/IDEs via JSON-RPC and manages its own purs ide server process for language services. It supports build integration, dependency tracking, and provides rich language features through sophisticated completion ranking and export management systems.
This repository is the official Visual Studio Code extension for PowerShell (published as ms-vscode.PowerShell). It provides rich language support including IntelliSense, code navigation, formatting, PSScriptAnalyzer linting, debugging with a custom debug adapter, integrated PowerShell console, Pester test runner, ISE compatibility mode, command explorer, help view, alias expansion, remote file editing, and language model tools for AI copilot integration. The extension acts as a Language Server Protocol (LSP) client that communicates with the external PowerShellEditorServices server, and uses the Debug Adapter Protocol for debugging. It supports all major platforms (Windows, macOS, Linux) and multiple PowerShell editions (stable, preview, daily, etc.). The architecture follows a modular feature-class pattern under `src/features/`, with a central `SessionManager` handling the PowerShell process lifecycle and language client connection. The extension is well-tested with unit and integration tests across CI, and its code demonstrates solid TypeScript patterns, clean separation of concerns, and reusable abstractions such as `LanguageClientConsumer` for async LSP client access and `PowerShellExeFinder` for cross-platform PowerShell discovery. While the codebase is actively maintained and keeps pace with VS Code API changes, it contains some deprecated settings and minor complexity in session management. Overall, it is a professional-grade VS Code extension with a few genuinely reusable components that could benefit other extensions or tools dealing with PowerShell or LSP clients.
This is the Spring Tools 4 (STS4) repository, a comprehensive set of IDE tooling for Spring Boot development. It provides language servers (LSP) for Spring Boot (Java, YAML, properties, XML), Concourse CI, BOSH, and Cloud Foundry manifests, along with Eclipse plugins and VS Code extensions. The architecture separates headless language servers (built as Spring Boot applications) from IDE-specific frontends, with shared commons libraries for YAML, Java project indexing, metadata, and live process monitoring via Actuator. The codebase is professional and well-structured but shows signs of organic growth over a decade, with some code duplication between the Eclipse and headless/VS Code paths, deprecated API usage, and developer-specific hardcoded paths. It is actively maintained by VMware/Spring engineering team with strong CI/CD pipelines.