Implementation:Kubeflow Pipelines Frontend Package Lock

Knowledge Sources	Kubeflow_Pipelines npm Documentation
Domains	Frontend, Dependency_Management
Last Updated	2026-02-13 14:00 GMT

Overview

NPM lockfile that pins the exact versions of all direct and transitive dependencies for the `pipelines-frontend` package, ensuring reproducible builds.

Description

The package-lock.json file is auto-generated by npm (lockfileVersion 2) and records the resolved version, integrity hash (SHA-512), and dependency tree for every package in `node_modules`. At 70,706 lines, it locks down the entire frontend dependency graph. The `npm ci` command uses this file as its source of truth, deleting `node_modules` and reinstalling from scratch to guarantee consistency.

Usage

This file is consumed by `npm ci` during CI/CD builds and local development setup for the KFP frontend. It should never be manually edited.

Code Reference

Source Location

• Repository: Kubeflow_Pipelines
• File: frontend/package-lock.json
• Lines: 1-70706

Signature

{
  "name": "pipelines-frontend",
  "lockfileVersion": 2,
  "requires": true,
  "packages": {
    "": {
      "name": "pipelines-frontend",
      "dependencies": { ... },
      "devDependencies": { ... }
    }
  }
}

Import

# Not imported directly; consumed by npm
npm ci  # Installs exact versions from package-lock.json

I/O Contract

Inputs

Name	Type	Required	Description
package.json	JSON file	Yes	Declares dependency ranges that this lockfile resolves

Outputs

Name	Type	Description
node_modules/	directory	Exact dependency tree installed by npm ci
Integrity hashes	SHA-512	Verification checksums for each package

Usage Examples

Installing Frontend Dependencies

cd frontend/

# Install exact versions from lockfile (recommended for CI)
npm ci

# Update lockfile after changing package.json
npm install

Related Pages

• Environment:Kubeflow_Pipelines_Python_SDK