mirror of
https://github.com/hanzo-apps/dataroom.git
synced 2026-10-30 14:47:36 +00:00
zooqueen
7ef03a2bdd
cloud carried a hand-vendored byte-copy of goja/bundle.js because this repo is a TS app with no Go module, so nothing checked what it embedded. The copy had already drifted: cloud's carried the link deny-list and this one did not. A std-lib-only embed module — the same shape github.com/hanzoai/sign has — makes the bundle a dependency cloud requires at a version and records in go.sum, so the three folds (sign, captable, dataroom) are all pinned the same way and there is no second copy to drift. The deny-list the copy was ahead by lands here with it: an address on a link's deny list is refused even when the allow list would admit it, checked first so deny cannot be bypassed.
22 lines
1.1 KiB
AMPL
22 lines
1.1 KiB
AMPL
// hanzoai/dataroom — Go embed module.
|
|
//
|
|
// This repo's PRIMARY artifact is the Hanzo Dataroom application (TypeScript/
|
|
// Next.js + Prisma). This tiny Go module exists ONLY so the unified hanzoai/cloud
|
|
// binary (HIP-0106, task #101) can embed the ESM-free goja bundle
|
|
// (goja/bundle.js) — the port of the dataroom domain (documents, data rooms,
|
|
// shareable links with access controls, viewers, per-page view analytics) — and
|
|
// run it in-process via dop251/goja, backed by Hanzo Base/SQLite. Cloud imports
|
|
// github.com/hanzoai/dataroom and gets Bundle().
|
|
//
|
|
// It is what makes the bundle a PINNED dependency rather than a hand-copied
|
|
// file: cloud requires this module at a version and records its checksum in
|
|
// go.sum, the same way it takes github.com/hanzoai/sign and
|
|
// github.com/hanzoai/captable. There is no second copy of the bundle to drift.
|
|
//
|
|
// std-lib only — no third-party Go deps. The object-storage seam and the bcrypt
|
|
// primitive live in cloud (Go host-functions); this module carries only the
|
|
// domain bundle.
|
|
module github.com/hanzoai/dataroom
|
|
|
|
go 1.26.4
|