You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
letfrom='file.txt'letto='/tmp/'fs.copySync(from,to);// errorfs.copySync(config,cache,()=>{console.log('done')});// no error, no filefs.copy(from,to);// ok
The problem is that I cannot copy a file to directory (file to file is ok).
@qa:npm-cache coping config /Users/a.abashkin/workspace/mail.ru/@qa/npm-cache/test.txt => /var/folders/0y/jg1cdcj50zv2vjsjzxtsfhqc0000gp/T/b68872c30295c440b0dc28c224bb9c3e +3ms
fs.js:988
return binding.unlink(pathModule._makeLong(path));
^
Error: EPERM: operation not permitted, unlink '/var/folders/0y/jg1cdcj50zv2vjsjzxtsfhqc0000gp/T/b68872c30295c440b0dc28c224bb9c3e'
at Object.fs.unlinkSync (fs.js:988:18)
at copyFileSync (/Users/a.abashkin/workspace/mail.ru/@qa/npm-cache/node_modules/fs-extra/lib/copy-sync/copy-file-sync.js:12:10)
at Object.copySync (/Users/a.abashkin/workspace/mail.ru/@qa/npm-cache/node_modules/fs-extra/lib/copy-sync/copy-sync.js:40:7)
at Cache.copyConfig (/Users/a.abashkin/workspace/mail.ru/@qa/npm-cache/index.js:257:6)
at Cache.installModules (/Users/a.abashkin/workspace/mail.ru/@qa/npm-cache/index.js:212:8)
at Cache.setCache (/Users/a.abashkin/workspace/mail.ru/@qa/npm-cache/index.js:345:8)
at request.response (/Users/a.abashkin/workspace/mail.ru/@qa/npm-cache/index.js:327:19)
at Request.request.on.response (/Users/a.abashkin/workspace/mail.ru/@qa/npm-cache/utils/request.js:47:4)
at emitOne (events.js:96:13)
at Request.emit (events.js:188:7)
supporting information:
npm -v prints: 3.10.8
node -v prints: v7.0.0
npm config get registry prints:
Windows, OS X/macOS, or Linux?: Darwin
The text was updated successfully, but these errors were encountered:
from
to
The problem is that I cannot copy a file to directory (file to file is ok).
supporting information:
npm -v
prints: 3.10.8node -v
prints: v7.0.0npm config get registry
prints:The text was updated successfully, but these errors were encountered: