@gitbeaker/rest

@gitbeaker/rest is the main entry-point package of the gitbeaker monorepo, providing a fully typed TypeScript SDK over the GitLab REST API. It wraps essentially every resource GitLab exposes — projects, merge requests, pipelines, issues, users, groups, and dozens more — behind a consistent client interface, and runs identically across Node.js, browsers, Deno, and Bun via a shared core built on top of @gitbeaker/core and @gitbeaker/requester-utils.

A companion @gitbeaker/cli package layers a command-line interface on the same client for scripting GitLab operations without writing custom code, making the gitbeaker family the de facto typed SDK for automating GitLab from JavaScript/TypeScript.

What You Get

• A typed client covering nearly all GitLab REST API resources (projects, MRs, pipelines, issues, groups, users, and more)
• Cross-platform support for Node.js, browsers, Deno, and Bun from the same package
• Built-in pagination helpers and automatic request retry/backoff via @gitbeaker/requester-utils
• Full TypeScript types for every request parameter and response shape
• A companion @gitbeaker/cli package for scripting GitLab operations from the command line

Common Use Cases

• Automating GitLab project/CI configuration from a Node.js script or internal tool
• Building custom GitLab integrations (bots, dashboards, migration scripts) with full type safety
• Fetching merge request, pipeline, or issue data for internal reporting and analytics
• Scripting bulk operations across many GitLab groups/projects (e.g. bulk permission changes)

Under The Hood

Architecture The gitbeaker monorepo (packages/core, packages/rest, packages/requester-utils, packages/cli) separates the typed resource definitions and request-building logic (core) from environment-specific HTTP transport (requester-utils), letting @gitbeaker/rest compose the two into a single client class exposing dozens of resource namespaces (Projects, MergeRequests, Issues, Pipelines, etc.), each implemented as a thin typed wrapper generating REST calls against GitLab’s documented endpoints.

Tech Stack Fully TypeScript, built with a monorepo toolchain (workspaces + CircleCI), releases automated via auto (intuit/auto) and semantic-release conventions, publishing separate packages per platform concern rather than one monolithic bundle.

Code Quality The project has an extensive CircleCI pipeline with Codecov-tracked coverage, 200 contributors, and heavy use of automated release tooling — a strong signal of process maturity for a single-maintainer-led project (jdalrymple holds the vast majority of commits). Prettier enforces consistent formatting across the codebase.

API Design Resource-namespaced methods (api.Projects.show(id), api.MergeRequests.all({projectId})) closely mirror GitLab’s own REST API documentation structure, which keeps the learning curve low for anyone already familiar with GitLab’s API reference, and full TypeScript types give strong autocomplete and compile-time safety for request parameters and responses.