question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error: ENAMETOOLONG: name too long, unlink

See original GitHub issue

For over a month today, i have being battling and trying to package my app with this amazing tool. However, all my effort failed. I have asked numerous question in SO , yet no solution among which is this http://stackoverflow.com/questions/37561851/electron-packaging-with-electron-packager.

After reading some blogs and suggestions. I moved my electron.js to my home folder . Now i am having the error below

image

I am running electron versions

 "electron-packager": "^7.0.3",
 "electron-prebuilt": "^1.2.1",

On my machine

image

Please i read somewhere some one was suggesting he solved his by building on his VM instead of the MAC machine. Does it really not work on MAC ? Previously, my build works for other platforms. However , it does not work for Darwin platform as you can noticed in my previous question on SO

http://stackoverflow.com/questions/37561851/electron-packaging-with-electron-packager . Someone suggested it was not building with my node_modules and i should move my electron.js to where my node_modules folder is available. Now i did moved it and i am getting the error above. Please how and what is wrong with my electron ? I have being trying this for over a month today. Any help would be appreciated.

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Comments:25 (11 by maintainers)

github_iconTop GitHub Comments

3reactions
maleptcommented, Jun 14, 2016

Clean out your output directories and try again. It seems you’re hitting a copy recursion loop.

1reaction
maleptcommented, Feb 21, 2017

FWIW I managed to figure out a non-hacky solution to this problem, and it is in the 8.5.2 release.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Unable to install latest SB version: Error: ENAMETOOLONG ...
Unable to install latest SB version: Error: ENAMETOOLONG: name too long, unlink... #18441. Answered by FikirYibeltal.
Read more >
Error: ENAMETOOLONG: name too long, stat 'cypress ...
And Cypress window is closed. There is Error in the console: Error: ENAMETOOLONG: name too long, stat 'cypress/integration/cypress/integration/ ...
Read more >
[SOLVED] ENAMETOOLONG: File name too long [rename]
Get this error: Cannot move file "/path/file.ffs_tmp" to "/path/filefullname.mkv". ENAMETOOLONG: File name too long [rename]. OS is Linux
Read more >
Pod install error ENAMETOOLONG: name too long
Solid newcomer here. Let me clarify: I am flabby, not solid, newly arriving to your wonderful Solid Project. I'm trying to follow the ......
Read more >
Upload Image Fail: [Error: ENAMETOOLONG: name too long
I'm afraid we don't support directly uploading svg files in this way, however, if you base64 encode the SVG, the upload should be...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found