Describe the known Node 24 native failure in the quickstart - #41
Merged
Merged
Conversation
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.
The Node quickstart currently describes errors as JavaScript rejections without identifying the intermittent Linux / Node 24.21.0 process crash. Add the observed scope and link to the runtime investigation, explaining that 0.1.3's worker shutdown fix has not established a resolution of the native failure.
Example code, downloads, versions, and package files are unchanged. Local checks confirm identical fenced code blocks and clean diff whitespace. The repository workflow will run the full documentation build, link checks, and installed-example verification.
Depends on fullbleed-engine/fullbleed-node#11 for the investigation page; merge after that PR.