en Copyright 2015 Java http://172.16.0.5:8080/history/expo/packages/expo-module-scripts/bin/npx#d295e37d [scripts] Fix npx script failing when yarn is not installed (#22582) List of files: /expo/packages/expo-module-scripts/bin/npx Wed, 24 May 2023 07:23:23 +0000 Tomasz Sapeta <tomasz.sapeta@swmansion.com> http://172.16.0.5:8080/history/expo/packages/expo-module-scripts/bin/npx#a41b516d [emc] Remove --silent for compat with yarn v3 List of files: /expo/packages/expo-module-scripts/bin/npx Tue, 22 Nov 2022 01:19:33 +0000 Brent Vatne <brentvatne@gmail.com> http://172.16.0.5:8080/history/expo/packages/expo-module-scripts/bin/npx#6d2045be [scripts] Run `npx` through `yarn exec` when run via npm instead of Yarn`npm publish` would fail because `npx` would install `tsc` from npm instead of using the copy installed in the workspace root's `node_modules/.bin` directory. In contrast, Yarn adds the workspace root's `.bin` directory and cwd's `.bin` directory to `$PATH` so we find our locally installed copy of `tsc`.To remedy this difference between Yarn and npm, we want to set up `$PATH` the same way Yarn does even when using npm. Yarn exposes a command called `yarn exec` that does this, so in `expo-module-scripts` we now use `yarn exec -- npx` instead of `npx` when we detect that we're run via npm instead of Yarn.Test plan: run `npm pack` in the expo package and verify it works. List of files: /expo/packages/expo-module-scripts/bin/npx Fri, 26 Oct 2018 19:27:18 +0000 James Ide <ide@expo.io>