EPERM: operation not permitted (rmdir) when using prune
See original GitHub issue- I have read the contribution documentation for this project.
- I agree to follow the code of conduct that this project follows, as appropriate.
- I have searched the issue tracker for an issue that matches the one I want to file, without success.
[Edited due to spelling error]
I am getting an EPERM error related to rmdir.
ERR! Error: EPERM: operation not permitted, rmdir c:\Users\Jon\Desktop\Test\distwin32a\mytest1-win32-x64\resources\app\node_modules
My command line is:
npm run build-win32
My script is:
"build-win32": "electron-packager . --electron-version 1.4.15 --tmpdir=false --platform win32 --icon ./assets/icon.ico --out ./distwin32a --overwrite"
My package.json is:
{
"name": "mytest1",
"version": "1.0.0",
"description": "MyTest2",
"main": "main.js",
"scripts": {
"start": "electron main.js",
"build-all": "electron-packager . --electron-version 1.4.15 --tmpdir=false --platform all --icon ./assets/icon --out ./dist",
"build-win32": "electron-packager . --electron-version 1.4.15 --tmpdir=false --platform win32 --icon ./assets/icon.ico --out ./distwin32a --overwrite",
"build-linux": "electron-packager . --electron-version 1.4.15 --tmpdir=false --platform linux --icon ./assets/background.png --out ./distlinux --overwrite",
"build-osx": "electron-packager . --electron-version 1.4.15 --tmpdir=false --platform darwin --icon ./assets/icon.icns --out ./distdarwin --overwrite"
},
"private": true,
"build": {
"appId": "mycompany.myproduct"
},
"keywords": [
"Stuff",
"Stuff"
],
"author": "JAA17",
"license": "SEE LICENSE IN LICENSE.TXT",
"devDependencies": {
"electron-packager": "^8.5.1"
}
}
The only thing I have in the background is Visual Studio where I do my code editing.
Issue Analytics
- State:
- Created 7 years ago
- Comments:23 (13 by maintainers)
Top Results From Across the Web
EPERM: operation not permitted (rmdir) when using prune -
[x] I have searched the issue tracker for an issue that matches the one I want to file, without success. [Edited due to...
Read more >npm - EPERM: operation not permitted on Windows
Today I got EPERM even in cmd.exe . But I ran the following command standing in C:\Program Files\nodejs , and it seems to...
Read more >Electron packager tutorial
In this electron packager tutorial we will look at how to create MacOS, Windows and Linux executables with an app icon.
Read more >Operation not permitted : can't delete any plugin - Bug reports
I have an internal SSD named K:/ that contains my Obsidian Vault. I can't succeed to delete any plugin and have an error...
Read more >Can't run n8n - Questions
When I type n8n it returns with: » Error: There was an error: EPERM: operation not permitted, scandir 'C:\Users\Administrator\Application ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
In order to debug your problem further, we need a minimal testcase to reproduce your problem. Using the
electron-quick-start
repository as a base, could you please create a minimal Electron app that illustrates the issue you described, and post a link to it here?Since the original issue reporter has not responded to the request for additional information about whether yarn works in over two months, I’m going to assume that they either found the answer in another manner or decided not to pursue this issue. If I’m incorrect, they can respond with answers to the questions posed, and I’ll reopen.