Jest: Cannot use NPM to install Jest

[shaunstone0]

🐛 Bug Report

When I am attempting to run npm install -D jest it shows this text in console:

npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN tar EINVAL: invalid argument, futime
npm WARN tar EINVAL: invalid argument, futime
npm WARN tar EINVAL: invalid argument, futime
npm WARN tar EINVAL: invalid argument, futime
npm WARN [email protected] No description
npm WARN [email protected] No repository field.

npm ERR! Maximum call stack size exceeded

npm ERR! A complete log of this run can be found in:
npm ERR!    view logs

To Reproduce

Attempt to install Jest as a dependency inside the Nodejs Environment.

Expected behavior

Should Install Dependency for me to use!

envinfo

System:
    OS: Windows 10 10.0.18363
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Memory: 7.70 GB / 15.82 GB
  Binaries:
    Node: 12.18.0 - C:\Program Files\nodejs\node.EXE
    npm: 6.14.4 - C:\Program Files\nodejs\npm.CMD
  Utilities:
    Git: 2.27.0. - C:\Program Files\Git\mingw64\bin\git.EXE
  IDEs:
    VSCode: 1.45.1 - C:\Users\shaun\AppData\Local\Programs\Microsoft VS Code\bin\code.CMD
  Languages:
    Bash: 4.4.23 - C:\Program Files\Git\usr\bin\bash.EXE
    Perl: 5.30.2 - C:\Program Files\Git\usr\bin\perl.EXE
  Browsers:
    Edge: 44.18362.449.0
    Internet Explorer: 11.0.18362.1
(I use Chrome)

I am also storing my files on an External Hard Drive

[ghostd]

Seems to be more an issue with your npm installation than jest. Did you try to remove your node_modules directory?

[shaunstone0]

Yes, I deleted the Cache also for NPM. Restarted my computer. It installs all of the dependencies but Jest. I updated NodeJs and NPM also.

EDIT: interestingly enough, it installs if I do the installation on my computer hard drive and not my external hard drive.
I wonder why that is...

[ghostd]

Different filesystem? Some symbolic links are missing?

[sauravhiremath]

Could you attach the logs npm is generating? Might aid in understanding the issue

[SEdilson]

I'm having the same issue but mine is hanging on installation.

[pouyajabbarisani]

Same problem

[MrrrLuiigii]

Same problem here. My project is also on an external SSD. These are the erros I'm getting:

npm WARN tar EINVAL: invalid argument, futime
npm WARN tar EINVAL: invalid argument, futime
npm WARN tar EINVAL: invalid argument, futime
npm WARN tar EINVAL: invalid argument, futime
npm WARN [email protected] requires a peer of babel-core@^6.25.0 || ^7.0.0-0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of canvas@^2.5.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of bufferutil@^4.0.1 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install peer dependencies yourself.

npm ERR! Maximum call stack size exceeded

[shaunstone0]

Different filesystem? Some symbolic links are missing?

Nope, formatted on windows. Using a windows machine. It's seriously just this packet. I will post logs when I get home from work.

[7Pass]

I also have this problem, npm v6.14.7, Windows.

[shaunstone0]

What fixed it for me was to move the entire project from my External Hard Drive to my SSD.

I do not have enough knowledge of the package to even guess why an External hard drive would cause this problem.

[SimenB]

This is a bug in npm, not with Jest's codebase. You should open up an issue with them

[Kermittt]

This issue appears to be directly related to a similar invalid argument, read issue that has appeared in multiple forums. I ran into this today and found the solution from those posts. This does appear to be an npm bug, but it only occurs when updating certain packages, and only when npm install is being executed on an external drive which is formatted as exFAT or FAT32. The solution that worked for me was to move everything off the drive, reformat as NTFS, and move everything back.

See this post on the npm community forums (and the many linked posts in the first response)
https://npm.community/t/issues-installing-npm-packages/9262

[Fuki26]

I have been facing the same issue, the resolution for me was... just placed the project into my SSD(not in commond hard drive as was before the fix).