@bilig/headless weekly downloads statistics

@bilig/headless

@bilig/headless is the lower-level formula and WorkPaper runtime behind the scoped @bilig/workpaper entrypoint.

If this npm page is the first thing you found, run the package proof before reading the full API docs:

npm exec --yes --package @bilig/workpaper@latest -- bilig-evaluate --door workpaper-service --json

It should print verified: true after editing an input cell, recalculating a dependent formula, exporting WorkPaper JSON, restoring it, and reading the same calculated value again.

Choose the narrow package by the state you own:

You own...	Start with	First proof
WorkPaper state inside a service	npm install @bilig/workpaper	bilig-evaluate --door workpaper-service --json
A new service or route	npm create @bilig/workpaper@latest pricing-workpaper	npm run smoke
Tool or MCP integration	npm create @bilig/workpaper@latest pricing-agent -- --agent	bilig-evaluate --door agent-mcp --json
Lower-level runtime subpaths	npm install @bilig/headless	The examples below prove WorkPaper JSON, provenance, and package weight.
A saved workbook file remains the contract	npm install @bilig/xlsx-formula-recalc	bilig-evaluate --door workbook-compatibility --json

Use @bilig/headless when the workbook is the business logic, but production needs API readback, tests, persistence, and deterministic proof instead of a person opening a spreadsheet app.

Your code owns a WorkPaper: build sheets, write inputs, recalculate formulas, read the cell value, and save the workbook as JSON. Product code gets reviewable workbook-shaped logic without shipping a spreadsheet UI. Tool hosts can expose narrow operations such as readRange and setInputCell instead of guessing state from screenshots.

The npm tarball also includes AGENTS.md and SKILL.md so tool hosts inspecting node_modules/@bilig/headless can find the write/read/persist loop locally. The public docs expose the same path through AGENTS.md, agent.json, skill.txt, WorkPaper agent tool, and llms-full.txt.

This package is not a browser grid or desktop Excel automation. Workbook file import/export is available from the @bilig/workpaper/xlsx and @bilig/headless/xlsx subpaths for services that need ingestion around the same WorkPaper model.

The bilig-workpaper-mcp binary still ships for hosts that specifically need an MCP stdio boundary. It is not the default evaluation path; prove the direct npm or TypeScript path first unless your tool host requires MCP. The bilig-formula-clinic binary turns a reduced XLSX into a fixture report without uploading workbook contents.

Saved workbook files are supported, but separate. Use the compatibility report or recalculation example only when the file boundary is the product contract: docs/workbook-compatibility-report.md, examples/xlsx-recalculation-node, and docs/xlsx-formula-recalculation-node.md.

Choose An Evaluation Path…