Skip to content

Docs/external blueprint install peer deps#279

Merged
frbrkoala merged 2 commits into
mainfrom
docs/external-blueprint-install-peer-deps
Jul 7, 2026
Merged

Docs/external blueprint install peer deps#279
frbrkoala merged 2 commits into
mainfrom
docs/external-blueprint-install-peer-deps

Conversation

@frbrkoala

@frbrkoala frbrkoala commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

What does this PR do?

🛑 Please open an issue first to discuss any significant work and flesh out details/direction — we would hate for your time to be wasted.
Consult the CONTRIBUTING guide for submitting pull-requests.

Motivation

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • New blueprint (adding a new protocol — see checklist below)
  • Documentation update
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Testing

  • I have run npm run build successfully
  • I have run npm run test and all tests pass
  • I have run npx cdk synth with a sample .env (e.g. from blueprints/dummy/samples/) and it succeeds
  • I have run pre-commit hooks: npm run run-pre-commit

New Blueprint Checklist (if adding a protocol)

  • Blueprint follows the structure of blueprints/dummy/ (reference implementation)
  • Blueprint README follows the standard template (matches Dummy section titles and ordering)
  • Setup section points to Getting Started (not inline instructions)
  • Deployment section leads with AI-driven deployment (Option 1) and manual as Option 2
  • Sample .env files are provided for at least one network (mainnet or testnet)
  • Configuration scripts follow the install/run dispatch pattern (see blueprints/dummy/)
  • Blueprint page added to website/docs/blueprints/ (.mdx mirror importing README)
  • Client Release Channels table added to README under Additional Resources

Documentation

  • I have updated relevant documentation (if applicable)
  • I have run cd website && npm run build with no broken links (if docs changed)

License

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

vlasonfa added 2 commits July 6, 2026 16:58
Installing an external blueprint (`npm install aws-bnr-blueprint-<protocol>`
or a github: URL) fails with npm E404 on npm 7+: the blueprint declares a peer
dependency on the `aws-blockchain-node-runners` framework, which is not
published to the npm registry, so strict peer resolution cannot satisfy it.

Add `--legacy-peer-deps` (with a short explanation of why) to every
external-blueprint install command across the docs: README, the community
blueprints page, the blueprint security-review workflow, and the add-protocol
workflow. Bare `npm install` (repo dependencies) is unaffected and left as-is.

Surfaced while validating the first community blueprint (TRON, issue #263).
Add the TRON blueprint (aws-bnr-blueprint-tron, java-tron client) as the first entry in the community blueprint catalog. Supports FullNode and Lite FullNode variants on x86_64 and ARM64/Graviton, mainnet and Nile testnet. Install command includes --legacy-peer-deps for consistency with external blueprint install guidance. Closes #263
@github-actions

github-actions Bot commented Jul 7, 2026

Copy link
Copy Markdown

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

@github-actions

github-actions Bot commented Jul 7, 2026

Copy link
Copy Markdown

Scan for commit: 6809d22 | Updated: 2026-07-07 03:34:45 UTC

🔒 Security Scan Results

Scanned files: 4

No security issues found.

@frbrkoala frbrkoala merged commit c610da8 into main Jul 7, 2026
7 checks passed
@frbrkoala frbrkoala deleted the docs/external-blueprint-install-peer-deps branch July 7, 2026 03:34
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.

2 participants