-
- Notifications
You must be signed in to change notification settings - Fork 313
Closed
Description
Hi! 👋
Firstly, thanks for your work on this project! 🙂
Today I used patch-package to patch patch-package@6.4.7 for the project I'm working on.
Closes #288
Here is the diff that solved my problem:
diff --git a/node_modules/patch-package/dist/getPackageResolution.js b/node_modules/patch-package/dist/getPackageResolution.js index bc7ffaa..287a2f1 100644 --- a/node_modules/patch-package/dist/getPackageResolution.js +++ b/node_modules/patch-package/dist/getPackageResolution.js @@ -65,7 +65,7 @@ function getPackageResolution({ packageDetails, packageManager, appPath, }) { lockFileStack.reverse(); const relevantStackEntry = lockFileStack.find((entry) => entry.dependencies && packageDetails.name in entry.dependencies); const pkg = relevantStackEntry.dependencies[packageDetails.name]; - return pkg.resolved || pkg.from || pkg.version; + return pkg.resolved || pkg.version || pkg.from; } } exports.getPackageResolution = getPackageResolution;This issue body was partially generated by patch-package.
macku, gabjauf, devattendant, lfalcao, jabiinfante and 6 moreevanjmg
Metadata
Metadata
Assignees
Labels
No labels