Closed jwangyangls closed 2 years ago
@jwangyangls To be honest it doesn't seem like a good idea if installing package A would modify a different package B.
If your package depends on modifications of other packages, you can publish a modified version of that dependency yourself under a different package name
Because I am in a hurry to use it, I have already done so, thanks @v4dkou
This is a usage requirement for open source projects: My open source project is also used by many people, I expect to use patch-package in the open source project and package the patches file and specify its location, use my open source project in the third party project, but in the third party project When installing dependencies, "postinstall": "patch-package --patch-dir ./patches", my expectation is to modify some dependency files in the project root directory node_modules, and the result of execution at this time is 'it will be open sourced in me The node_module in the project package looks for files', according to the existing method, how can I configure it to achieve the expected, if I can't configure the existing method, can I add parameters, such as "--target-dir ../../../ node_modules"