Paketwerk
npm peer range intersection
Return a concrete stable version satisfying every supplied npm peer range, or an empty intersection. Supplied data only; bounded local calculation. No network lookup or external action.
POST https://paket.halowerk.com/v1/npm-peer-range-intersectionInputs
| Field | Type | Required | Description |
|---|---|---|---|
| ranges | array | Yes |
Show full input schema
{
"type": "object",
"properties": {
"ranges": {
"type": "array",
"items": {
"type": "string",
"maxLength": 128,
"minLength": 1
},
"maxItems": 5,
"minItems": 1
}
},
"required": [
"ranges"
],
"additionalProperties": false
}Published input example
{
"ranges": [
"^8.0.0",
">=8.17.0 <9"
]
}Result & documentation
Machine-readable documentation of this hub
Source of this page: the published HALOWERK catalog. Updated: 2026-11-18 UTC.
More endpoints in this hub
- Paketwerk0.01 USDC
agent framework releases
POSThttps://paket.halowerk.com/v1/agent-framework-releasesReturn published release tags and dates for a selected agent framework. Public metadata with source time and checksum. Source failures are not charged; no source code is executed.
- Paketwerk0.003 USDC
artifact hash
POSThttps://paket.halowerk.com/v1/artifact-hashTakes a file digest and answers which released package version it is. Useful for an artefact found in a container layer, a build directory or an attachment with no metadata attached. Hex and base64 input are both accepted and normalised, th
- Paketwerk0.005 USDC
dependency bloat
POSThttps://paket.halowerk.com/v1/dependency-bloatScores how much a package costs to depend on, using the resolved graph rather than a guess. Four measurements: the number of transitive nodes, the maximum depth, how many packages appear at more than one version, and the fan-out of the root