ENGINE / @packvium/engine
Node engine
Native N-API addon when one is built, and a deterministic JavaScript fallback when it is not — the same request either way.
INSTALL
npm install @packvium/engineFIRST CALL
// npm install @packvium/engine
import { pack } from '@packvium/engine';
const result = pack({
items: [{ id: 'book', quantity: 4, dimensions: { length: '210', width: '140', height: '30' } }],
containers: [{ id: 'carton', inner_dimensions: { length: '400', width: '300', height: '250' } }],
});
console.log(result.status); // "feasible"- Version
- 1.11.0
- Requires
- Node >= 16
- License
- MIT
- Role
- Engine
- Registry
- npm
- Availability
- published
EVIDENCE
Held to the same fixtures as every other engine.
A package is not a separate product with its own quality level. It runs the shared corpus, and where its guarantees differ from the reference engines, the difference is documented rather than implied.