Rush StackShopBlogEvents
Skip to main content

Peer dependencies

This hands-on demo uses the lockfile-explorer-demos environment. For setup instructions, read the Demos repository article.

Step 1: A peer dependency​

GitHub checkout branch: demo/peer-1

cd lockfile-explorer-demos

# WARNING: THIS COMMAND WILL DELETE ANY LOCAL CHANGES YOU MADE
git checkout -f -B demo/peer-1 remotes/origin/demo/peer-1
rush install

Step 2: An "unmet" peer dependency​

GitHub checkout branch: demo/peer-2

# WARNING: THIS COMMAND WILL DELETE ANY LOCAL CHANGES YOU MADE
git checkout -f -B demo/peer-2 remotes/origin/demo/peer-2
rush install

Step 3: Why do we need peers?​

GitHub checkout branch: demo/peer-3

# WARNING: THIS COMMAND WILL DELETE ANY LOCAL CHANGES YOU MADE
git checkout -f -B demo/peer-3 remotes/origin/demo/peer-3
rush install

Step 4: Catching missing peers​

GitHub checkout branch: demo/peer-4

# WARNING: THIS COMMAND WILL DELETE ANY LOCAL CHANGES YOU MADE
git checkout -f -B demo/peer-4 remotes/origin/demo/peer-4
rush install

Step 5: A missing peer is sometimes okay​

GitHub checkout branch: demo/peer-5

# WARNING: THIS COMMAND WILL DELETE ANY LOCAL CHANGES YOU MADE
git checkout -f -B demo/peer-5 remotes/origin/demo/peer-5
rush install