Repository navigation
Releases
Packvium 1.11.0
The browser build on the 1.11.0 core: bottom gussets and standing pouches, a certified bound
for shipping_cost and lowest_landed_cost, and one money ceiling.
Added
bottom_gusset_depthandorientation: "standing"on agusseted_bag.optimality.lower_boundand the gap undershipping_costandlowest_landed_cost.examples/checkout.mjs.
Changed
- A
rate_tablepriced above 9007199254740991 minor units at its top bracket is refused at
admission. - Measures follow the shared grammar, including upper-case unit suffixes.
hull_vertices
holds at most 32 points. effort_budgetlimits andtag_limitswritten as1000.0are the integers they equal.
Fixed
- A JSON count of 2^32 truncated to 0 on wasm32 (
max_restarts,tag_limits); it now
saturates. validate_jsoncould panic on a crafted result with mixed-type values.
Packvium 1.10.0
A rebuild on the 1.10.0 Rust core: pallets may overhang their deck, mailers may have gussets, a
hull turns 24 ways, every placement has an id, a request may name its currency, and three more
objectives state a lower bound. units refuses keys it used to ignore.
Added
container.pallet_overhang_limitis honoured, where 1.9 refused it: a load may pass the
deck by the stated length at each end and width at each side. Positions are measured from
the corner of the overhang zone; a floor placement'ssupport_ratiois the share of its base
on the deck; the pallet reportsachieved_dimensionsand is billed at the larger of its
declared footprint and that size. Besideaccess_directions,axles,made_to_measure,
obstacles, a non-zerovoid_fill_reserve_ratioor an item'sstop_indexit throws
UnsupportedFeatureError.- Gusseted bags:
deformable_boundary.kind: "gusseted_bag"withside_gusset_depth
admits a load whenb + c <= W + G. - 24 rotations for a
convex_hullitem: 18 signed codes such as-L-W+Hafter the six
legacy ones, accepted only on a hull. placement_idon every placement, the canonical JSON of
[container id, x, y, z, item_type, orientation]in ticks; afixed_placements[]entry may
quote it, andvalidatereportsplacement_id_mismatchandduplicate_placement_id.currencyon the request and onrate_table, echoed on the result; a rate table
without a request currency, or in another one, throwsInvalidRequestError, andvalidate
reportscurrency_mismatch. It never changes the answer.- Lower bounds for
maximum_value,open_dimension_heightandmaximum_volume, so
optimality.lower_boundis stated under every objective but the two carrier ones. - A made-to-measure box may keep a
void_fill_reserve_ratio.
Changed
unitsrefuses every key butlength:InvalidRequestErrorwith reasonnot_allowed
at/units/<key>. Write the unit on each weight instead ofunits.weight.- Every container is numbered per type on the grid lattice and block loader too:
pair#1,large#1where 1.9 could saypair#2orlarge#10. - An unknown
deformable_boundary.kindis refused with both kinds listed. - Built with
wasm-bindgen0.2.130.
Fixed
- An explicit rotation list emptied by
keep_uprightis refused atallowed_rotations,
with the same named request error the independent validator checks. - Stocking cut boxes indexes artifact lookups once and reports malformed consumed
machine fields as structuredinvalid_revisionerrors.
Packvium 1.9.0
A rebuild on the 1.9.0 Rust core: the centre of gravity is checked, and answers agree with the
other engines where 1.8 found them apart.
Changed
- Under a clearance a compressible item bears its load on its own footprint, so its crush
check is stricter andvalidatemeasures its own compressed volume. - Breaking for weights past
2^53 - 1ticks: a weight'sticks, and ashipping_cost
score position, are aBigIntpast it, soJSON.stringifyrefuses such a result; the new
stringifyExactandparseExactcarry it through JSON exactly. Below it nothing changes. - A weight is at most
2^63 - 1ticks, and so is every item's weight times its quantity plus
the heaviest tare: past it,invalid_request/above_maximum; a weight written as a JSON
number past2^53 - 1isinvalid_valueand must be a string. - The centre of gravity is checked under a
minimum_support_ratioabove 0: a placement
covering at most half its base with the centroid outside the contact hull is refused.
A request without a ratio packs as before. - Agrees with the other engines where 1.8 did not: nesting under a clearance shares the
items' own overlap and a deep nesting column nests in pairs; a length past2^53 - 1ticks or
a box past10^30cubic ticks isinvalid_request/above_maximum; a side that reads as zero
ticks isinvalid_value/must be positive; an obstacle box outside its container is
invalid_value/lies outside inner_dimensions, each at its own pointer. validatechecks the centroid (centre_of_gravity_unsupported) and the whole stack's load
(top_load_exceeded), an item on several bearers shared by contact area. It no longer
holds that item's whole weight against every bearer, so it accepts some results 1.8 rejected
and names the overloaded bearer.- A plan beam wider than 1 compares every container type, whatever the node limit.
- Accepts null obstacle coordinates as zero, including additional boxes,
consistently with request admission.
Packvium 1.8.0
A rebuild on the 1.8.0 Rust core: results say how far they can be from the best possible
answer, validate checks that claim, and a mistyped flag is refused.
Added
optimality.lower_boundand the gap under thedefaultandlowest_costobjectives;
validatechecks them.
Changed
- Only attaining the bound sets
optimal, on a complete result, 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); it was read
as the field's default.
validaterejects such a request withMalformedResult(contract), and readsnullas the
default.
Fixed
solvers: ["homogeneous_blocks"]packs underfastandbalanced; it placed nothing.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.
Packvium 1.7.0
A rebuild on the 1.7.0 Rust core. Breaking: a refused call now throws a typed Error, not a
string. The reference validator joins the package, and quality looks ahead in its block solver.
No request or result field changes.
Added
validate(request, result)andMalformedResult. The reference validator, a promise of a
list of issues (code,detail), empty when the result is valid;MalformedResultfor a
result of the wrong shape.PackviumWasmModulegains an optionalvalidate_json. The
WebAssembly module grows by about 414 KB (148 KB gzipped) to carry it.InvalidRequestError,FixedPlacementError,UnsupportedFeatureErrorand
CommerceInputError, exported from both entry points with their types.
Changed
- Node 18 or later. The WebAssembly module uses reference types (
externref), which
Node 16 cannot instantiate. 1.6.0's module did too, so it never loaded on the Node 16 that
enginesand this README promised; both now say 18, and CI runs Node 18, 20 and 22. - A refused call throws an
Error, not a string. Breaking for code that tested
typeof error === 'string'or read the message as the thrown value. A refused request throws
InvalidRequestError(aRangeError) orFixedPlacementErrorwithcode,reason,field
anddetail; a field the engine does not implement throwsUnsupportedFeatureErrorwith
codeandfields; a commerce refusal throwsCommerceInputError. The message is the
engine's own sentence, unchanged. The classes are built as@packvium/engine's are:
new UnsupportedFeatureError(fields)takes the list of fields, not a message. - Every schema enum value is refused as
not_allowed. A value outside its list in
allowed_rotations, the output and dimensional-weight units,shape_type,
ground_contact_ruleorconfiguration.solversthrowsInvalidRequestErrorwith reason
not_allowedat its JSON Pointer. An unknown output unit was copied through;ticksas an
output unit is now refused, as the schema always said. qualitylooks ahead in the block solver, completing its leading blocks greedily
and committing the best, so the answer is never worse than the greedy pass. Under a tight
effort budget the block start can now reporttruncated/effort_limit.qualitydoes less work for the same answers. Its staged beam refines
the best greedy order instead of the first two, and extreme points scan the exposed corners
instead of every combination of placed faces. Measured on the native Rust build, no answer
changed with either: the first took 44% offquality's CPU on our benchmark, and the second
cut what was left to 42%.- Portfolio starts go to distinct item orders; a stacking scene that took two
containers now takes one. no_eligible_containeris reportedproven, andinsufficient_supportis reported
(observed) where the support rule is the only blocker.- A
nesting_heightnot below the item's height is refused asinvalid_valueat its
pointer, and with nooutputblock the result is written inunits.length's schema code.
Fixed
- A rejected
initis retried on the next call instead of cached, and the Node loader
imports a literal path. incompatible_tagsis applied item against item, not against container tags.
Packvium 1.6.0
A rebuild of the WebAssembly engine on the 1.6.0 Rust core: boxes cut to measure, flat bags,
stacking groups and a volume-first objective in the request, and a fix for small orders with a
convex_hull item.
Added
rebalanceWeight(request, result, {maxMoves}), the same call as in@packvium/engine.made_to_measure,deformable_boundary: {kind: "flat_bag"},stacking_group/
accepts_stacking_groupsandobjective: "maximum_volume"in the request, and
achieved_dimensionsandmade_to_measurein the result.- A warning for items resting on nothing when
minimum_support_ratiois 0. No answer
changes.
Changed
- An unpacked item names the limit that left it out, the same in every engine.
Where the search used to fall back tono_feasible_placementorsearch_exhausted, an item a
fresh container would take but none is left reportscontainer_inventory_exhausted, and one
that overloads an axle wherever it stands alone reportsaxle_overloaded; both are
inferred. Code that matched the old reason for these cases must match the new one. - An explicit
solvers: ["homogeneous_blocks"]request packs in the profile's start order
when the block solver declines the scene, so the answer no longer depends on the
order the items are listed in. qualityorders its beam by aconvex_hullitem's own solid, not its box, so
it no longer assumes a second wedge cannot fit when it can.- The container plan counts a
convex_hullitem by its own solid too, so
qualityno longer ranks a plan as if wedges that share a container each needed their own. fastandbalancedadd the block solver as one more start and keep its answer only
when strictly better.
Fixed
- Small orders with a
convex_hullitem finish in a handful of search nodes instead of
spending the whole time limit. max_payloadholds in the block and grid solvers. Their capacity cap narrowed weights
to 32 bits, so a payload limit above about 537 g was read wrong and a block could overfill
the container.
Packvium 1.5.0
A rebuild of the WebAssembly engine on the 1.5.0 Rust core. No API changes. Searches are
faster, and a misspelt configuration key is now refused (see Fixed).
Changed
- Faster searches, same results. The Rust core's collision index keeps its cells in a flat
array instead of a tree; natively that made beam searches 41% faster. Every result is
byte-identical.
Fixed
qualitywithminimum_support_ratioanswers instead of failing with
solution_failed_validation, and a block answer reports the support each item really has
rather than 1.0 for every item.- 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. It is now refused with
reasonnot_allowedand the key's pointer, for example/configuration/profile.parallel
is refused too; this build always runs search starts in sequence. - An item that fits no orientation no longer spends the exact search's budget; the search
now finishes instead of reportingeffort_limit. Placements are unchanged. - An unknown
objectiveor access direction is refused with its pointer (not_allowed),
and refusal messages match the documentation.
Packvium 1.4.0
A rebuild of the WebAssembly engine on the 1.4.0 Rust core. A request the schema never
allowed is now refused instead of packed (see Fixed).
Added
fixed_placementsin a request: items already loaded keep their place, count toward
weight, support and top load, and come back markedfixed: true.- A malformed request's error names the bad value: its message reads
invalid_request: /items/0/quantity: must be at least 1, with a reason from a closed set.
Changed
- The compiled beam search keeps its speed without its memory cost. Results are
byte-identical. - Container ids number each type from 1, as the other engines number them. Only answers
with more than one container type change, and only their ids.
Fixed
- Numbers below their floor are refused. A negative item or container quantity was packed,
and a zero or negative limit was silently replaced by its default. - A placement or obstacle far outside its container is refused instead of wrapping around
and looking inside it.
Plan revisions are not exposed by this package.
Packvium 1.3.0
A rebuild of the WebAssembly engine on the 1.3.0 Rust core. No API changes; nothing breaks 1.2.0.
Changed
- The compiled beam search caches its sort keys instead of recomputing them. Results are
byte-identical.
Operational artifacts are not exposed by this package.
Packvium 1.2.0
A rebuild of the WebAssembly engine on the 1.2.0 Rust core. No API changes; nothing breaks 1.1.0.
Changed
- Faster group batching in the compiled solver: two quadratic scans over group members
became a single pass. Results are byte-identical. - The README now lists
examples/shapes.mjs(convex-hull and compressible items).
Execution plans are not exposed by this package.