3 homepage: https://webinstall.dev
5 Webi is how developers install their tools.
14 Since `webi` is just a small helper script, it's always update on each use.
18 > `webi` is what you would have created if you automated how you install your
19 > common tools yourself: Simple, direct downloads from official sources,
20 > unpacked into `~/.local`, added to `PATH`, symlinked for easy version
21 > switching, with minimal niceties like resuming downloads and 'stable' tags.
24 - No magic, no nonesense, no bulk.
25 - What you would have done for yourself.
27 You can install _exactly_ what you need, from memory, via URL:
30 curl https://webinstall.dev/node@lts | bash
33 Or via `webi`, the tiny `curl | bash` shortcut command that comes with each
37 webi node@lts golang@stable flutter@beta rustlang
42 You can see exactly what PATHs have been edited:
51 cat ~/.config/envman/PATH.env
54 ### How to uninstall Webi
56 These are the files that are installed when you use [webinstall.dev](/):
62 ~/.local/opt/pathman-*
66 ~/.local/bin/webi-pwsh.ps1
67 ~/.local/bin/pathman.exe
68 ~/.local/opt/pathman-*
71 Assuming that you don't use `pathman` for anything else, you can safely remove
72 all of them. If you use [webinstall.dev](/) again in the future they will be
75 Additionally, these files may be modified to update your `PATH`:
80 ~/.config/fish/config.fish
81 ~/.config/envman/PATH.env
84 It's probably best to leave them alone.
86 ### How to uninstall Webi-installed programs
88 Except where noted otherwise (such as `wsl`) Webi installs everything into
89 `~/.local/bin` and `~/.local/opt`.
91 Some programs also use `~/.local/share` or `~/.config` - such as `postgres` and
92 `fish` - and some use program-specific directories - such as Go, which uses
95 If you want to remove any of them, simply deleting them should do well enough -
96 just check the Cheat Sheet for any special notes.
98 Here are some examples:
102 rm -rf ~/.local/bin/jq
103 rm -rf ~/.local/jq-*/
106 rm -rf ~/.local/opt/node/
107 rm -rf ~/.local/opt/node-*/