Jump to content

Connect SuperML | Leeroopedia MCP: Equip your AI agents with best practices, code verification, and debugging knowledge. Powered by Leeroo — building Organizational Superintelligence. Contact us at founders@leeroo.com.

Implementation:Microsoft Playwright Root Package Lock

From Leeroopedia
Knowledge Sources
Domains Dependency Management, Build Tooling
Last Updated 2026-02-12 00:00 GMT

Overview

The root package-lock.json pins exact dependency versions for the entire Playwright monorepo workspace.

Description

This lockfile uses npm lockfile version 3 and covers the top-level playwright-internal package (version 1.59.0-next) along with all workspace packages under packages/*. It records resolved registry URLs, integrity hashes, and the full transitive dependency tree for every direct and indirect dependency used across the monorepo. At approximately 8,700 lines, it ensures deterministic installs in CI and local development environments.

Contents

Key dev-dependency categories pinned by this lockfile include:

  • Linting and formatting: @eslint/*, @typescript-eslint/*, @stylistic/eslint-plugin, eslint-plugin-notice, eslint-plugin-import
  • TypeScript tooling: TypeScript compiler, @types/node, various @types/* packages
  • Testing infrastructure: Internal Playwright packages (workspace references)
  • Build tooling: Babel, bundlers, and related utilities
  • CI/CD: @actions/core, @actions/github, @octokit/graphql-schema
  • MCP integration: @modelcontextprotocol/sdk, @lowire/loop

Usage

This file is automatically maintained by npm install and should be committed to version control. It guarantees that every developer and CI runner resolves identical dependency versions. Manual edits are discouraged; instead, update dependencies via npm install, npm update, or npm audit fix.

Code Reference

Source Location

Related Pages

Page Connections

Double-click a node to navigate. Hold to expand connections.
Principle
Implementation
Heuristic
Environment