@builder.io/dev-tools 1.28.16-dev.202602271627.4aedad8b4 → 1.28.17-dev.202603022004.da8b71164

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.
Files changed (11) hide show
  1. package/cli/index.cjs +63 -22
  2. package/cli/index.cjs.map +3 -3
  3. package/core/index.cjs +1 -1
  4. package/core/index.mjs +1 -1
  5. package/node/index.cjs +1 -1
  6. package/node/index.mjs +1 -1
  7. package/package.json +1 -1
  8. package/server/index.cjs +2 -2
  9. package/server/index.mjs +2 -2
  10. package/types/cli/utils/resolve-shell-env.d.ts +5 -4
  11. package/types/tsconfig.tsbuildinfo +1 -1
package/types/cli/utils/resolve-shell-env.d.ts CHANGED
@@ -6,10 +6,11 @@
6
6
  * files (e.g. .zshrc, .bash_profile) are never sourced, so tools added to PATH
7
7
  * by those files are invisible.
8
8
  *
9
- * This function spawns `$SHELL -i -l -c "echo <marker>$PATH<marker>"` to
10
- * capture the fully-resolved PATH from the user's interactive shell. It uses
11
- * unique markers to reliably extract the PATH even when the shell prints
12
- * banners, motd messages, or other noise.
9
+ * This function spawns `$SHELL -i -l -c "printf <marker>; printenv PATH; printf <marker>"`
10
+ * to capture the fully-resolved PATH from the user's interactive shell. It uses
11
+ * `printenv` instead of `$PATH` to avoid issues with shells like fish where
12
+ * `$PATH` is a list variable. Unique markers reliably extract the PATH even
13
+ * when the shell prints banners, motd messages, or other noise.
13
14
  *
14
15
  * Returns `null` on Windows, in cloud environments, or on any failure.
15
16
  */