Error 'Must use npm@>=5' while using npm 5.4.2 about patch-package HOT 2 CLOSED

Thanks for the report!

npm prepare -- react-navigation should be npm run prepare -- react-navigation

That's my bad, the README is wrong. I'll update it now.

As for the first issue, that's a new one. The error message is a little misleading. It implies that you might be using an old npm but really it just means that it can't find any lock files. Do you definitely have one? i.e. a package-lock.json, npm-shrinkwrap.json, or yarn.lock? If so, then perhaps you could do me a favour:

1. edit node_modules/patch-package/dist/detectPackageManager.js and put the following line at the top of the detectPackageManager function:

   console.log("app root path:", appRootPath)
   

2. Then re-run patch-package and let me know whether the value that is logged is different from the root folder of your project (where the package.json is)?

from patch-package.

Got it working. What happened is that I was on npm 4.3.0 when I tried to use the package. I updated to npm >= 5 and did not touch any packages since then. It turns out that the lock file is not generated until you at least once touch the node_modules or package.json

In their words:

package-lock.json is automatically generated for any operations where npm modifies either the node_modules tree, or package.json.

After removing and reinstalling a package it could run and created a patch file :)

from patch-package.