Implementation:Puppeteer Puppeteer Website Package Lock

Attribute	Value
sources	Puppeteer_Puppeteer\|https://github.com/puppeteer/puppeteer
domains	Documentation, Build_System
last_updated	2026-02-12 00:00 GMT

Overview

The website/package-lock.json is the npm lockfile for the Puppeteer documentation website, pinning exact dependency versions for the Docusaurus-based site.

Description

This file is an auto-generated npm lockfile (lockfileVersion 3) for the package named website (version 0.0.0). It is separate from the root monorepo lockfile because the documentation website is not part of the npm workspace configuration and manages its own dependency tree independently.

The website is built with Docusaurus 3.9.2 and its key dependencies include:

@docusaurus/core, @docusaurus/preset-classic -- Core Docusaurus framework
@docusaurus/plugin-client-redirects, @docusaurus/plugin-content-docs -- Documentation plugins
@docusaurus/remark-plugin-npm2yarn -- Converts npm commands to yarn/pnpm equivalents in docs
@docsearch/react and algoliasearch-helper -- Algolia search integration
react and react-dom (19.2.4) -- UI rendering
prism-react-renderer -- Syntax highlighting in code blocks

At approximately 18,804 lines, it records the full resolved dependency tree for all direct and transitive dependencies.

Usage

This lockfile is consumed by npm ci or npm install when run inside the website/ directory. It ensures that documentation site builds are reproducible across development machines and CI environments.

Code Reference

Source Location

File	Purpose
`website/package-lock.json`	Website npm dependency lockfile (18,804 lines)
`website/package.json`	Website package manifest defining dependencies and scripts

I/O Contract

The file is a JSON document conforming to the npm lockfileVersion 3 schema.

Top-level structure:

{
  "name": "website",
  "version": "0.0.0",
  "lockfileVersion": 3,
  "requires": true,
  "packages": {
    "": {                                  // Root website package metadata
      "name": "website",
      "version": "0.0.0",
      "dependencies": { ... },             // Runtime dependencies (Docusaurus, React, etc.)
      "devDependencies": { ... }           // Build-time dependencies (@swc/core, etc.)
    },
    "node_modules/<package-name>": {       // Per-dependency entry
      "version": "<semver>",
      "resolved": "<registry-url>",
      "integrity": "<sha512-hash>",
      "dependencies": { ... },
      "engines": { ... }
    }
  }
}

Key fields per dependency entry:

Field	Type	Description
`version`	string	Exact resolved semver version
`resolved`	string	Full URL to the package tarball on the npm registry
`integrity`	string	Subresource integrity hash (SHA-512) for verification
`license`	string	SPDX license identifier for the package
`dependencies`	object	Nested dependency version constraints

Usage Examples

Installing website dependencies for local development:

cd website/
npm ci
npm start

Building the documentation site for production:

cd website/
npm ci
npm run build

Checking the installed Docusaurus version:

cat website/package-lock.json | jq '.packages["node_modules/@docusaurus/core"].version'
# "3.9.2"

Related Pages

Root Package Lock -- Monorepo-level dependency lockfile
Versions Map -- Puppeteer-to-browser version mapping used in documentation

Page Connections

Double-click a node to navigate. Hold to expand connections.

Principle

Implementation

Heuristic

Environment