summaryrefslogtreecommitdiff
path: root/makima/frontend/pnpm-lock.yaml
Commit message (Collapse)AuthorAgeFilesLines
* fix(frontend): regenerate pnpm-lock.yaml as v6 format + pin packageManager ↵soryu2026-05-021-1741/+1498
| | | | | | | | | | | | | | | | | | | | | | | | | | | (#123) Build env's pnpm warned "Ignoring not compatible lockfile" against the v9 lockfile produced by my last regen — older pnpm (8.x and below, which some build images still ship) only understands v6 lockfiles, and falls back to "no lockfile" mode which then errors under --frozen-lockfile: WARN Ignoring not compatible lockfile at /app/pnpm-lock.yaml ERR_PNPM_NO_LOCKFILE Cannot install with "frozen-lockfile" because pnpm-lock.yaml is absent Two-pronged fix: 1. Regenerate the lockfile in v6 format using pnpm 8.15.4 via corepack (`corepack pnpm@8.15.4 install`). The lockfile now starts with `lockfileVersion: '6.0'` again — readable by both old and new pnpm. 2. Pin `packageManager: "pnpm@8.15.4"` in package.json so build envs that respect corepack/Volta install the right version automatically instead of falling back to whatever's globally installed. Verified locally with `corepack pnpm@8.15.4 install --frozen-lockfile` (the CI command). \`tsc --noEmit\` passes. Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* fix(frontend): regenerate corrupted pnpm-lock.yaml (#122)soryu2026-05-021-1604/+544
| | | | | | | | | | | | | | | | | | | | The committed lockfile was a manual frankenstein of pnpm v6 metadata (`lockfileVersion: '6.0'` + `resolution:` blocks at the top) and v9-style snapshot entries appended below. pnpm 9 read it as a single packages: map and tripped on duplicate mapping keys (\`@floating-ui/core@1.7.5\` appeared twice; same for \`@floating-ui/utils@0.2.11\`, plus dozens of \`@lexical/*\` and \`@babel/*\` entries duplicated across the v6/v9 sections). This blew up Docker / Caddy builds: ERR_PNPM_BROKEN_LOCKFILE The lockfile at "/app/pnpm-lock.yaml" is broken: duplicated mapping key (688:3) Regenerated with \`pnpm install --no-frozen-lockfile\` against the existing package.json — net -1605 / +545 lines. \`pnpm install --frozen-lockfile\` now succeeds (the CI check), \`tsc --noEmit\` passes, \`vite build\` produces a clean bundle. Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* feat: multi-document directives with ephemeral task lifecycle (#119)soryu2026-05-021-305/+1608
| | | | | | | | | | | | | | | | | | | | | * feat: soryu-co/soryu - makima: Fix folder/file naming and breadcrumb hash bugs * WIP: heartbeat checkpoint * WIP: heartbeat checkpoint * WIP: heartbeat checkpoint * feat: soryu-co/soryu - makima: Frontend: render multiple documents per directive folder * WIP: heartbeat checkpoint * WIP: heartbeat checkpoint * WIP: heartbeat checkpoint * Fix DirectiveRevision import in openapi.rs after merge * Fix document-directives.tsx merge artifacts and add inactive status
* fix(ci): regenerate pnpm-lock.yaml for lexical deps added by #101 (#102)soryu2026-04-301-1623/+1711
| | | | | | | | | | | PR #101 added @lexical/* and lexical to makima/frontend/package.json but did not refresh the lockfile, breaking CI installs that run with the default --frozen-lockfile setting. Regenerated via `pnpm install --no-frozen-lockfile` and verified `pnpm install --frozen-lockfile` now resolves cleanly. `npx tsc --noEmit` also passes. Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* Fixup: pnpm lockfilesoryu2026-02-061-1257/+1636
|
* Initial Control systemsoryu2026-01-111-0/+101
|
* Fixup: Update pnpm lockfilesoryu2025-12-231-2/+276
|
* Update makima FE to add initial listening systemsoryu2025-12-231-0/+1765