fix: correct read.js API calls in multi-author-blog guide#787
Open
NoahMaizels wants to merge 1 commit intomasterfrom
Open
fix: correct read.js API calls in multi-author-blog guide#787NoahMaizels wants to merge 1 commit intomasterfrom
NoahMaizels wants to merge 1 commit intomasterfrom
Conversation
Two bugs in the read.js code block:
1. reader.download() returns { payload, feedIndex } with no reference
property — replace with reader.downloadReference() which returns
{ reference, feedIndex } as needed by bee.downloadFile().
2. bee.downloadFile() returns data as a bee-js Bytes object, not an
ArrayBuffer — new TextDecoder().decode(authorsData.data) throws;
use authorsData.data.bytes to get the underlying Buffer.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
✅ Deploy Preview for test-twitter-preview-testing-3 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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.
Summary
Two bugs in the
read.jscode block of the Multi-Author Blog guide, found by running the code against a live Bee node:reader.download()→reader.downloadReference():download()returns{ payload, feedIndex, feedIndexNext }with noreferenceproperty. The code then passesindexResult.reference(which isundefined) tobee.downloadFile(), crashing immediately.downloadReference()returns{ reference, feedIndex, feedIndexNext }as needed. Fixed in all three call sites.authorsData.data→authorsData.data.bytes:bee.downloadFile()returnsdataas a bee-jsBytesobject, not a rawArrayBuffer. Passing it directly tonew TextDecoder().decode()throwsERR_INVALID_ARG_TYPE. The.bytesproperty exposes the underlyingBufferwhichTextDecoderaccepts.Test plan
read.jsinto a project with a running Bee node, runnode init.js,node add-post.js alice ...,node add-post.js bob ...,node update-index.js, thennode read.js— should print index feed state, both authors, and homepage URL without errors🤖 Generated with Claude Code