ivanseidel / ivanseidel/IAMDinosaur
508 verbose stack ZlibError: zlib: unexpected end of file
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2.8k
- Forks
- 532
- PR merge metrics
- No merged PRs in 30d
Description
This error occurred while using `npm install` .
Ocorreu esse erro ao usar o `npm install` .
- 508 verbose stack ZlibError: zlib: unexpected end of file
508 verbose stack at Zlib.(anonymous function).onerror (C:\Program Files (x86)\nodejs\node_modules\npm\node_modules\minizlib\index.js:131:21)
508 verbose stack at Unzip.write (C:\Program Files (x86)\nodejs\node_modules\npm\node_modules\minizlib\index.js:255:31)
508 verbose stack at Unzip.flush (C:\Program Files (x86)\nodejs\node_modules\npm\node_modules\minizlib\index.js:222:10)
508 verbose stack at Unzip.end (C:\Program Files (x86)\nodejs\node_modules\npm\node_modules\minizlib\index.js:229:10)
508 verbose stack at Object.end (C:\Program Files (x86)\nodejs\node_modules\npm\node_modules\tar\lib\parse.js:415:21)
508 verbose stack at PassThrough.onend (_stream_readable.js:595:10)
508 verbose stack at Object.onceWrapper (events.js:313:30)
508 verbose stack at emitNone (events.js:111:20)
508 verbose stack at PassThrough.emit (events.js:208:7)
508 verbose stack at endReadableNT (_stream_readable.js:1064:12)
508 verbose stack at _combinedTickCallback (internal/process/next_tick.js:139:11)
508 verbose stack at process._tickCallback (internal/process/next_tick.js:181:9)
509 verbose cwd D:\ALEXANDRO\Google Drive ( PESSOAL - alexandrogonsan )\BANCO DE DADOS EM USO\IAMDinosaur
510 verbose Windows_NT 6.3.9600
511 verbose argv "C:\\Program Files (x86)\\nodejs\\node.exe" "C:\\Program Files (x86)\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install"
512 verbose node v8.12.0
513 verbose npm v6.4.1
514 error code Z_BUF_ERROR
515 error errno -5
516 error zlib: unexpected end of file
517 verbose exit [ -5, true ]
You can help me sort this out.
Pode me ajudar a resolver isso .
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing npm install in the repository with Node v8.12.0 and npm 6.4.1, then inspect the dependency archive or cache implicated by minizlib and tar. Compare the result after a clean install or refreshed dependency metadata; done means npm install completes and the project dependencies are usable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100