zeekayandHanzo Dev e98c0b9065 Resolve the lockfile to the versions the manifest asks for ...

The manifest moved and the lockfile did not, so npm ci refused on a clean
checkout: twelve direct dependencies were behind what package.json requires,
@hanzo/design and next and react and typescript among them. A lockfile that
disagrees with its manifest is not a lockfile — it is a second, contradictory
manifest, and the one npm trusts least.

next-env.d.ts moves with it. Next writes that file, and the version the lock
now resolves writes one more reference into it.

Co-authored-by: Hanzo Dev <[email protected]>

2026-09-04 00:14:33 -07:00

..

public

the Hanzo mark, a Papers link that resolves, and an icon

2026-08-21 00:25:47 -07:00

src

Form controls and code take the site's faces

2026-09-03 23:48:14 -07:00

next-env.d.ts

Resolve the lockfile to the versions the manifest asks for

2026-09-04 00:14:33 -07:00

next.config.mjs

proofs: CRDT privacy, commutativity, anchoring, site

2025-12-15 12:00:00 -08:00

package-lock.json

Resolve the lockfile to the versions the manifest asks for

2026-09-04 00:14:33 -07:00

package.json

every Hanzo dependency is the version npm serves

2026-09-01 16:17:00 -07:00

postcss.config.mjs

proofs: CRDT privacy, commutativity, anchoring, site

2025-12-15 12:00:00 -08:00

tsconfig.json

proofs: CRDT privacy, commutativity, anchoring, site

2025-12-15 12:00:00 -08:00