History

Danila Poyarkov c2aec9bacb fix(packages): make packed exports runtime-safe (#665 ) * fix(packages): make packed exports runtime-safe Make checked-in package manifests truthful for ordinary npm and Bun packing, and verify installed artifacts under both runtimes. Centralize package discovery, artifact inspection, and bounded process execution so CI and release publication share the same contracts. * ci: build package dependencies before checks Keep workspace jobs independent of ignored dist output now that public package exports consistently resolve built artifacts. * ci: preserve source-first engine tests Keep the broader dependency build for package and repository validation, but retain Core-only setup for engine shards so workspace tests continue exercising source modules. * ci: build engine shard dependencies Build the seven workspace packages imported by engine tests in dependency order. This preserves a single module instance per package and keeps each clean CI shard independent of ignored dist output. * ci: restore established package build boundaries Keep the original repository and engine job setup, and add installed artifact verification only after the existing package build. Avoid changing which module copies unrelated tests execute. * fix(packages): preserve Bun source identity in tarballs Retain source-first workspace resolution and ship complete source trees for Bun conditions. Verify clean installed consumers without overlaying archives, reuse consumer validation before release publication, and repair Bun 1.3.10 private source alias resolution. * refactor(tooling): reuse package and process utilities Use pkg-types for manifest I/O and types, tinyexec for subprocess lifecycle, and npm's pack listing for release staging. Preserve archive verification and project release invariants rather than reimplementing package-manager file selection. * refactor(tooling): resolve workspace roots at CLI boundaries Discover and validate the nearest workspace once, support explicit roots, and pass roots to reusable checks. Replace subprocess entrypoint dispatch with direct calls and preserve aggregate package diagnostics without adding arbitrary test timeout increases. * fix(release): enforce publication boundaries Use root version alignment and shared validated npm output parsing. Enforce the public npm registry policy and test verification-before-publication, mismatched artifacts, and partial retries without registry writes. * refactor(tooling): validate package responses with Valibot Express npm pack and manifest identity contracts as schemas, infer parsed output types, and preserve contextual failures and relative-path safety. Document Valibot as the first-party validation convention while retaining Zod at SDK boundaries. * refactor(tooling): validate manifests at input boundaries Share Valibot schemas for consumed manifest fields, recursive exports, supported workspace declarations, and npm registry responses. Infer domain types and reject malformed metadata instead of silently skipping it downstream. * refactor(tooling): group package helpers by ownership Colocate manifest and workspace contracts, separate npm response parsing from generic JSON handling, and split smoke packing, installation, and runtime checks. Remove the release tarball forwarding shim and consolidate its coverage in package-artifacts. Preserve public tooling exports and CLI commands.		2026-09-09 18:25:22 +03:00
..
scripts	refactor(fig): own NodeChange export policy	2026-07-18 02:41:35 +03:00
src	fix(fig): preserve explicit text alignment metadata	2026-09-02 22:54:13 +03:00
tests	fix(fig): preserve explicit text alignment metadata	2026-09-02 22:54:13 +03:00
package.json	fix(packages): make packed exports runtime-safe (#665 )	2026-09-09 18:25:22 +03:00
README.md	refactor(fig): own NodeChange export policy	2026-07-18 02:41:35 +03:00
tsconfig.json	refactor(fig): own instance interpretation	2026-07-18 02:06:34 +03:00
tsconfig.test.json	feat(fig): scaffold package shell	2026-06-30 10:51:36 +03:00
tsdown.config.ts	refactor(fig): own instance interpretation	2026-07-18 02:06:34 +03:00

README.md

@open-pencil/fig

.fig file-format package for OpenPencil.

The package owns the outer .fig archive boundary and is the staged home for Figma-specific SceneGraph conversion policy. Production SceneGraph read/write remains available through @open-pencil/core/io while conversion modules move behind this package's public API.

Current ownership:

Complete .fig archive parsing through parseFigBuffer()
.fig archive assembly through writeFigArchive()
Canvas payload and image resource handling
readFigContainer() / writeFigContainer() helpers for raw fig-kiwi payloads
.fig source and archive result types
NodeChange-to-SceneGraph property conversion, including styles, plugin metadata, text, paint, vector, and font policy, through @open-pencil/fig/node-change
Component-property, symbol-override, derived-symbol-data, and instance synchronization policy through @open-pencil/fig/instance-overrides
Effective raw-metadata precedence and invalidation over SceneGraph's format-neutral edited-field tracking
SceneGraph-to-NodeChange export conversion with an explicit glyph-outline runtime service
Package-local archive, conversion, instance, export, and dist smoke tests

Planned ownership:

Oracle-backed .fig fixtures

Non-goals:

Generic Kiwi schema/runtime internals — use @open-pencil/kiwi
Format-neutral IO registration, export targeting, CanvasKit thumbnails, or browser workers — use @open-pencil/core/io
Editor actions, renderer behavior, Vue/app UI, CLI formatting, or MCP transport

This follows the existing @open-pencil/pen pattern: a format package owns its source model/parser and SceneGraph policy, while core registers it in the shared IO system.

Checks

cd packages/fig
bun run check