Skip to content
This repository has been archived by the owner on Sep 12, 2019. It is now read-only.

Error: EPERM: operation not permitted when using create_source_map: true #45

Open
Aqours opened this issue May 17, 2018 · 1 comment
Open

Comments

@Aqours
Copy link

Aqours commented May 17, 2018

Node: 10.0.0
System: Windows 10
webpack-closure-compiler: 2.1.6
google-closure-compiler: 20170521.0.0

Error log

D:\git\corp\fakename\node_modules\temp\node_modules\rimraf\rimraf.js:137
      throw er
      ^

Error: EPERM: operation not permitted, unlink 'C:\Users\fake\AppData\Local\Temp\ccwp-dump-118417-17908-1f8a0mj.xn1m'
    at Object.fs.unlinkSync (fs.js:1015:3)
    at rimrafSync (D:\git\corp\fakename\node_modules\temp\node_modules\rimraf\rimraf.js:211:13)
    at cleanupFilesSync (D:\git\corp\fakename\node_modules\temp\lib\temp.js:88:5)
    at process.cleanupSync (D:\git\corp\fakename\node_modules\temp\lib\temp.js:195:19)
    at process.emit (events.js:182:13)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! fakename@0.9.28 build: `npm run prefetch && npm run tslint && webpack --env.prod --display=errors-only`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the fakename@0.9.28 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\fake\AppData\Roaming\npm-cache\_logs\2018-05-17T10_42_02_279Z-debug.log

Process finished with exit code 1
@Aqours
Copy link
Author

Aqours commented May 18, 2018

It seems #37 (comment) can solve the problem. The issue had been closed by #39 PR which didn't fix the issue actually.

var temp = require('temp').track();

fs.unlinkSync(outputSourceMapFile.path);

=>

var temp = require('temp');
// ...
// fs.unlinkSync(outputSourceMapFile.path);

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant