Skip to content

docs: use published SDK peers for local setup - #4

Open
EgorMajj wants to merge 2 commits into
mainfrom
codex/published-package-docs
Open

EgorMajj wants to merge 2 commits into
mainfrom
codex/published-package-docs

Conversation

@EgorMajj

@EgorMajj EgorMajj commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Use published SDK peers in contributor and example setup instructions; sibling repositories are optional.
  • Explain the existing lockfile and peer-install settings without claiming the packages are unpublished.
  • Keep manifests, lockfiles, runtime APIs and workflow behavior unchanged.
    +- Missing-peer error guidance uses the same published-package install command; absent, 1.x and wrong-major fixture cases pass.

Validation

  • Fresh standalone install using published npm packages, type checks and package build.
  • Packed example build for this framework.
  • Additional compatibility checks: React 18, Vue 3.3 and Angular 17/22 in their respective repositories.
  • No live identification, credential changes, publication or deployment.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant