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:PrefectHQ Prefect UI V2 Package Lock

From Leeroopedia


Knowledge Sources
Domains Frontend, Dependency_Management, Build_System
Last Updated 2026-02-09 22:00 GMT

Overview

NPM dependency lock file that pins exact versions of all direct and transitive dependencies for the ui-v2 React application.

Description

The ui-v2/package-lock.json is an auto-generated file produced by npm that records the resolved version, integrity hash (SHA-512), and complete dependency tree for every installed package in the ui-v2 project. It ensures that all developers and CI environments install identical dependency versions regardless of when `npm install` is run. The file covers the full transitive closure of dependencies from React 19, TanStack ecosystem, Radix UI primitives, Recharts, CodeMirror, and all dev tooling (Vite, Vitest, Playwright, Storybook, Biome).

Usage

This file is consumed automatically by `npm install` (or `npm ci` in CI). It should be committed to version control and never edited manually. It is regenerated when dependencies in `package.json` change.

Code Reference

Source Location

Signature

{
  "name": "prefect-ui",
  "version": "0.0.0",
  "lockfileVersion": 3,
  "packages": {
    "": {
      "name": "prefect-ui",
      "dependencies": { ... },
      "devDependencies": { ... }
    },
    "node_modules/react": {
      "version": "19.2.4",
      "resolved": "https://registry.npmjs.org/react/-/react-19.2.4.tgz",
      "integrity": "sha512-..."
    }
  }
}

Import

# Not importable; consumed by npm automatically
cd ui-v2
npm ci  # Install exact locked versions (preferred for CI)
npm install  # Install and potentially update lock file

I/O Contract

Inputs

Name Type Required Description
package.json file Yes Declares desired dependency ranges
npm registry network Yes Source for resolving package versions

Outputs

Name Type Description
node_modules/ directory Installed packages matching locked versions
Deterministic builds guarantee Identical dependency tree across all environments

Usage Examples

Clean Install in CI

cd ui-v2
npm ci  # Uses package-lock.json for deterministic install
npm run build  # Build with exact locked dependency versions

Updating Dependencies

cd ui-v2
npm update  # Updates within semver ranges, regenerates lock file
npm audit fix  # Fix vulnerabilities, regenerates lock file

Related Pages

Page Connections

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