Scoop

Installs packages using Scoop. Scoop is a command-line package manager for Windows that focuses on developer tools and open-source software. It installs programs cleanly into your user directory without needing admin privileges.

YAML Key: scoop

Properties:

id: The package identifier (e.g., nodejs).

Basic Usage

Scoop installs packages from "buckets" (repositories of package definitions). You can search for packages at scoop.sh or by running:

scoop search <app-name>

To install a single package using WinHome:

scoop:
  - id: nodejs

To install multiple packages at once:

scoop:
  - id: nodejs
  - id: python
  - id: git

Advanced Configuration

Adding Buckets

Scoop organizes packages into buckets. The default bucket covers common tools, but many packages live in extra buckets like extras, games, or nerd-fonts. You can add buckets manually before running WinHome:

scoop bucket add extras
scoop bucket add nerd-fonts

Real-World config.yaml Examples

Example 1 — Developer Tools Setup

scoop:
  - id: git
  - id: nodejs
  - id: python
  - id: curl

Example 2 — Terminal & Shell Setup

scoop:
  - id: starship
  - id: neovim
  - id: windows-terminal
  - id: fzf

Example 3 — Fonts & UI Extras

scoop:
  - id: FiraCode-NF
  - id: JetBrainsMono-NF
  - id: Cascadia-Code

Note: Add the nerd-fonts bucket first: scoop bucket add nerd-fonts

Troubleshooting

Issue: scoop is not recognized as a command

Scoop is not pre-installed on Windows. Install it by running this in PowerShell:

  Set-ExecutionPolicy RemoteSigned -Scope CurrentUser
  irm get.scoop.sh | iex

Issue: Package not found

The package may be in a different bucket. Try adding the extras bucket:

  scoop bucket add extras

Then search again: scoop search <app-name>

Issue: Installation fails due to permissions

Scoop is designed to work without admin rights. If you face issues, make sure you are NOT running PowerShell as Administrator, as this can cause path conflicts.

Issue: Package installs but doesn't work correctly