Our team was facing problem on making patch, in which the package is hosted in private registry. We have noticed that #152 has already handle such scenario, but we are still facing error with message similar as #300
After checking, we notice that since our .npmrc is symlink to somewhere else (as to facilitate switch registry), we use symlink which is copied into the tmp folder during make patch, and thus the symlink cannot resolve.
Our team was facing problem on making patch, in which the package is hosted in private registry. We have noticed that #152 has already handle such scenario, but we are still facing error with message similar as #300
After checking, we notice that since our
.npmrc
is symlink to somewhere else (as to facilitate switch registry), we use symlink which is copied into the tmp folder during make patch, and thus the symlink cannot resolve.This PR uses node fs
copySync
dereference
flag (https://github.com/jprichardson/node-fs-extra/blob/master/docs/copy-sync.md) to dereference the symlinkThanks