chore(deps): take @preflight/runreport 0.1.1 #504

Merged

gmackie merged 1 commit from chore/relock-runreport-0-1-1 into main

2026-08-27 21:38:45 +00:00

gmackie commented

2026-08-27 21:24:39 +00:00

Owner

Takes @preflight/runreport@0.1.1, which fixes an ESM defect in 0.1.0.

0.1.0 publishes "type": "module" with extensionless relative specifiers in its emitted dist, which Node's ESM resolver rejects:

ERR_MODULE_NOT_FOUND
Cannot find module '.../dist/status' imported from '.../dist/index.js'

0.1.1 (preflight-app #22) adds the extensions at build time, leaving the source resolvable for that repo's own workspace consumer.

This is not fixing a live failure. The OpenNext build tolerates 0.1.0 — webpack resolves extensionless specifiers where Node does not, which is why #340 deployed successfully. This removes a latent failure that would only surface wherever the package meets the real ESM resolver.

Why the specifier changes too

The lockfile pins the exact version. ^0.1.0 already permits 0.1.1, but --frozen-lockfile installs what is pinned — so bumping the range alone would have changed nothing, and re-running pnpm install --lockfile-only against the old range is a no-op for the same reason.

Deliberately surgical

pnpm update @preflight/runreport -r is the obvious route and it mass-upgraded @babel, @better-auth and @expo: 3,142 added lockfile lines plus a reordering of apps/web/package.json. Reverted that and did the specifier edit plus pnpm install --lockfile-only instead.

Result is 6 lines:

-    "@preflight/runreport": "^0.1.0",
+    "@preflight/runreport": "^0.1.1",
-        version: 0.1.0(react@19.2.3)
+        version: 0.1.1(react@19.2.3)
-  '@preflight/runreport@0.1.0':
+  '@preflight/runreport@0.1.1':

The resolved integrity sha512-G8yCTDD81GPbb…MGpgRnG1Jay5w== matches the tarball published for 0.1.1.

Depends on #503 — main's Deploy ForgeGraf / test is currently 401ing on the registry because the auth block writes to $HOME/.npmrc in steps that never export HOME. Until that lands, any cold install of this package fails regardless of version.

Takes `@preflight/runreport@0.1.1`, which fixes an ESM defect in 0.1.0. 0.1.0 publishes `"type": "module"` with extensionless relative specifiers in its emitted `dist`, which Node's ESM resolver rejects: ``` ERR_MODULE_NOT_FOUND Cannot find module '.../dist/status' imported from '.../dist/index.js' ``` 0.1.1 (preflight-app #22) adds the extensions at build time, leaving the source resolvable for that repo's own workspace consumer. **This is not fixing a live failure.** The OpenNext build tolerates 0.1.0 — webpack resolves extensionless specifiers where Node does not, which is why #340 deployed successfully. This removes a latent failure that would only surface wherever the package meets the real ESM resolver. ## Why the specifier changes too The lockfile pins the exact version. `^0.1.0` already permits 0.1.1, but `--frozen-lockfile` installs what is pinned — so bumping the range alone would have changed nothing, and re-running `pnpm install --lockfile-only` against the old range is a no-op for the same reason. ## Deliberately surgical `pnpm update @preflight/runreport -r` is the obvious route and it mass-upgraded `@babel`, `@better-auth` and `@expo`: **3,142 added lockfile lines** plus a reordering of `apps/web/package.json`. Reverted that and did the specifier edit plus `pnpm install --lockfile-only` instead. Result is 6 lines: ``` - "@preflight/runreport": "^0.1.0", + "@preflight/runreport": "^0.1.1", - version: 0.1.0(react@19.2.3) + version: 0.1.1(react@19.2.3) - '@preflight/runreport@0.1.0': + '@preflight/runreport@0.1.1': ``` The resolved integrity `sha512-G8yCTDD81GPbb…MGpgRnG1Jay5w==` matches the tarball published for 0.1.1. **Depends on #503** — main's `Deploy ForgeGraf / test` is currently 401ing on the registry because the auth block writes to `$HOME/.npmrc` in steps that never export HOME. Until that lands, any cold install of this package fails regardless of version.

gmackie added 1 commit

2026-08-27 21:24:39 +00:00

chore(deps): take @preflight/runreport 0.1.1

CI / gitleaks (pull_request) Successful in 7s

Details

CI / storybook (pull_request) Successful in 1m44s

Details

forgegraph/ci CI passed

CI / ci (pull_request) Successful in 11m19s

Details

ff411b63f5

0.1.0 publishes `"type": "module"` with extensionless relative specifiers in
its emitted dist, which Node's ESM resolver rejects:

    ERR_MODULE_NOT_FOUND
    Cannot find module '.../dist/status' imported from '.../dist/index.js'

0.1.1 (preflight-app #22) fixes that by adding the extensions at build time,
leaving the source resolvable for that repo's own workspace consumer.

The OpenNext build tolerates 0.1.0 — webpack resolves extensionless specifiers
where Node does not, which is why this has not broken a deploy. So this is
removing a latent failure that would only appear wherever the package meets the
real ESM resolver, not fixing a live one.

Bumps the specifier because the lockfile pins the exact version: `^0.1.0`
permits 0.1.1, but `--frozen-lockfile` installs whatever is pinned, so a range
change alone would have changed nothing.

Deliberately surgical. `pnpm update @preflight/runreport -r` was the obvious
route and it mass-upgraded @babel, @better-auth and @expo — 3,142 added
lockfile lines and a reordering of apps/web/package.json. This is the specifier
edit plus `pnpm install --lockfile-only`: 6 lines, one package.

The resolved integrity (sha512-G8yCTDD81GPbb…) matches the tarball published
for 0.1.1.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

gmackie merged commit fdfd97f1bc into main

2026-08-27 21:38:45 +00:00

gmackie referenced this pull request from a commit

2026-08-27 21:38:47 +00:00

chore(deps): take @preflight/runreport 0.1.1 (#504)