Un able to package electron app. ENOENT: no such file or directory,
See original GitHub issueI have tried more than 20 times to package the application built with an electron but failed. I do not want the issue is. I have seen many tutorials on YouTube and on the internet even then I could not package the app. When I run the command electron-packager . Please help me ho do I solve this issue? here is my packaje.json file:
`{ “name”: “myapp”, “version”: “1.0.0”, “description”: “”, “main”: “main.js”, “dependencies”: { “electron”: “^8.2.3” }, “devDependencies”: { “electron-packager”: “^14.2.1” }, “scripts”: { “start”: “electron .” }, “author”: “”, “license”: “ISC” }
here is a screenshot of an issue:
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Electron Forge: Error: ENOENT: no such file or directory
im currently trying to build my Electron Application.
Read more >macOS build breaks - ENOENT: no such file or directory - help
Problem is solved. Had to reset the head to the last commit before the electron package updates, then do a npm i and...
Read more >A Comprehensive Guide to Building and Packaging an ...
Building and Packaging an Electron App wasn't as straight forward as I had hoped. This guide aims to help you navigate the complexities...
Read more >How to fix: npm ERR! enoent ENOENT: no such file or ...
I recently struggled for a while with an npm error thrown when executing npm install of some package. The error message was npm...
Read more >electron-packager - npm
Customize and package your Electron app with OS-specific bundles (.app, .exe, etc.) via JS or CLI. Latest version: 17.1.1, last published: 2 ...
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 FreeTop 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
Top GitHub Comments
I had the same error message today, so i made this repo to try to reproduce the issue https://github.com/hugoruscitti/electron-packager-issue-1143
When i clone the repo and run the command “npm install” and then “npm run package” i get this error message:
Then, i try different (random/crazy) things and i notice that the problems seems to be related to my “package-lock.json” file, that i made some time ago in osx.
This screenshot shows how things stats to work again if i remove the “node_package” folder and the “package-lock.json”:
Since the original issue reporter has not responded to the request for additional information in about a week, it’s assumed that they either found the answer in another manner or decided not to pursue this issue. If this is incorrect, they can respond with answers to the questions posed, and this issue can be reopened.