We've been working on a SaaS product using Wasp, and everything was fine until last Friday. Since yesterday, our GitHub CI builds started to fail during project compilation. Can anyone help us resolve this?
Below is the error message. The failure is happening while running the "wasp test client run --silent" command:
[Client!] npm WARN deprecated abab@2.0.6: Use your platform's native atob() and btoa() methods instead
--- Starting compilation and setup phase. Hold tight... ------------------------
--- Compiling wasp project... --------------------------------------------------
...Installation going great - we'll get there soon!
...The installation is taking a while, but we'll get there!
[Server]> server@0.0.0 postinstall [Server]> patch-package [Server] [Server]patch-package 6.5.1 [Client!] npm WARN deprecated domexception@4.0.0: Use your platform's native DOMException instead [Server!] ERROR Failed to apply patch for package oauth at path [Server!] [Server!] node_modules/oauth [Server!] [Server!] This error was caused because oauth has changed since you [Server!] made the patch file for it. This introduced conflicts with your patch, [Server!] just like a merge conflict in Git when separate incompatible changes are [Server!] made to the same piece of code. [Server!] [Server!] Maybe this means your patch file is no longer necessary, in which case [Server!] hooray! Just delete it! [Server!] [Server!] Otherwise, you need to generate a new patch file. [Server!] [Server!] To generate a new one, just repeat the steps you made to generate the first [Server!] one. [Server!] i.e. manually make the appropriate file changes, then run [Server!] patch-package oauth [Server!] Info: [Server!] Patch file: patches/oauth+0.9.15.patch [Server!] Patch was made for version: 0.9.15 [Server!] Installed version: 0.10.0