-
-
Notifications
You must be signed in to change notification settings - Fork 280
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't patch package- fails with status 1, no error #484
Comments
Same issue:
|
Same |
This happened to me when the registry listed in my package-lock.json didn't match the registry in my .npmrc. |
This has been happening to me as well all of a sudden Edit: Using npx patch-package instead of just patch-package fixed the issue. |
We are seeing occasional flakes in `patch-package`, possibly caused by ds300/patch-package#484. This wrapper script will retry patch-package three times before giving up. Longer-term we hope to upgrade to a package manager with built-in patch support.
We are seeing occasional flakes in `patch-package`, possibly caused by ds300/patch-package#484. This wrapper script will retry patch-package three times before giving up. Longer-term we hope to upgrade to a package manager with built-in patch support.
I still get the problem using Edit: when I added proper private registry configuration to my |
Hi I'm still getting the below error even though it was allegedly fixed in an earlier version:
C:\TMAX-R\trunk\lucid_client>npx patch-package @inovua/reactdatagrid-enterprise
npm WARN config global
--global
,--local
are deprecated. Use--location=global
instead.patch-package 8.0.0
• Creating temporary folder
• Installing @inovua/reactdatagrid-enterprise@5.9.2 with npm
{
status: 1,
signal: null,
output: [ null, null, null ],
pid: 24900,
stdout: null,
stderr: null,
error: null
}
C:\TMAX-R\trunk\lucid_client\node_modules\patch-package\dist\makePatch.js:395
throw e;
^
{
status: 1,
signal: null,
output: [ null, null, null ],
pid: 24900,
stdout: null,
stderr: null,
error: null
}
The text was updated successfully, but these errors were encountered: