Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: spawn ENAMETOOLONG when running npm run deploy #211

Open
2 of 5 tasks
phroureo opened this issue Oct 27, 2024 · 1 comment
Open
2 of 5 tasks

Error: spawn ENAMETOOLONG when running npm run deploy #211

phroureo opened this issue Oct 27, 2024 · 1 comment
Assignees

Comments

@phroureo
Copy link

phroureo commented Oct 27, 2024

Category

Which of these applies to you? (Select all that apply)

  • I'm following the tutorial as-written from start to finish
  • I'm using a custom domain (note: not covered in tutorial)
  • I'm using React Router (note: not covered in tutorial)

Step

Which step of the tutorial do you want someone to help you with? (Select one)

  • Step number: 7
  • Something else

Links

Tell us where we can find your code and your GitHub Pages site:

Everything else

I'm getting this error when I try to run npm run deploy:

Error: spawn ENAMETOOLONG
    at ChildProcess.spawn (node:internal/child_process:420:11)
    at Object.spawn (node:child_process:757:9)
    at C:\Users\(folder)\source\repos\pf2e-tools\node_modules\gh-pages\lib\git.js:30:22
    at new Promise (<anonymous>)
    at spawn (C:\Users\(folder)\source\repos\pf2e-tools\node_modules\gh-pages\lib\git.js:29:10)
    at Git.exec (C:\Users\(folder)\source\repos\pf2e-tools\node_modules\gh-pages\lib\git.js:69:10)
    at Git.rm (C:\Users\(folder)\source\repos\pf2e-tools\node_modules\gh-pages\lib\git.js:146:15)
    at C:\Users\(folder)\source\repos\pf2e-tools\node_modules\gh-pages\lib\index.js:180:22
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

I tried shortening long files and long file names, but am still having issues with this step.

@gitname
Copy link
Owner

gitname commented Dec 1, 2024

Hi @phroureo, sorry about the delay in my response. I have not encountered this issue before. Are you still facing this issue?

If so, will you tell me how many characters are in the part of the path that you represented with (folder)? I don't need to know the actual string (in case it is private; e.g. it includes your real name).

Also, I see a 10 year-old issue in the npm repository involving that ENAMETOOLONG error code: npm/npm#6776 (comment). I think the person that created that Issue had a file on their computer that had a very long name and was created by mistake. Will you check for any particularly long-named files or folders in your working directory? Edit: Sorry, you said you already did this.

@gitname gitname self-assigned this Dec 2, 2024
@gitname gitname changed the title Error: spwn ENAMETOOLONG Error: spawn ENAMETOOLONG Dec 2, 2024
@gitname gitname changed the title Error: spawn ENAMETOOLONG Error: spawn ENAMETOOLONG when running npm run deploy Dec 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants