vercel deployment

Is there a trick to using this with vercel like there is for heroku? I always see this in the vercel build log:

19:59:19.800 | Applying patches...
-- | --
19:59:19.803 | **ERROR** Failed to apply patch for package rich-markdown-editor at path
19:59:19.804 |  
19:59:19.804 | node_modules/rich-markdown-editor
19:59:19.804 | This error was caused because patch-package cannot apply the following patch file:
19:59:19.804 | patches/rich-markdown-editor+11.10.0.patch
19:59:19.804 | Try removing node_modules and trying again. If that doesn't work, maybe there was
19:59:19.804 | an accidental change made to the patch file? Try recreating it by manually
19:59:19.804 | editing the appropriate files and running:
19:59:19.804 |  
19:59:19.804 | patch-package rich-markdown-editor
19:59:19.804 |  
19:59:19.804 | If that doesn't work, then it's a bug in patch-package, so please submit a bug
19:59:19.804 | report. Thanks!
19:59:19.804 | https://github.com/ds300/patch-package/issues
19:59:19.804 |  
19:59:19.805 | ---
19:59:19.805 | patch-package finished with 1 error(s).

while locally it works great. thank you

[reck753]

Hi, I also got an issue with vercel deployment, but a little different scenario than this issue.

I have got a monorepo setup, with one of the packages being a Next application. The issue is that, this specific package, doesn’t pick up the patches from the root of the monorepo, nor does the postinstall script in the root package.json which does the package patching. If I would add the postinstall script to the specific package, I would get the error from patch-package that, the libraries I am trying to patch, are not present in the node_modules. This is true, the libraries are not present in the scoped node_modules of that package, because they get hoisted to the root node_modules of monorepo. I got a hacky solution, that I would rather not use, which involves nohoisting libraries that I am patching. This could lead to few issues, that is why I am not willing to use it.

Does anyone have some advice? Thanks in advance.

[suyoin]

Same issue is happening to me. It seems to be happening when multiple files’ diffs are in the same patch file.