This is the output from `elm.cmd install` as of elm 0.19 (0.19-bugfix6). The `package` command is no longer available, and `elm install :package-name` is only used when you are installing to the Elm module manifest, aka `elm.json`. See the note about how the command doesn't use the same approach as `npm install`.

elm-0-19-elm-install-attempt

> ..\node_modules\.bin\elm.cmd install

-- INSTALL WHAT? ---------------------------------------------------------------

I am expecting commands like:

    elm install elm/http
    elm install elm/json
    elm install elm/random

Hint: In JavaScript folks run `npm install` to start projects. "Gotta download
everything!" But why download packages again and again? Instead, Elm caches
packages in C:\Users\andrew.lenards\AppData\Roaming\elm so each one is
downloaded and built ONCE on your machine. Elm projects check that cache before
trying the internet. This reduces build times, reduces server costs, and makes
it easier to work offline. As a result elm install is only for adding
dependencies to elm.json, whereas elm make is in charge of gathering
dependencies and building everything. So maybe try elm make instead?

C:\workspace\bhive\src\Web\elm [feature/lenards/elm-upgrade-0-19 +2 ~1 -0 !]> ..\node_modules\.bin\elm.cmd install all
elm.exe: TODO show possible arg configurations
CallStack (from HasCallStack):
  error, called at ui/terminal/src\Terminal\Args\Error.hs:281:13 in main:Terminal.Args.Error