Skip to content

feat(deno): developer-ecosystem workspace finalisation — root deno.json with workspace field (STEP 7 closeout)#100

Merged
hyperpolymath merged 1 commit into
mainfrom
campaign-253/workspace-finalisation-dev-eco
May 31, 2026
Merged

feat(deno): developer-ecosystem workspace finalisation — root deno.json with workspace field (STEP 7 closeout)#100
hyperpolymath merged 1 commit into
mainfrom
campaign-253/workspace-finalisation-dev-eco

Conversation

@hyperpolymath
Copy link
Copy Markdown
Owner

Summary

Completes the STEP 7 workspace finalisation acceptance criterion (1) for developer-ecosystem from hyperpolymath/standards#275: add deno.json at repo root with workspace array listing all 40 sub-projects with their own deno.json.

Per the STEP 6 closure (hyperpolymath/standards#273), the per-sub-project migrations were already landed via the cross-cutting workflow-modernisation + tooling sweeps over April-May 2026 (19 of 23 in-scope manifests paired with deno.json; the remaining 4 are dependency-shim Class C npm-publishable consumer artifacts where Deno-native exposure isn't a priority). The workspace-root coordination is the closeout task per STEP 7's body.

Workspace member breakdown (40 members)

Tree Members Notes
affinescript-ecosystem/ 3 affinescript-deno-test, rattlescript/affinescript/packages/{affine-js,affine-ts}
aggregate-library 1 Always Deno-native
cadre-router + nested 2 top-level + tea-router-pkg
cadre-tea-router 1 top-level peer
coq-ecosystem/coq-jr 1 Class A migrated
deno-ecosystem/projects/ 2 beamdeno, deno-bunbridge (always Deno-native)
rescript-ecosystem/ 29 packages/, cadre-router*, cadre-tea-router, idaptik-rescript13-staging*, rescript-{deno-starter,dom-mounter,evangeliser,tea,vite}
v-ecosystem/v-deno 1 V-lang Deno binding

Top-level tasks build-all/test-all/fmt/lint delegate to per-member tasks via deno task --recursive.

What is intentionally NOT included

  • rescript-ecosystem/rescript/ — upstream-fork carve-out (22 manifests) covered by hypatia :nodejs_detected rescript/ path_allow_prefix
  • rescript-ecosystem/packages/core/compiler-source/ — vendored upstream rescript snapshot (45 manifests, separate version line 13.0.0-alpha.1 vs alpha.3 of the active fork)
  • affinescript-ecosystem/.../editors/{vscode,tree-sitter-affinescript}/ — VSCode + tree-sitter Class C carve-outs
  • 4 dependency-shim Class C npm-publishable manifestsaffinescript-vite, rescript-grpc-runtime, rescript-string-power, rescript-vite-config — declared in STEP 6 closure as residual

After this PR merges, developer-ecosystem satisfies acceptance criterion (1) of hyperpolymath/standards#275; the remaining residuals are out-of-scope per the umbrella body's Out of scope carry-forward.

Test plan

  • CI green (additive only — no existing manifest touched)
  • deno task --version recognises the workspace root
  • Hypatia :nodejs_detected scan stays quiet (zero package-lock.json in repo)

Refs hyperpolymath/standards#275 (this completes the developer-ecosystem portion).
Refs hyperpolymath/standards#253 (umbrella npm → Deno migration).
Refs hyperpolymath/standards#273 (STEP 6 closeout — substantially-done declaration).

🤖 Generated with Claude Code

…rkspace field (STEP 7 closeout)

Completes the STEP 7 workspace finalisation acceptance criterion (1) for
developer-ecosystem from hyperpolymath/standards#275: add `deno.json` at
repo root with `workspace` array listing all 40 sub-projects that have
their own `deno.json`.

This was the missing acceptance gate. Per the STEP 6 closure comment on
hyperpolymath/standards#273, the per-sub-project migrations were already
landed via the cross-cutting workflow-modernisation + tooling sweeps over
April-May 2026 (19 of 23 in-scope manifests paired with deno.json; the
remaining 4 are dependency-shim Class C npm-publishable consumer artifacts
where Deno-native exposure isn't a priority). The workspace-root
coordination is the closeout task per STEP 7's body.

## Workspace member breakdown

- `affinescript-ecosystem/` (3 members)
- `aggregate-library` (1)
- `cadre-router` + nested `tea-router-pkg` (2)
- `cadre-tea-router` (1)
- `coq-ecosystem/coq-jr` (1)
- `deno-ecosystem/projects/` (2)
- `rescript-ecosystem/` (29 across packages/, cadre-router, cadre-tea-router, idaptik, rescript-*)
- `v-ecosystem/v-deno` (1)

Top-level tasks `build-all`/`test-all`/`fmt`/`lint` delegate to per-member
tasks via `deno task --recursive`.

## What is intentionally NOT included

- `rescript-ecosystem/rescript/**` — upstream-fork carve-out (22 manifests)
  covered by hypatia `:nodejs_detected` `rescript/` path_allow_prefix
- `rescript-ecosystem/packages/core/compiler-source/**` — vendored upstream
  rescript snapshot (45 manifests, separate version line from the active
  `rescript/` fork)
- `affinescript-ecosystem/.../editors/{vscode,tree-sitter-affinescript}/**`
  — VSCode + tree-sitter Class C carve-outs
- 4 dependency-shim Class C npm-publishable manifests
  (`affinescript-vite`, `rescript-grpc-runtime`, `rescript-string-power`,
  `rescript-vite-config`) — declared in STEP 6 closure as residual

After this PR merges, developer-ecosystem satisfies acceptance criterion (1)
of hyperpolymath/standards#275; the remaining residuals are out-of-scope
per the umbrella body's `Out of scope` carry-forward.

Refs hyperpolymath/standards#275 (this completes the developer-ecosystem portion)
Refs hyperpolymath/standards#253 (umbrella npm → Deno migration)
Refs hyperpolymath/standards#273 (STEP 6 closeout — substantially-done declaration)

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@hyperpolymath hyperpolymath enabled auto-merge (squash) May 31, 2026 07:17
@hyperpolymath hyperpolymath merged commit 2c35dff into main May 31, 2026
0 of 19 checks passed
@hyperpolymath hyperpolymath deleted the campaign-253/workspace-finalisation-dev-eco branch May 31, 2026 07:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant