chore(web): take @preflight/runreport 0.1.2 to unblock the deploy #508

Merged
gmackie merged 1 commit from chore/runreport-012 into main 2026-08-27 22:41:28 +00:00
Owner

main's deploy job has been red since #340 landed:

Turbopack build failed with 1 error:
./node_modules/@preflight/runreport/src/index.ts
Error: Unknown module type

@preflight/runreport 0.1.1 published "exports": { ".": "./src/index.ts" }, so the production build pulled raw TypeScript out of node_modules. Its dist/ was built and shipped but unreachable through the exports map. 0.1.2 fixes the map (gmackie/preflight-app#23) and is already on npm.forgegraf.com.

^0.1.1 already admitted 0.1.2; the pin was in the lockfile. Bumping the range too so the intent is on the record.

Why CI was green when #340 merged

Nothing in ci.yml runs the Next production build. Only the deploy job does. Typecheck, lint, and tests all resolve the package through vitest/tsc, which read TypeScript happily — the failure only appears where Turbopack refuses to.

Verification

In this tree after install, rather than inferred from the manifest:

$ node -e 'import.meta.resolve("@preflight/runreport")'   # from apps/web
file:///.../node_modules/@preflight/runreport/dist/index.js

The .ts file is no longer in the module graph. The lockfile's recorded react peer is unchanged from 0.1.1 (19.2.3), so this is a version bump and nothing else.

main's deploy job has been red since #340 landed: ``` Turbopack build failed with 1 error: ./node_modules/@preflight/runreport/src/index.ts Error: Unknown module type ``` `@preflight/runreport` 0.1.1 published `"exports": { ".": "./src/index.ts" }`, so the production build pulled raw TypeScript out of `node_modules`. Its `dist/` was built and shipped but unreachable through the exports map. 0.1.2 fixes the map (gmackie/preflight-app#23) and is already on npm.forgegraf.com. `^0.1.1` already admitted 0.1.2; the pin was in the lockfile. Bumping the range too so the intent is on the record. ## Why CI was green when #340 merged Nothing in `ci.yml` runs the Next production build. Only the deploy job does. Typecheck, lint, and tests all resolve the package through vitest/tsc, which read TypeScript happily — the failure only appears where Turbopack refuses to. ## Verification In this tree after install, rather than inferred from the manifest: ``` $ node -e 'import.meta.resolve("@preflight/runreport")' # from apps/web file:///.../node_modules/@preflight/runreport/dist/index.js ``` The `.ts` file is no longer in the module graph. The lockfile's recorded `react` peer is unchanged from 0.1.1 (`19.2.3`), so this is a version bump and nothing else.
chore(web): take @preflight/runreport 0.1.2 to unblock the deploy
All checks were successful
CI / gitleaks (pull_request) Successful in 6s
CI / storybook (pull_request) Successful in 1m49s
forgegraph/ci CI passed
CI / ci (pull_request) Successful in 11m43s
d86676e219
main's deploy job has been failing since #340 landed:

    Turbopack build failed with 1 error:
    ./node_modules/@preflight/runreport/src/index.ts
    Error: Unknown module type

0.1.1 published `"exports": { ".": "./src/index.ts" }`, so the production
build pulled raw TypeScript out of node_modules. Its `dist/` was built
and shipped but unreachable through the exports map. 0.1.2 points exports
at dist (gmackie/preflight-app#23).

CI never caught this because nothing in ci.yml runs the Next production
build -- only the deploy job does, which is why #340 was green when it
merged.

Verified in this tree rather than assumed: after install,
`import.meta.resolve("@preflight/runreport")` from apps/web returns
dist/index.js, so the .ts file is no longer in the module graph.

The lockfile's recorded react peer is unchanged from 0.1.1 (19.2.3), so
this is a version bump and nothing else.
gmackie deleted branch chore/runreport-012 2026-08-27 22:41:28 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
gmackie/ForgeGraph!508
No description provided.