Error: `spawn ENAMETOOLONG` when running `npm run deploy`

[phroureo]

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:

• GitHub repository (source code): https://github.com/phroureo/pf2e-tools
• GitHub Pages site (deployed app): https://phroureo.github.io/pf2e-tools/

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]

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.

[ThantHtetAung101]

This also happened with my project. I even made a python script to check the whole project if I got any files or folder which names are too long but I don't have any. Any clues?

[ismail-is]

what is error?

[ThantHtetAung101]

I've solved this by doing the workaround method. I still can't directly deploy. I first build my project using npm run build and I copied the whole dist or build folder into a seperate folder and link a fresh new github repo to it. I manually deploy the page by going to Project Repo -> Setting -> Pages. You can select a branch to deploy and wait a few minutes. The site will be up and running. If you made changes to your code, you will have to build or complie it again, copied the main js and css codes to build folder. Push the changes of the build folder to reflect changes.