fix(chat template): unblock next build (write narrowing + build-safe registry default)#88
Merged
Merged
Conversation
…ld-safe registry default
Two latent errors that only surfaced once the earlier smoke blockers were cleared:
- app/api/post/route.ts:95 — `contract.write.post` is a `Record<string,…>`
access, so under `noUncheckedIndexedAccess` it's possibly-undefined ("cannot
invoke"). Assert the method exists, then narrow the returned
`Receipt | DryRunResult<Receipt>` union before reading `.txHash`.
- 0g.config.ts — `NEXT_PUBLIC_MESSAGE_REGISTRY_ADDRESS` was required, and
`lib/contract.ts` reads it via `config.client()` at module load, so `next build`
with no env (the fresh-dev / CI path) threw ConfigError during page-data
collection. Default it to the zero address so the build succeeds out of the box;
`0g dev` prints the real address to paste into .env.
Verified: a fresh `npm create 0gkit-app --template chat` (published 1.12.x deps)
now compiles + collects page data + generates all routes cleanly.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #87. With the BodyInit fix in,
chat'snext buildprogressed and hit two more latent errors (verified by a freshnpm create 0gkit-app --template chatagainst published 1.12.x):contract.write.postis aRecord<string,…>access → possibly-undefined undernoUncheckedIndexedAccess. Assert the method, then narrow theReceipt | DryRunResult<Receipt>union before reading.txHash.NEXT_PUBLIC_MESSAGE_REGISTRY_ADDRESSwas required and read at module load inlib/contract.ts, sonext buildwith no env threw during page-data collection. Default it to the zero address (fresh-dev/CI build path);0g devprints the real address for .env.Verified locally: fresh chat scaffold now compiles, collects page data, and generates all routes cleanly. Template-only; no package publish.
🤖 Generated with Claude Code