Publint usage in CopilotKit codebase.

#opensource #publint #copilotkit #linter

In this article, we review Publint package. You will learn:

What is Publint?
Publint script in CopilotKit codebase.

What is Publint?

publint lints npm packages to ensure the widest compatibility across environments, such as Vite, Webpack, Rollup, Node.js, etc.

How it works?

Given an npm package, the site downloads the tarball and runs publint against it in a web worker. For larger packages, it may take a while to download and lint.

Below are Publint examples, demonstrating how Publint works. This is applied on the Semver package.

Publint script in CopilotKit codebase.

I found the Publint script in the copilotkit/packages/agentcore-runner/package.json.

 "scripts": {
    ...
    "publint": "publint .",
    ...
  },

This script runs publint against the current package, agentcore-runner.

Below is a comment I found above the AgentCoreRunner.

/**
 * AgentCore stores conversation history server-side via AgentCoreMemorySaver /
 * AgentCoreMemorySessionManager. When CopilotKit reconnects to an existing
 * thread (e.g. page refresh), two issues arise that this runner fixes:
 *
 * 1. Unknown threads — CopilotKit may call `connect()` for a thread that has
 *    never had a `run()` (first load). The base runner would error; we emit an
 *    empty snapshot instead so the UI initialises cleanly.
 * 2. Missing tool-call results — AgentCore's replayed history contains assistant
 *    messages with tool calls but no corresponding TOOL_CALL_RESULT events.
 *    CopilotKit needs those to reconcile its message state, so we synthesise
 *    empty results for each past tool call before the snapshot.
 */

Below is another example of Publint on uuid