You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
PS C:\Users\rober\WebstormProjects\angular\aio> yarn
yarn install v1.22.19
[1/5] Validating package.json...
[2/5] Resolving packages...
success Already up-to-date.
$ node tools/cli-patches/patch.js && patch-package --patch-dir ../tools/npm-patches/
'patch' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\rober\WebstormProjects\angular\aio\node_modules\shelljs\src\common.js:401
if (config.fatal) throw e;
^
Error: exec: 'patch' is not recognized as an internal or external command,
operable program or batch file.
at Object.error (C:\Users\rober\WebstormProjects\angular\aio\node_modules\shelljs\src\common.js:110:27)
at execSync (C:\Users\rober\WebstormProjects\angular\aio\node_modules\shelljs\src\exec.js:120:12)
at Object._exec (C:\Users\rober\WebstormProjects\angular\aio\node_modules\shelljs\src\exec.js:223:12)
at Object.exec (C:\Users\rober\WebstormProjects\angular\aio\node_modules\shelljs\src\common.js:335:23)
at C:\Users\rober\WebstormProjects\angular\aio\tools\cli-patches\patch.js:11:27
at Array.forEach (<anonymous>)
at Object.<anonymous> (C:\Users\rober\WebstormProjects\angular\aio\tools\cli-patches\patch.js:11:8)
at Module._compile (node:internal/modules/cjs/loader:1254:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1308:10)
at Module.load (node:internal/modules/cjs/loader:1117:32)
Node.js v18.16.0
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
PS C:\Users\rober\WebstormProjects\angular\aio> node tools/cli-patches/patch.js
'patch' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\rober\WebstormProjects\angular\aio\node_modules\shelljs\src\common.js:401
if (config.fatal) throw e;
^
Error: exec: 'patch' is not recognized as an internal or external command,
operable program or batch file.
at Object.error (C:\Users\rober\WebstormProjects\angular\aio\node_modules\shelljs\src\common.js:110:27)
at execSync (C:\Users\rober\WebstormProjects\angular\aio\node_modules\shelljs\src\exec.js:120:12)
at Object._exec (C:\Users\rober\WebstormProjects\angular\aio\node_modules\shelljs\src\exec.js:223:12)
at Object.exec (C:\Users\rober\WebstormProjects\angular\aio\node_modules\shelljs\src\common.js:335:23)
at C:\Users\rober\WebstormProjects\angular\aio\tools\cli-patches\patch.js:11:27
at Array.forEach (<anonymous>)
at Object.<anonymous> (C:\Users\rober\WebstormProjects\angular\aio\tools\cli-patches\patch.js:11:8)
at Module._compile (node:internal/modules/cjs/loader:1254:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1308:10)
at Module.load (node:internal/modules/cjs/loader:1117:32)
Node.js v18.16.0
Please provide the environment you discovered this bug in (run ng version)
workaround: run yarn from git bash
while it seems easy fix, the error happens when you run yarn test:ci and it's not obvious it's caused by failing yarn install or that running it from git bash will fix it
The text was updated successfully, but these errors were encountered:
Which @angular/* package(s) are the source of the bug?
Don't known / other
Is this a regression?
Yes
Description
this affects only windows contributors
in this file https://github.com/angular/angular/blob/main/aio/tools/cli-patches/patch.js#L11
the patch command isn't available in windows, and so it fails
steps to reproduce (in windows only)
git clean -dfx
aio
yarn
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
Please provide the environment you discovered this bug in (run
ng version
)Anything else?
workaround: run yarn from git bash
while it seems easy fix, the error happens when you run
yarn test:ci
and it's not obvious it's caused by failingyarn install
or that running it from git bash will fix itThe text was updated successfully, but these errors were encountered: