Repository navigation
Packvium 1.5.0
No API changes. The JavaScript engine's beam search is faster; route packing,
rebalanceWeight and the quality termination report are fixed, and a misspelt configuration
key is now refused (see Fixed).
Changed
- Beam search 7–9% faster in the JavaScript engine, same results. Expansions that cannot
beat the best plan so far are no longer copied, and the bound that ranks beam nodes is one
binary search per node. - No probe for
@packvium/native. The package tried to load that name, which is neither
published nor declared, so a supply-chain scanner reported an unresolved dependency. A
compiled addon is still loaded frompackvium-native.nodebesideindex.js; an
npm installruns the JavaScript engine, as it already did.
Fixed
qualitywithminimum_support_rationo longer returns unsupported items. The
homogeneous block solver ran even when the request asked for support, and a block set on a
smaller one overhangs it: the result could hold items below the requested ratio, some
resting on nothing, reported asbest_found. Such a request is now left to the per-item
search, and every item meets the ratio. Present since the block solver was added.- A misspelt
configurationkey is refused. A key the request schema does not declare in
configurationor itseffort_budget(profileforsolver_profile,top_kfor
alternatives) was silently ignored, so the request ran on defaults.packnow throws
InvalidRequestErrorwith reasonnot_allowedand the key's pointer, for example
/configuration/profile. rebalanceWeightno longer strands a supported item. It could move the item underneath
and leave the one above floating; such a move is now discarded, as documented.qualityreportseffort_limitwhen the effort budget stopped it, nottime_limit.- Route packing with a
-xdoor now packs all five items in the regression scene (formerly
two), keeps next-stop parcels behind the first stop's pallet, and orients upright pallets to
save length. - An unknown
objectiveor access direction is refused with its pointer (not_allowed,
e.g./configuration/objective) instead ofinvalid_valuewith an empty field; refusal
messages match the documentation.