Repository navigation
Packvium 1.8.0
validate works after a plain npm install, results say how far they can be from the best
possible answer, and a mistyped flag is refused instead of guessed.
Added
optimality.lower_boundand the gap under thedefaultandlowest_costobjectives,
computed with exactBigIntvolumes;validatechecks them.
Changed
validate(request, result)answers without the compiled addon, with the same issues
in the same order.- Attaining the bound sets
optimal, and an effort budget names a stop: a run that ends
on exactly its budget iscomplete. - A non-boolean
keep_upright,stackable,must_be_on_flooror
require_placement_coordinatesthrowsInvalidRequestError(wrong_type), with or
without the addon.
validatethrowsMalformedResult(contract) for such a request, with or without the addon,
and readsnullas the default. - The JavaScript fallback reuses measures parsed during request checking in the bound
and starts, including made-to-measure machine settings. Hull and fixed-position measures
retain their separate admission paths. The measured macOS / Node 26 warm small-request
paired wall-time median improved about 4%; retained results agree after removing timing. - Axle-limited solves up to 2x faster,
validateup to 2.4x faster on nested results, loading
and removal sequences up to 15% faster; answers are identical.
Fixed
solvers: ["homogeneous_blocks"]packs underfastandbalanced; without the addon
it placed nothing and reportedcomplete.validatereadsunits: nullandunits.length: nullas millimetres, as the engines do,
and refuses aunitsthat is not an object, or an unknownunits.length, as acontract
MalformedResultnaming the field.units.weightis not a field and is ignored: put the unit
on each weight.
Deprecated
ValidatorUnavailableError. Still exported; nothing throws it.