The JavaScript package never released a 2.x line, so 3.0 is the first release after 1.x and carries both steps: the record
and contract changes that 2.0 made (the same ones the Python package made in its 2.0), and the move to the Rust core. This
guide lists both. Application code that only calls logger.info(...) and friends needs no change; what changes is what is on
disk and on the wire, the Node version, and how the package is installed.
Not released yet. The 3.0 Node package (
bindings/node) is built from thedevelopbranch, is MIT licensed, and nothing is on npm yet. The platform packages for targets other than the build machine’s have not been built. The 1.x package stays as it is in thelogquill-jsrepository.
engines.node is >=22). Node 20 is unsupported.dist/).npm install, npm run build, npm run build:sdk in bindings/node.These are the changes from the 1.x migration notes, summarised.
"schema_version": "2.0". A parser that accepts “exactly these five top-level keys” breaks. Old
1.x lines need no conversion: a record with no schema_version is read as "1.0" by parseRecord.meta keys are snake_case: runId→run_id, spanId→span_id, parentSpanId→parent_span_id,
traceId→trace_id, durationMs→duration_ms, prevHash→prev_hash. Your own keys are untouched, and the options
you pass in code (RunPlugin({ runId }), span(..., { parentSpanId })) keep their camelCase names. Anything that reads or
writes those keys in meta directly must change.run_id, span_id, parent_span_id, trace_id. The package does not alter your tables:
rename the columns, or write to a new table. A DynamoDB partition key cannot be renamed; create a new table.genesisHash.meta.input_messages, output_messages, system_instructions, tool_arguments,
tool_result and state_diff are replaced by a placeholder before any plugin or transport sees them. To keep them, pass
contentPolicy: "full" (or "hash", "truncate") to Logger; children inherit it.afterLog fires when the record is handed to Rust, not when it is written, for native transports.console and fetch, which your code and tests
replace). Transports you write in JavaScript stay on the SDK’s own queue. A logger with both kinds writes them in no fixed
order.process exit (at most 5 seconds), including after
process.exit(3). A hard kill is still yours to handle (installShutdownHandlers).failsClosed on your own plugin class to get the same.NaN, Infinity and -Infinity words are accepted in input text (D19).1
from 1.0. Where an integral float written by Python (12.0) is re-read by JavaScript it hashes as 12; keep chain
input as text when it comes from another language. The details are in the legacy guide, section 4.meta keys, and any SQL or DynamoDB schema.contentPolicy for each logger that logs prompts or tool results.genesisHash if you need continuity.afterLog meaning “written”, move that check to flush().