rman 2.3.0 → 2.3.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/constants.js +1 -1
- package/package.json +1 -1
- package/utils/run-bin.js +8 -1
package/constants.js
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
export const version = '2.3.
|
|
1
|
+
export const version = '2.3.1';
|
package/package.json
CHANGED
package/utils/run-bin.js
CHANGED
|
@@ -49,9 +49,16 @@ export async function runBin(bin, argv, options = {}) {
|
|
|
49
49
|
* colour, and a pipe is not one - so routing eslint's output through the region would
|
|
50
50
|
* otherwise strip the colour it had when it inherited the terminal. Set only for that case:
|
|
51
51
|
* a caller that asked for `pipe` itself is usually capturing text to read, not to show. */
|
|
52
|
+
/* **It is added *onto* a base environment, never written as one.** `BinPath.env`'s `env` is the
|
|
53
|
+
* environment to derive from - it replaces `process.env` rather than extending it - so
|
|
54
|
+
* `{ FORCE_COLOR: '1' }` handed over alone left the child with that one variable plus a PATH
|
|
55
|
+
* holding only `node_modules/.bin`. Measured on `panates/sqb` at 2.3.0: `rman test` found npm
|
|
56
|
+
* (the walk ends at the running node's own directory) and npm then died with
|
|
57
|
+
* `spawn sh ENOENT`, because `/bin` was not on the PATH it was given. Every `runBin` call made
|
|
58
|
+
* while a status region is live had it, which since 2.3.0 is every one of them. */
|
|
52
59
|
env: BinPath.env({
|
|
53
60
|
cwd,
|
|
54
|
-
env: region && atLeast('info') ? { FORCE_COLOR: '1', ...options.env } : options.env,
|
|
61
|
+
env: region && atLeast('info') ? { FORCE_COLOR: '1', ...(options.env ?? process.env) } : options.env,
|
|
55
62
|
app: options.app,
|
|
56
63
|
}),
|
|
57
64
|
windowsHide: true,
|