netcracker/ai-for-dummies
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

build: migrate from npm to pnpm

Browse Source 
Ten git worktrees each carried their own 225 MB node_modules (1.1 GB across
five) and paid 11s per `npm ci`. pnpm hardlinks from a shared store: the same
five worktrees cost ~250 MB total, and a fresh install is 4s.

What changed beyond the mechanical rename:

- `overrides` moved to `pnpm-workspace.yaml`. pnpm 11 does not read the `pnpm`
  field in package.json *or* npm's top-level `overrides`, and it fails silently
  — the vite/defu/language-server pins would have quietly stopped applying.
- Build scripts are blocked by default in pnpm; esbuild and sharp are allowed
  explicitly via `allowBuilds` (renamed from `onlyBuiltDependencies` in 11).
- `packageManager` + `engines` pin the toolchain.
- gate.sh rejects a package-lock.json/yarn.lock/bun.lock outright, so an agent
  running `npm install` out of habit fails loudly instead of building a second,
  divergent dependency tree.
- CI bootstraps pnpm with `npm install --global pnpm@11.25.0` rather than
  corepack (unbundled as of Node 25) or pnpm/action-setup (this self-hosted
  act-runner has never run a job; fetching a third-party action is not
  something to discover on the first one).

Two pre-existing CI bugs fixed while in the file:

- the gate installed with `npm install --package-lock=false`, which discarded
  the lockfile the previous session had just fixed.
- the visual-regression step imported `playwright`, which is not a dependency,
  and `visual-regression.mjs` has no compare mode anyway — in CI it overwrote
  its own baselines and passed unconditionally. Removed with a comment; it
  comes back when it can diff.

The `publish` job is now manual (`workflow_dispatch`). During the migration
dist/ holds three HTML files against the live pages branch's ten, so publishing
on every push to main would take the site down to a stub. Restore at task 20.

HANDOVER.md's incident log still says npm where it describes what happened at
the time; that is history, not a missed rename.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Marcos Paulo
2026-09-05 04:29:42 +00:00
parent 63da0a4727
commit 48c31dc1b3
53 changed files with 5958 additions and 9642 deletions
Download Patch File Download Diff File Expand all files Collapse all files
AGENTS.md
+38 -28
View File
@@ -12,62 +12,72 @@ rules, and verification.** It is published as a static site on a self-hosted
Gitea Pages Server, and it doubles as its own teaching artifact: the hands-on
labs are dependency-free HTML/CSS/JS that workshop attendees point an agent at.
- **Current stack**: hand-written HTML + CSS + ES modules, no build step, no dependencies
- **Target stack**: Astro (see [`plans/astro-refactor/`](plans/astro-refactor/README.md)) — migration in progress
- **Current stack**: hand-written HTML + CSS + ES modules, no build step, no
dependencies
- **Target stack**: Astro (see
[`plans/astro-refactor/`](plans/astro-refactor/README.md)) — migration in
progress
- **Languages**: English and Brazilian Portuguese, toggled client-side
- **Companion service**: `vote-service/` (Go + Kubernetes) — separate lifecycle, see its own README
- **Companion service**: `vote-service/` (Go + Kubernetes) — separate lifecycle,
see its own README
## Essential commands
```bash
npm run verify # content + interaction contracts (scripts/verify.mjs) — the gate
pnpm run verify # content + interaction contracts (scripts/verify.mjs) — the gate
node scripts/audit-ui.mjs # responsive / no-external-dependency audit
node scripts/build-skill-review.mjs # regenerate skill-reviews/improved/ from catalog.js
npm run serve # python3 -m http.server 4173
pnpm run serve # python3 -m http.server 4173
```
`npm run verify` is not a formality. It is a set of ~42 string-token assertions
that pin the site's real content and interactions. **A refactor that "passes"
by deleting assertions has failed.** See
`pnpm run verify` is not a formality. It is a set of ~42 string-token assertions
that pin the site's real content and interactions. **A refactor that "passes" by
deleting assertions has failed.** See
[`.agents/context/verification.md`](.agents/context/verification.md).
## Publishing
`main` is the source of truth. The `pages` branch is what the Gitea Pages
Server actually serves, and its tree must end up identical to `main`'s. The
full procedure — including why `merge --ff-only` does *not* work here — is in
`main` is the source of truth. The `pages` branch is what the Gitea Pages Server
actually serves, and its tree must end up identical to `main`'s. The full
procedure — including why `merge --ff-only` does _not_ work here — is in
[`docs/operations-guide.md`](docs/operations-guide.md).
Adding a build step changes this contract. Read
[`.agents/context/publishing.md`](.agents/context/publishing.md) before doing so.
[`.agents/context/publishing.md`](.agents/context/publishing.md) before doing
so.
## Never touch
- `hands-on/starter/` and `hands-on/rules/` — **lab fixtures.** The exercise *is*
that they are dependency-free vanilla HTML/CSS/JS an attendee can hand to an
agent. Componentizing them destroys the lesson. They ship as static assets.
- `hands-on/starter/` and `hands-on/rules/` — **lab fixtures.** The exercise
_is_ that they are dependency-free vanilla HTML/CSS/JS an attendee can hand to
an agent. Componentizing them destroys the lesson. They ship as static assets.
- `submitted-skills/` — other people's submitted work, reproduced verbatim
- `skill-reviews/improved/` — generated; edit `skills-review/catalog.js` instead
- `vote-service/` — separate deploy lifecycle; do not fold into the site build
- `dist/`, `node_modules/` — build output, never committed
- `package-lock.json` — **committed, but never hand-edited.** Change it only
as a side effect of `npm install`. Every worktree spins up with `npm ci`,
which fails outright without it.
- `pnpm-lock.yaml` — **committed, but never hand-edited.** Change it only as a
side effect of `pnpm install`. Every worktree spins up with
`pnpm install --frozen-lockfile`, which fails outright without it.
- This project is **pnpm-only** (`packageManager` in `package.json` pins the
version). Never run `npm install` or `bun install` here — the gate rejects a
`package-lock.json`, `yarn.lock`, or `bun.lock` outright. pnpm settings live
in `pnpm-workspace.yaml`, **not** in a `pnpm` field in `package.json`; pnpm 11
ignores that field silently.
## Rules
Binding. Read the one that covers what you are about to do.
| Rule | When |
| --- | --- |
| [`astro.md`](.agents/rules/astro.md) | any `.astro` file |
| [`theming.md`](.agents/rules/theming.md) | any colour, font, or spacing value |
| [`componentization.md`](.agents/rules/componentization.md) | creating or splitting a component |
| [`animation.md`](.agents/rules/animation.md) | any motion, transition, or transform |
| [`accessibility.md`](.agents/rules/accessibility.md) | any interactive element |
| [`content-i18n.md`](.agents/rules/content-i18n.md) | any user-visible string |
| [`code-style.md`](.agents/rules/code-style.md) | always |
| [`git-worktrees.md`](.agents/rules/git-worktrees.md) | starting or finishing a task |
| Rule | When |
| ---------------------------------------------------------- | ------------------------------------ |
| [`astro.md`](.agents/rules/astro.md) | any `.astro` file |
| [`theming.md`](.agents/rules/theming.md) | any colour, font, or spacing value |
| [`componentization.md`](.agents/rules/componentization.md) | creating or splitting a component |
| [`animation.md`](.agents/rules/animation.md) | any motion, transition, or transform |
| [`accessibility.md`](.agents/rules/accessibility.md) | any interactive element |
| [`content-i18n.md`](.agents/rules/content-i18n.md) | any user-visible string |
| [`code-style.md`](.agents/rules/code-style.md) | always |
| [`git-worktrees.md`](.agents/rules/git-worktrees.md) | starting or finishing a task |
## The one thing to understand first