Runbook: Tools: Data

Auto-generated from ./src/tools/data/index.ts. Do not edit by hand — run node scripts/gen-runbooks.mjs.

Import path: personaforge/tools/data · Public symbols: 0 · Guide: /guide/tools

What it is

personaforge/tools/data is a public entry point of personaforge. Import it directly; you only pull in this feature's code (subpath exports are tree-shakeable and optional native deps load lazily).

Install

npm i personaforge
# or: bun add personaforge · pnpm add personaforge · yarn add personaforge

Import

import 'personaforge/tools/data';

Public API surface

• No named runtime exports; import for side effects or types.

Minimal use

Real example from the tools guide:

import {
  BigQueryToolkit,
  CsvToolkit,
  DatabaseToolkit,
  Neo4jToolkit,
  RedisToolkit,
} from 'personaforge/tools/data';

Verify it works

• Type-check: npx tsc --noEmit resolves personaforge/tools/data with no missing-module error.
• Runtime: node -e "import('personaforge/tools/data').then(m => console.log(Object.keys(m)))" lists the exports above.
• Behavior: follow the runnable example in /guide/tools.

Common failures

• Cannot find module 'personaforge/tools/data' — package not installed or stale build; run npm i personaforge and rebuild.
• Cannot find module '<peer>' at call time — this feature lazy-loads an optional native/SDK dep; install the one named in the error.
• Type errors after upgrade — check CHANGELOG.md for the symbol you import; names above are the current contract.

Rollback

• Remove the import and the feature is gone from your bundle (subpaths are isolated; nothing else depends on importing it).
• Pin a known-good version: npm i personaforge@<version>.

Related

• Full index: /runbooks/ · llms.txt
• Concept guide: /guide/tools