eval/npm · pac · Tangled

ryan.freumh.org / pac

This repository has no description

1 folder · 43 files

Ryan Gibb · tolerated-misses lists the four names the registry answers 404 that pac asks for in the shared and placement readings, each a dependency of an old or pre-release version · 22h ago

npm: re-fetch the snapshot at one date and close it over both sides' cones

npm's controls pose answers under the shared reading and to berry.sh, one per verdict, and the Berry scripts refuse a Yarn other than 4.14.1

npm's controls pose answers under the shared reading and to berry.sh, one per verdict, and the Berry scripts refuse a Yarn other than 4.14.1

The Berry scripts share one yarn.lock reader, one berry_spec and mklock's manifest, mklock reads a package's fields through relation's, and berryall.sh and berryownall.sh start berryreg.py through serve.sh, which it now answers

The Berry scripts share one yarn.lock reader, one berry_spec and mklock's manifest, mklock reads a package's fields through relation's, and berryall.sh and berryownall.sh start berryreg.py through serve.sh, which it now answers

The Berry scripts share one yarn.lock reader, one berry_spec and mklock's manifest, mklock reads a package's fields through relation's, and berryall.sh and berryownall.sh start berryreg.py through serve.sh, which it now answers

The Berry scripts share one yarn.lock reader, one berry_spec and mklock's manifest, mklock reads a package's fields through relation's, and berryall.sh and berryownall.sh start berryreg.py through serve.sh, which it now answers

npm's resolution resolves a descriptor once and reads a peer beside a dependency of its name as Yarn Berry's peer with default, and PAC_NPM_CORE=1 reads manifests as npm and Berry both do, which a Berry check of each answer confirms

The Berry scripts share one yarn.lock reader, one berry_spec and mklock's manifest, mklock reads a package's fields through relation's, and berryall.sh and berryownall.sh start berryreg.py through serve.sh, which it now answers

resolve.js and lockname.py read a root's devDependencies over its dependencies and a root override on the key, as npm does

npm/close.sh closes repos/npm over every query in the npm, shared and placement readings, and SNAPSHOTS records the snapshot it closed, 4012c06a, 5796 packuments, as the one the final run uses

resolve.js and lockname.py read a root's devDependencies over its dependencies and a root override on the key, as npm does

npm's resolution offers a dependency's peer only what its depender holds, peers on or is, the root alone installing a peer nothing else provides; the replay closes a cycle through one name with a link, and the npm check closes an optional peer left open over the chain

eval/npm checks a placement answer as the lock it is, with npm ci, npm ls and require.resolve per edge, and controls pose layouts to that check

layout-check.sh

resolve.js and lockname.py read a root's devDependencies over its dependencies and a root override on the key, as npm does

eval/npm checks a placement answer as the lock it is, with npm ci, npm ls and require.resolve per edge, and controls pose layouts to that check

resolve.js and lockname.py read a root's devDependencies over its dependencies and a root override on the key, as npm does

The Berry scripts share one yarn.lock reader, one berry_spec and mklock's manifest, mklock reads a package's fields through relation's, and berryall.sh and berryownall.sh start berryreg.py through serve.sh, which it now answers

npm: re-fetch the snapshot at one date and close it over both sides' cones

The eval flake takes Node 24.21.0 with npm 11.19.0 (arborist 9.9.1) from a later nixos-26.05, the npm body.tex §7.3 cites, and npm-version records it

eval: one serve for shim.py and sparse_proxy.py, which asks the server what it serves; npm's command line and module loader shared

eval: one serve for shim.py and sparse_proxy.py, which asks the server what it serves; npm's command line and module loader shared

pac npm reads its manifests under --reading=npm|shared rather than PAC_NPM_CORE, and the npm harness passes READING to pac and the check and records it in a run's parameters

eval/npm: copies keyed by alias, unreached packages placed, an answer no finite node_modules tree holds INVALID; one reader of pac's tree

A placement run's resume check reads FILL too, so a filling and a frozen run never share a results file

eval: one serve for shim.py and sparse_proxy.py, which asks the server what it serves; npm's command line and module loader shared

eval: a regression line is a whole query in the tool's syntax, in queries.txt; opam adds its two --with-test queries

eval: opam's and alpine's refusals in one file each, read by the run and the check alike; npm's lock walk in Python alone and cargo's newest in scale.py alone; the README says who reads the rows

npm's check verifies every peer from its declarer, and reads npm's overridden peers and npm ls's invalid edges as refusals

eval: one list of refusals per ecosystem, read by the tool's run and by the check alike

harness: each ecosystem's refusal rule is one refused.sh, which its scale.sh and check.sh both source

relation.py's misses leaves the peers the answer leaves open to open_misses

resolve.js and lockname.py read a root's devDependencies over its dependencies and a root override on the key, as npm does

eval: one serve for shim.py and sparse_proxy.py, which asks the server what it serves; npm's command line and module loader shared

npm/close.sh closes repos/npm over every query in the npm, shared and placement readings, and SNAPSHOTS records the snapshot it closed, 4012c06a, 5796 packuments, as the one the final run uses

eval: alpine reads the apk setup.sh resolved; seed.sh keeps roots.txt until it finishes and bounds pac; stale names

comments: say only what the code, the proofs and the tools' sources bear out; check cited Rocq names in runtest

One copy of Yarn Berry's packageExtensions, lib/npm/berry-extensions.json, feeds pac and the npm check alike, and pac matches an extension as Berry does, retrying a version with its prerelease tags dropped

eval/npm: copies keyed by alias, unreached packages placed, an answer no finite node_modules tree holds INVALID; one reader of pac's tree

tolerated-misses

tolerated-misses lists the four names the registry answers 404 that pac asks for in the shared and placement readings, each a dependency of an old or pre-release version

eval: an uncompared answer is not exact; a query named twice runs once; queries read once; pac's statuses in the summary; npm totals per query

npm's check closes a cycle of copies with a link, as npm does, and reads links wherever it reads a lock

npm's and cargo's checks judge an answer consistent, npm's by the lock holding every edge and cargo's by an independent checker, and report the tool's lock apart

eval/npm: copies keyed by alias, unreached packages placed, an answer no finite node_modules tree holds INVALID; one reader of pac's tree