Skip to content

chore(deps): install the hREA GraphQL adapter from npm, drop the vendored tarball - #177

Open
Soushi888 wants to merge 1 commit into
devfrom
chore/adapter-from-npm
Open

Soushi888 wants to merge 1 commit into
devfrom
chore/adapter-from-npm

Conversation

@Soushi888

@Soushi888 Soushi888 commented Nov 3, 2026 •

Copy link
Copy Markdown
Collaborator

SoushAI analysis. Drafted by Soushi's AI assistant, reviewed and posted by @Soushi888.

Summary

The hREA GraphQL adapter is on npm: @valueflows/[email protected], published 2026-11-03 by hREA's CI through npm trusted publishing, with SLSA provenance (h-REA/hREA#412). The UI now installs it from the registry, and the tarball #155 vendored for #153 goes. vendor/hrea, the submodule the hApp builds its hrea DNA from, is untouched.

Changes
  • ui/package.json: file:../vendor/…tgz becomes ^0.700.0-rc.0. bun.lock regenerated with the flake's bun (1.2.13, the one CI uses); its only change is that entry, now pinned to the npm integrity sha512-HdnnB44Q…MSnGw==, the value npm view … dist.integrity returns.
  • Removed: vendor/valueflows-vf-graphql-holochain-0.700.0-rc.0.tgz, its .sha256, and vendor/README.md, which described only that tarball.
  • Docs: ui/README.md, documentation/hREA/integration-strategy.md (the read-only bound on the adapter is unchanged, only where it comes from), documentation/specifications/ui_architecture.md.
Same code as the vendored copy

The published tarball and the vendored one were unpacked side by side: diff -r differs in package.json only, which gains repository, homepage and bugs (hREA #418 added them so npm could attest provenance). Every JavaScript and type file is identical.

Verification

Run in nix develop on this branch, and on a clean origin/dev worktree for comparison:

this branch origin/dev
bun install no changes
svelte-check 0 errors 0 after .svelte-kit sync (1 on a cold first run, both sides)
vitest (chromium) 81/82 81/82
prettier --check . in ui/ 59 files flagged 59 files flagged
vite build --mode production done

The one failing spec, src/routes/page.svelte.spec.ts, cannot resolve virtual:uno.css from +layout.svelte. It fails identically on dev and has nothing to do with the adapter. The files this branch touches pass Prettier.

Schema smoke: createHolochainSchema from the installed npm package, with a dummy cell, builds and exposes the Proposal, Agreement, Commitment and EconomicEvent surface, fulfills and clauseOf included. The adapter is not wired to any screen yet, so this is the check that the real module loads.

In CI on 4fbc22c: build, rustfmt, all seven Sweettest legs (governance, misc, nondominium a and b, person, resource) and the Playwright e2e job passes 23/23 in 2.6 minutes.

…ored tarball

@valueflows/vf-graphql-holochain 0.700.0-rc.0 is on npm (h-REA/hREA#412),
published by hREA's CI with provenance. The UI now depends on
^0.700.0-rc.0 from the registry, and bun.lock (regenerated with the
flake's bun) pins its npm integrity. The published package is the vendored
tarball's code, file for file; only its package.json gains repository,
homepage and bugs.

The tarball, its .sha256 and the vendor README that described it go.
vendor/hrea, the submodule the hApp builds its hrea DNA from, stays.
@Soushi888 Soushi888 added frontend Frontend development - UI, SvelteKit, Effect-TS hrea hREA integration - Holochain Resource-Event-Agent ValueFlows backend labels Nov 3, 2026
@Soushi888
Soushi888 marked this pull request as ready for review November 4, 2026 00:37

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

frontend Frontend development - UI, SvelteKit, Effect-TS hrea hREA integration - Holochain Resource-Event-Agent ValueFlows backend

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant