Document version dependet patches
- Dominant language
- TypeScript
- Stars
- 11.2k
- Forks
- 325
- PR merge metrics
- No merged PRs in 30d
Description
i'm not even sure if it's supported, but there seem to be some infrastructure in place to detect versions conflicts.
Anyways, if I provide two patches for the same package but with different version suffixes, `patch-package` fails to apply the correct version.
Interestingly detects the mismatch but doesn't bother to check the correct file first.
The use case is as follows: I have a Hugo template which is reused across different projects, some have a locked dependency to a specific package, version X.0.0 (which isn't the latest) and some don't. The latest version of this package (lets say X.1.1) has some changes that are part of the patch for X.0.0. So a patch for X.1.1 would only be a subset of the patch for X.0.0. Needlessly to say that the included fixes had been implemented in a way that break the patch but provide the required functionality...
So I need `patch-package` to apply different patches to a package depending of the version of this package. How can I archive this?
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.