Analog integration baseline

Generated by pnpm test:analog at 2026-10-28T16:56:05.925Z. This report is regenerated on every run; it reflects the most recent execution against baseline 02b06a17dbd5e9221bf02367beadabfbf84e54ee.

Scope. One question: how does the current @strata-sc/core / @strata-sc/h3 fit inside a real Angular + Analog application (apps/analog-fixture), built and run with the stock Analog pipeline? No Strata Vite plugin and no decorator transform. @strata-sc/core decorators are used in src/server/**, and @strata-sc/analog registers a controller on the Nitro router through Nitro's public plugin API. It makes no claim beyond the single tuple below and the two modes exercised (dev server, production server).

Result of this run: every recorded expectation held.

Exact dependency tuple

Node v22.23.1, pnpm 10.30.1. The fixture's manifests follow the official create-analog@2.7.2 template-latest. "Resolved" is read from the installed packages on disk (symlinks followed), not from package.json.

Lockfile (pnpm-lock.yaml, packages: section) — every version present in the whole workspace graph:

Runtime graph: which H3?

h3 as resolved from each consumer, and the top-level APIs that copy actually exports (loaded from disk, not inferred):

• Resolved Nitro: 2.13.4 (nitropack, preset node-server), recorded by the built server in dist/analog/nitro.json. Production start command: node dist/analog/server/index.mjs.
• The built production server does not load an installed h3: Nitro inlines it into dist/analog/server/chunks/nitro/nitro.mjs, which defines createApp: yes, createRouter: yes and an H3 v2 H3 class: no.
• Analog/Nitro run H3 v1; @strata-sc/h3 targets H3 v2. They are different majors with different APIs (createApp/createRouter vs the H3 class).

Angular/Analog compilation and standard decorators

The same consumer-authored @Controller() / @Get() (standard TC39 decorators from @strata-sc/core) was observed in the two places Analog compiles TypeScript. Classes: A works, B compile-time failure, C build succeeds but runtime fails, D other.

• Nitro server routes (src/server/**, native Analog API routes) are bundled by Nitro's own Rollup + esbuild pipeline, not by the Angular compiler. esbuild lowers standard decorators on its own; getControllerDefinition() returns the right metadata in dev and production.
• The Angular-compiled graph (pages, components, anything a page imports) uses the stock Analog template's experimentalDecorators: true: the Angular compiler type-checks the consumer's decorators as legacy decorators and fails the build (class B). With experimentalDecorators: false the decorators are lowered and the metadata is correct in the dev server, but the production server's SSR of that page fails (class C).
• Nothing here modified Strata or added a transform. The baseline build uses the stock vite.config.ts; the G arms use vite.probe.config.ts, which differs only by also building the probe page and by selecting which tsconfig Analog's Angular plugin reads.

Production build

pnpm --filter @strata-fixtures/analog run build (vite build) exit status: 0.

Native Analog server route (/api/native)

Strata metadata through @strata-sc/core only (/api/strata-core)

H3 seam and @strata-sc/h3

Nitro hands its app to server plugins through the public defineNitroPlugin() from nitropack/runtime; NitroApp.h3App and NitroApp.router are part of Nitro's exported NitroApp type. A fixture plugin observed (never modified) what a real production server passes:

{
  "nitroAppKeys": ["captureError", "h3App", "hooks", "localCall", "localFetch", "router"],
  "h3App": {
    "typeofValue": "object",
    "constructorName": "Object",
    "ownKeys": ["handler", "options", "resolve", "stack", "use", "websocket"],
    "hasOn": false,
    "hasUse": true,
    "hasStack": true,
    "hasFetch": false,
    "hasRoutes": false
  },
  "router": {
    "typeofValue": "object",
    "constructorName": "Object",
    "ownKeys": [
      "add",
      "connect",
      "delete",
      "get",
      "handler",
      "head",
      "options",
      "patch",
      "post",
      "put",
      "trace",
      "use"
    ],
    "hasOn": false,
    "hasUse": true,
    "hasStack": false,
    "hasFetch": false,
    "hasRoutes": false
  }
}

registerControllers() in @strata-sc/h3 (packages/h3/src/register-controllers.ts) calls app.on(...): yes. The Nitro h3App has .on: no.

Outcome B. Nitro exposes its H3 through a public plugin hook, but as an H3 v1 App (use/stack) and v1 Router, not an H3 v2 H3 instance. The current @strata-sc/h3 cannot mount directly.

@strata-sc/h3 was not mounted in Analog: the only H3 app the public seam provides is an H3 v1 App, and passing it to a function typed for the H3 v2 H3 class would need an unsafe cast between majors, a fake H3 instance, or a second router — all ruled out for this experiment.

@strata-sc/analog: a Strata controller through the public Nitro router seam

src/server/plugins/strata.ts is a Nitro server plugin that calls registerControllers(nitroApp.router, [UsersController, LifecycleController]) and, separately, registerControllers(nitroApp.router, [GreetingController], { controllerFactory }). None of these controllers is reachable from any file under src/server/routes/**: no file-system route wraps them. The routes below exist only because @strata-sc/analog read their @strata-sc/core metadata and registered them on nitroApp.router.

Controllers are request-scoped: LifecycleController and GreetingController increment an instance field, and each is requested twice in a row per mode. Both answers carry calls: 1, so each request got a new instance. GreetingController receives a plain GreetingService only from the fixture's controllerFactory (Strata's default factory would leave it null).

The native Analog route (/api/native, above) answers in the same run, on the same router.

Experiment (SPEC-003): Angular DI through controllerFactory

Specified by SPEC-003; the source trace, candidate comparison and verdict are in Analog DI feasibility. src/server/plugins/strata-angular-di.ts registers CatalogController with a factory owned by the fixture, not by @strata-sc/analog (which has no Angular dependency). The plugin bootstraps an application injector with Angular's public createApplication() on a platformServer(), as Analog does for its server functions, so @Injectable({ providedIn: 'root' }) CatalogService resolves there once per process. For each request the factory creates a child createEnvironmentInjector() providing STRATA_REQUEST, RequestIdentity and RequestAudit, registers onCleanup(() => requestInjector.destroy()), and builds the controller with runInInjectionContext(requestInjector, () => new Controller()). The controller resolves its dependencies with inject() in field initializers and keeps them across await; it also calls inject() inside its handler, before and after an await, and reports the outcome. No Nitro request/afterResponse/error hook or event.context slot is used (checked on the sources); only the application is destroyed in Nitro's close hook.

Each scenario is bracketed by two reads of /api/strata-angular-di-stats, once each, with no retry; the table shows after − before, except for levels shown as read: injectorsAlive, maxInjectorsAlive and catalogInstances (the providedIn: 'root' service is created lazily by the first request and must stay at one). Overlap is enforced, not assumed: ?meet=<key> holds a handler at a rendezvous that answers met: true only if a second request with the same key reaches it while the first is still suspended, and met: false after 5 s otherwise. The lone request is the negative control.

Expected: overlapping requests both answer met: true, share catalogInstance: 1, and get different identity values, each bound to its own product id; the controller and RequestAudit see the same RequestIdentity within a request; the injected STRATA_REQUEST is the handler's argument; inject() in a handler throws NG0203 before and after an await; no injector is destroyed before the handler's last await settles; and every request injector created — on success, synchronous throw or asynchronous rejection — is destroyed, running RequestIdentity.ngOnDestroy() and the controller's DestroyRef callback, before the response arrives. Limits: the application injector is not the injector of an Analog SSR render or of Analog's server functions (no supported seam reaches either), and cleanup covers the controller invocation, not a streamed response body. The experiment's files carry STRATA_ANALOG_ANGULAR_DI_MARKER, scanned in the module-graph section below.

Package boundary. @strata-sc/analog declares:

Bare module specifiers in the built package (what a consumer's bundler and tsc must resolve):

The fixture reaches the package only through @strata-sc/analog (its exports entry, built dist).

Type check against Nitro's real types. A generated probe calls registerControllers(nitroApp.router, …) inside defineNitroPlugin and type-checks it against the nitropack Analog resolves: the router is accepted without a cast, and nitroApp.h3App (H3 v1 App) is rejected — a @ts-expect-error negative control that fails if the parameter were loosely typed. Command: pnpm exec tsc -p .strata-typecheck/tsconfig.json (exit 0).

Server/client module graph baseline

STRATA_ANALOG_SERVER_ONLY_MARKER is used only from src/server/strata/hello.controller.ts (imported by Nitro routes). STRATA_ANALOG_CLIENT_CONTROL_MARKER is a positive control that lives in a client page, so a scan that finds it proves the scanner can see client output at all.

STRATA_ANALOG_REGISTERED_CONTROLLER_MARKER is used only by the controller registered through @strata-sc/analog (src/server/strata/users.controller.ts, imported only by the Nitro plugin). STRATA_ANALOG_CONTROLLER_FACTORY_MARKER is used only by src/server/strata/greeting.controller.ts, registered with a custom controllerFactory:

Expected and observed: server output contains the server-only markers and the adapter; dist/client, dist/analog/public and dist/ssr do not; no @strata-sc/h3 code is in any output. This is only a baseline — nothing here is a Server Component or a guarantee for future code.

Commands

Checks

Blockers discovered

1. H3 major mismatch at the seam. Analog 2.7.2 → nitropack 2.13.4 → H3 v1. The only public H3 handle (nitroApp.h3App) is an H3 v1 App with no .on(). @strata-sc/h3 needs an H3 v2 H3 instance, so it cannot mount directly (Outcome B). Resolved for Analog without touching it: @strata-sc/analog is a sibling adapter on nitroApp.router and does not depend on @strata-sc/h3. @strata-sc/h3 stays an H3 v2-only adapter.

2. Phantom h3 dependency in @analogjs/vite-plugin-nitro@2.7.2. It imports h3 without declaring it. Under pnpm's default hoisting, in a workspace that also contains @strata-sc/h3, the bare import resolved to H3 v2 and the Vite config failed to load. This repo now declares the H3 major Nitro 2 uses through packageExtensions in pnpm-workspace.yaml (workspace configuration only; no Strata code changed). Recorded failure before that workaround:

   failed to load config from <repo>/apps/analog-fixture/vite.config.ts
   error during build:
   file://<repo>/node_modules/.pnpm/@analogjs+vite-plugin-nitro@2.7.2_…/node_modules/@analogjs/vite-plugin-nitro/src/lib/utils/register-dev-middleware.js:1
   import { createEvent } from 'h3';
            ^^^^^^^^^^^
   SyntaxError: The requested module 'h3' does not provide an export named 'createEvent'
   

3. Angular pipeline treats consumer decorators as legacy with the stock experimentalDecorators: true (arm G1, class B). Turning it off makes the dev server work but exposes the next item.

4. Production SSR of Angular-compiled standard decorators fails on tslib (arm G2-prod, class C): TypeScript's standard-decorator lowering imports __esDecorate/__runInitializers from tslib (importHelpers: true); Nitro traces only tslib's module-condition files, so Node's import + node resolution of tslib/modules/index.js fails at runtime. SSR then returns HTTP 200 with an empty router outlet — a silent failure. Not investigated further or fixed here.

5. Repo-wide Node floor (addressed). @angular/build@22 and create-analog@2.7.2 require Node ^22.22.3 || ^24.15.0 || >=26, and engine-strict=true makes pnpm install fail below that. The root/workspace development floor is now >=22.22.3. The public engines of @strata-sc/core, @strata-sc/h3 and @strata-sc/analog stay >=22: only the Angular fixture needs the higher patch. CI (node-version: 22) resolves the latest 22.x; that it satisfies the floor was not verified.

6. Unchanged, not attempted: the H3 v2 / crossws declaration blocker from SPEC-001/SPEC-002. The fixture never imports @strata-sc/h3, so it neither triggers nor hides it.

Non-blocking observations from pnpm install: pnpm ignored the install scripts of esbuild, @parcel/watcher, lmdb and msgpackr-extract (builds and servers worked without approving them), and warns that @angular/build wants vitest@^4.0.8 while the workspace root has vitest@5.0.1 (only used by Angular's own unit-test builder, which the fixture does not run).

Other Analog lines (npm metadata only — not installed, not executed)

The alpha line is the only one whose declared runtime is H3 v2 (same major as @strata-sc/h3). Whether that line exposes a compatible H3 app is unverified; this fixture did not run it.