a request for npm run to traverse directory tree

PR-URL: #73
Credit: @agorovyi
Close: #73
Reviewed-by: @isaacs

EDIT(@isaacs): Added implementation details and clarified some of the
context.

accepted/0024-npm-run-traverse-directory-tree.md

@@ -0,0 +1,139 @@
+# Let `npm run` traverse monorepo directory tree up to the root before failing
+
+## Summary
+
+Allow `npm run` command to traverse the directory tree up to the root level
+if it can't find a required `/node_modules/.bin` with executable command in
+subdirectory where it was executed from.
+
+## Motivation
+
+In the context of a multi-package monorepo where all dependencies are
+installed in the root `node_modules` it would've been very useful and
+convenient to have an ability to execute scripts from subdirectories that
+are packages within this monorepo without writing a full path to the root's
+`/node_modules/.bin` executable or adding a `prefix` to each run. Currently
+if you attempt to run a script from a subdirectory it will fail with
+`command not found` if there is no `/node_modules/.bin/` executable in the
+same subdirectory.
+
+## Detailed Explanation
+
+The expected change to `npm run` is to let it traverse the directory tree
+up to the root in search of an executable that may be stored in the root
+`/node_modules/.bin/`. If such executable doesn't exist anywhere in the
+directory tree then fail.
+
+In `npm-lifecycle`, used by npm v6 and before, the `node_modules/.bin`
+folders are added to the `PATH` environment variable _only_ when contained
+within a nested `node_modules` structure.  However, a package at
+`./packages/foo` would _not_ have `./node_modules/.bin` added to its script
+`PATH` environ.
+
+### Example:
+
+#### Folder structure:
+
+```
+monorepo-root
+├─ node_modules
+│  └─ .bin
+│     ├─ react-docgen
+│     ├─ rimraf
+│     ├─ run-s
+│     └─ webpack
+├─ packages
+│  ├─ foo
+│  │  ├─ src
+│  │  └─ package.json
+│  ├─ bar
+│  │  ├─ src
+│  │  └─ package.json
+│  └─ baz
+│     ├─ src
+│     └─ package.json
+├─ package.json
+└─ package-lock.json
+```
+
+#### scripts example for package `bar`
+
+```json
+bar - package.json
+{
+  "name": "@monorepo/bar",
+  "scripts": {
+    "build": "run-s clean prod comments",
+    "prod": "BABEL_ENV=production webpack --mode production",
+    "webpack:dev": "BABEL_ENV=development webpack --mode development",
+    "build:dev": "run-s clean webpack:dev comments",
+    "clean": "rimraf dist",
+    "comments": "react-docgen ./src/components/ --exclude index.js --include Examples"
+  }
+}
+```
+
+With the above structure `npm run build` from bar directory will fail in
+npm v6 with `sh: run-s: command not found` as it can't find
+`node_modules/.bin/run-s` in that directory.
+
+In npm v7, the PATH will include the root's `node_modules/.bin` folder, and
+so will run the command successfully.
+
+## Rationale and Alternatives
+
+The rationale for this feature is coming purely from a Developer Experience
+where you may have different teams working on different packages within one
+monorepo. In this case it is convenient for one team to work within one
+package folder and being able to run various scripts from that location
+without workarounds.
+
+There are 3 alternative solutions that somewhat resolve this problem:
+
+### Solution #1
+
+Write full paths in `scripts` to point to appropriate executables. The
+disadvantage of this approach is that each `package.json` file may be
+polluted and it will be hard to maintain it going forward:
+
+```json
+{
+  "name": "@monorepo/bar",
+  "scripts": {
+    "build": "../../node_modules/.bin/run-s clean prod comments",
+    "prod": "BABEL_ENV=production ../../node_modules/.bin/webpack --mode production",
+    "webpack:dev": "BABEL_ENV=development ../../node_modules/.bin/webpack --mode development",
+    "build:dev": "../../node_modules/.bin/run-s clean webpack:dev comments",
+    "clean": "../../node_modules/.bin/rimraf dist",
+    "comments": "../../node_modules/.bin/react-docgen ./src/components/ --exclude index.js --include Examples"
+  }
+}
+```
+
+### Solution #2
+
+Use `--prefix ../..` each time when you run a script, e.g. `npm run
+--prefix ../.. build`.
+
+This approach is a little bit cleaner than Solution #1 but still requires
+everyone to remember to prefix an executable. Working in large teams this
+`prefix` approach may be solved by documenting it but there is still a risk
+that people may forget to add `prefix`.
+
+### Solution #3
+
+Since this is a monorepo that may be managed with `lerna`, there is a way
+to execute these scripts from root by running `lerna run build` that will
+execute all build scripts in all packages or `lerna run build --scope bar`
+to execute it only in the `bar` package.
+
+The disadvantage of this approach is that you need to constantly `cd`
+between root and your working directory and also scoping your script to a
+package that you work on.
+
+## Implementation
+
+The `@npmcli/run-script` module builds up the `PATH` environment variable
+including the `node_modules/.bin` included in _every_ parent directory,
+rather than merely adding the `.bin` folder included in every
+`node_modules` folder in the script working directory.