Alec Larson

Try using `git pull --rebase` if a cloned repo has no uncommitted changes.

Add heuristics for automatic rebuilds/reinstalls

1

Inside `/.indo-cache`, track when local packages were last built. Build any package missing a timestamp. Also, check the "mtime" of the package's lockfile to know if a package should be...

Two changes are needed to allow a package to build while another installs its node_modules. - Start building a package once (1) its node_modules are installed, (2) its local dependencies...

If a folder contains its own `.indo.json`, it's called a "nested root". The following commands are ignoring them: - `indo exec` - `indo ls` Probably others...?

If no path is given, ask for the user to choose between `/vendor/` and `/packages/`.

Add pipe support to "indo exec"

1

```sh indo exec -- 'cat package.json | jq .version' ```

Stop "indo" command from creating .indo.json when one does not exist

1

The `indo` command is useful even in repos that have no reason to keep a `.indo.json` file in version control. For example, after an npm client runs an `install` command,...

Add "indo pull" to update forks

2

The `indo pull` command would run `git pull` in every fork. Once finished, each fork with changes has its `build` script executed. Nested indo roots should be supported.

Now that #12 is added, we should update the `package.json` of every package that depends on the package being renamed.