Failure when attempting to make patch
See original GitHub issue$ npx patch-package serverless-webpack
patch-package 6.2.2
• Creating temporary folder
• Installing serverless-webpack@5.3.1 with npm
{
status: 243,
signal: null,
output: [ null, <Buffer >, <Buffer > ],
pid: 29938,
stdout: <Buffer >,
stderr: <Buffer >,
error: null
}
undefined
Same problem occurs no matter which package I attempt to make a patch for.
Ubuntu 18.04.3 LTS Node and NPM installed via
snap install --classic node --channel=14/stable
resulting in
$ snap list
Name Version Rev Tracking Publisher Notes
...redacted...
node 14.1.0 2687 14/stable nodesource✓ classic
...redacted...
Issue Analytics
- State:
- Created 3 years ago
- Reactions:5
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Troubleshooting failed patch installs and failed patch scans ...
If you cannot find a recent patch scan, go to Patch Management > Scan Machine, select the endpoint, and click “Run Now” to...
Read more >What are your options when a patch goes wrong? - N-able
Most of the time patches and updates run smoothly, but every now and again things can go badly wrong. Here's how to prepare...
Read more >How To: Troubleshoot a Failed Patch Install - Ivanti Community
If the patch is not located in the Patch Repository, the issue may be a failure attempting to download the patch. To test...
Read more >Fatal Error in Patch Installation - ManageEngine
If you get this error message while trying to install a Microsoft patch, then verify the %windows%\KB******.logs and upload the same. Upload the...
Read more >Chapter 29. Problems applying a patch - eCosCentric
First make sure that you used the right patch command line, as shown above. If that still did not work, try with a...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@landsman add the above patch to your
patches
folder with the file namepatch-package+6.2.2.patch
and you’ll be able to create patches for other packages and patch-package will auto patch itself on every new install.I have same problem.
Environment: