Repository navigation
Correct published package installation instructions - #2
Merged
Merged
Conversation
dKosarevsky
marked this pull request as ready for review
October 9, 2026 00:01
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
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.
Why
The usage guide still said StreamSplit was not published, contradicting the README and the existing npm 0.1.0 release. npm's current 0.1.0 README also retains its pre-publication text; that registry copy needs a separately approved future release.
Changes
npm install --save-dev @agent-axiom/streamsplitcommand in both guides.example:*scripts are not included in the npm archive.Verification
npm run checkpassed locally: 53 tests, TypeScript checks, packed ESM/TypeScript consumers, zero runtime dependencies.npm run demoandgit diff --checkpassed. Exact-commit CI will check Node 20/22/24 and eventsource-parser 4.1.1.No API, package version, publishing access, or release changes. This PR has not been merged or published.