chore(web): take @preflight/runreport 0.1.2 to unblock the deploy #508
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
gmackie/ForgeGraph!508
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "chore/runreport-012"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
main's deploy job has been red since #340 landed:
@preflight/runreport0.1.1 published"exports": { ".": "./src/index.ts" }, so the production build pulled raw TypeScript out ofnode_modules. Itsdist/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.1already 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.ymlruns 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:
The
.tsfile is no longer in the module graph. The lockfile's recordedreactpeer is unchanged from 0.1.1 (19.2.3), so this is a version bump and nothing else.