IssueTracker

This might be related and might point to the root cause:

https://github.com/ds300/patch-package/issues/160

Hello there,
Ok, after reviewing the docs on the page for patch-package, specifically the section for Docker/CI, I've noticed that the third bullet point points out:
"If you cache node_modules rather than running yarn install every time, make sure that the patches dir is included in your cache key somehow. Otherwise if you update a patch then the change may not be reflected on subsequent CI runs."

I believe this would be applicable to App Engine, Cloud Functions, and Cloud Run. App Engine installs dependencies from yarn.lock files and Cloud Functions also accepts package-lock.json files as another alternative to yarn.lock, however I'm not certain if that applies to Cloud Run, or if App Engine accepts package-lock.json as an alternative when using Node.js.

Nevertheless, I believe this is expected/intended for patch-package, as after re-reading the contents of the Docker/CI section above, the second bullet point (prior to the third one I mentioned) states that you should copy the patch files created by the library before running npm install (it states that you should modify the Dockerfile).

I apologize if this response is a little late, if you'd like a little bit of help with the Dockerfile I can certainly help out as a best effort; and if you still think that this specific library should be something we somehow integrate within our existing systems, I'll forward your request to the appropriate team so that they can approve or deny the request. Do note that even if it is approved, there is no ETA for the implementation of said feature.

Kind regards

Hello again,
As there's been no response to this feature request (be it a commment or even having it be starred), and it is my understanding that this is intended (or at least expected) behavior by patch-package, I will be closing this under the status Won't fix (intended behavior). Should anyone find this to be an issue for them, please create a new issue and add this issue under "Blocked By" so that the issues are linked and there's a history for people reviewing the feature to follow.

Kind regards