Initial execution of shadow-cljs compile requires an id

[k2n]

I got the following error for the first time I ran shadow-cljs compile. It worked if I specified the target shadow-cljs compile check-all, and the subsequent executions don't require it.

ip-192-168-1-58 ~/ghq/github.com/iku000888/shadow-cljs-kitchen-async-puppeteer(master|✔)
👉 shadow-cljs compile
shadow-cljs - config: /Users/kenji/ghq/github.com/iku000888/shadow-cljs-kitchen-async-puppeteer/shadow-cljs.edn  cli version: 2.8.26  node: v11.6.0
shadow-cljs - starting via "clojure"

Action "compile" requires one or more build ids

Usage:
  shadow-cljs <action> <zero or more build ids>

Supported actions are:

     compile - ...
       watch - ...
       check - ...
     release - ...
   node-repl - ...
browser-repl - ...
   cljs-repl - ...
    clj-repl - ...
    clj-eval - ...
     clj-run - ...
         run - ...
        info - ...
         pom - ...
    npm-deps - ...
        test - ...
         aot - ...
        init - ...
        help - ...
      server - ...
       start - ...
        stop - ...
     restart - ...

Options:
-----
      --npm                internal, used by the shadow-cljs npm package
  -d, --dependency DEP     adds an additional dependency (eg. -d foo/bar:1.2.3 -d another/thing:4.0.0)
      --config-merge DATA  merges additional EDN data into the build config
  -A, --aliases ALIASES    adds aliases for use with clj, only effective when using deps.edn
      --source-maps        temporarily enable source-maps for release debugging
      --pseudo-names       temporarily enable pseudo-names for release debugging. DO NOT SHIP THIS CODE!
      --debug              enable source-maps + pseudo-names. DO NOT SHIP THIS CODE!
      --stdin              clj-eval from stdin
  -v, --verbose            verbose build log
      --force-spawn        spawn new process, do not connect to running server
      --cli-info           prints a bunch of information
      --via VIA            internal option, used by node script
  -h, --help
-----