$ show unjs/pkg-types
pkg-types is a small, ESM-only TypeScript library that provides utilities and type definitions for Node.js configuration files. In production it is consumed as a dependency rather than run as a service: callers use functions such as readPackageJSON, readTSConfig, findWorkspaceDir, resolveLockfile, parseGitConfig, and sortPackage to locate, parse, serialize, and manipulate package.json, tsconfig.json, and .git/config files. It supports package.json, package.json5, package.yaml, JSONC, JSON5, YAML, and git INI formats, with lazy parser loading for JSON5/YAML to keep cold-start cost low. The code is organized into four small vertical slices — resolve, packagejson, tsconfig, and gitconfig — all re-exported from src/index.ts. Path resolution uses exsolve for module-style imports and pathe for cross-platform paths; parsing is delegated to confbox. The primary data flow is simple: an input path is resolved to the nearest or farthest matching file, the file is read and parsed into a typed object, and optionally written back after mutation. There are no API endpoints, data stores, or background processes. Notable implementations include a boundary-aware nearest/farthest file finder that stops at node_modules, workspace directory detection from pnpm/lerna/turbo/rush/deno markers or git config/lockfiles, a Proxy-based updatePackage that auto-creates common package.json map fields during mutation, deterministic package.json sorting/normalizing, and conversion of git's subsection INI format ([remote "origin"]) into generic dotted INI keys for parsing and back on stringify. The project has solid Vitest coverage, type-level tests, and modern CI using oxlint, oxfmt, and obuild. One minor limitation is that git config subsection round-tripping is regex-based and not fully robust for unusual subsection names containing slashes or other non-word characters.
The LLM identified 4 files worth highlighting for reuse:
Implements findFile, findNearestFile, and findFarthestFile: an async file-discovery utility that traverses up or down directory trees, supports multiple candidate filenames, stops at a configurable root boundary (default node_modules), and accepts a custom async test predicate. The path-segment handling with leading-slash restoration and root-boundary limiting is non-obvious and clean. It depends only on pathe and node:fs, making it easy to extract into another project.
Contains sortPackage, normalizePackage, and updatePackage. sortPackage reorders known package.json fields according to community conventions while preserving unknown-field relative order, and alphabetically sorts dependency maps and scripts. normalizePackage builds on this by removing invalid dependency declarations. updatePackage wraps a package object in a Proxy that lazily auto-creates common map fields (scripts, dependencies, etc.) when accessed, allowing ergonomic in-place mutation of package manifests while preserving the original file format. The pure sorting/normalizing functions are standalone and reusable.
parseGitConfig and stringifyGitConfig convert git's subsection INI syntax ([remote "origin"], [branch "main"]) into generic dotted INI keys ([remote.origin], [branch.main]) and back. This lets a standard INI parser handle git config files without custom grammar, and the reverse transformation restores git's canonical format on write. The two functions are independent of the rest of the module and could be reused in any tool that needs to read or write .git/config files.
A hand-maintained, comprehensive CompilerOptions interface for tsconfig.json files. It models dozens of compiler options, marks deprecated/removed TypeScript options inline with JSDoc, and intentionally uses `any` for enum-like string options (target, module, moduleResolution, jsx) so real-world tsconfig files type-check. The type definitions are self-contained and can be extracted as a standalone schema for any TypeScript tooling that reads or writes tsconfig files.