EPERM: operation not permitted, [NodeJs] [Electron]

Environments Windows
2

My Windows builds run into the same error occasionally, one example can be found in full here and its error log also below:

npm ERR! path C:\Users\travis\build\bkimminich\juice-shop\frontend\node_modules\.staging\typescript-685a7086\lib\typescriptServices.js
npm ERR! code EPERM
npm ERR! errno -4048
npm ERR! syscall unlink
npm ERR! Error: EPERM: operation not permitted, unlink 'C:\Users\travis\build\bkimminich\juice-shop\frontend\node_modules\.staging\typescript-685a7086\lib\typescriptServices.js'
npm ERR!  [OperationalError: EPERM: operation not permitted, unlink 'C:\Users\travis\build\bkimminich\juice-shop\frontend\node_modules\.staging\typescript-685a7086\lib\typescriptServices.js'] {
npm ERR!   cause: [Error: EPERM: operation not permitted, unlink 'C:\Users\travis\build\bkimminich\juice-shop\frontend\node_modules\.staging\typescript-685a7086\lib\typescriptServices.js'] {
npm ERR!     errno: -4048,
npm ERR!     code: 'EPERM',
npm ERR!     syscall: 'unlink',
npm ERR!     path: 'C:\\Users\\travis\\build\\bkimminich\\juice-shop\\frontend\\node_modules\\.staging\\typescript-685a7086\\lib\\typescriptServices.js'
npm ERR!   },
npm ERR!   stack: "Error: EPERM: operation not permitted, unlink 'C:\\Users\\travis\\build\\bkimminich\\juice-shop\\frontend\\node_modules\\.staging\\typescript-685a7086\\lib\\typescriptServices.js'",
npm ERR!   errno: -4048,
npm ERR!   code: 'EPERM',
npm ERR!   syscall: 'unlink',
npm ERR!   path: 'C:\\Users\\travis\\build\\bkimminich\\juice-shop\\frontend\\node_modules\\.staging\\typescript-685a7086\\lib\\typescriptServices.js',
npm ERR!   parent: '@angular-devkit/build-optimizer'
npm ERR! }
npm ERR! 
npm ERR! The operation was rejected by your operating system.
npm ERR! It's possible that the file was already in use (by a text editor or antivirus),
npm ERR! or that you lack permissions to access it.
npm ERR! 
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator (though this is not recommended).

With “occasionally” I mean "not always but so often that I set

matrix:
  fast_finish: true
  allow_failures:
    - os: windows

to avoid having to manually restart builds all the time"… :expressionless: