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

[BUG] error cb() never called! #547

Closed
CanPacis opened this issue Dec 3, 2019 · 0 comments
Closed

[BUG] error cb() never called! #547

CanPacis opened this issue Dec 3, 2019 · 0 comments

Comments

@CanPacis
Copy link

CanPacis commented Dec 3, 2019

What / Why

Neither 'npm install' nor 'npm install -g works'

When

  • Whenever I try to install an npm package to my machine

Where

  • npm cli itself

How

Current Behavior

  • I have recently bought a new machine and download the recommended version of nodejs and installed. Every command of npm but 'install' or its alieses works. As much as I could understand, npm creates a .staging folder for ongoing proccesses then fetches needed folders or files. But in my machine while trying to run this command, cli names folders, just the folders, incorrectly, namely not adding the first letter. Package's lib or bin files, for instance, is named ib and in.
    npm- staging

Steps to Reproduce

  • install recommended or latest version of nodejs and run npm install

Expected Behavior

  • it should install the package, obviously

Here is the log file:

0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli   'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli   'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   'install',
1 verbose cli   '-g',
1 verbose cli   'typescript'
1 verbose cli ]
2 info using npm@6.13.1
3 info using node@v13.2.0
4 verbose npm-session 41cd34c1ae2a1aae
5 silly install loadCurrentTree
6 silly install readGlobalPackageData
7 http fetch GET 304 https://registry.npmjs.org/typescript 351ms (from cache)
8 silly pacote tag manifest for typescript@latest fetched in 448ms
9 timing stage:loadCurrentTree Completed in 518ms
10 silly install loadIdealTree
11 silly install cloneCurrentTreeToIdealTree
12 timing stage:loadIdealTree:cloneCurrentTree Completed in 1ms
13 silly install loadShrinkwrap
14 timing stage:loadIdealTree:loadShrinkwrap Completed in 2ms
15 silly install loadAllDepsIntoIdealTree
16 silly resolveWithNewModule typescript@3.7.2 checking installable status
17 timing stage:loadIdealTree:loadAllDepsIntoIdealTree Completed in 6ms
18 timing stage:loadIdealTree Completed in 11ms
19 silly currentTree npm
20 silly idealTree npm
20 silly idealTree `-- typescript@3.7.2
21 silly install generateActionsToTake
22 timing stage:generateActionsToTake Completed in 6ms
23 silly diffTrees action count 1
24 silly diffTrees add typescript@3.7.2
25 silly decomposeActions action count 8
26 silly decomposeActions fetch typescript@3.7.2
27 silly decomposeActions extract typescript@3.7.2
28 silly decomposeActions preinstall typescript@3.7.2
29 silly decomposeActions build typescript@3.7.2
30 silly decomposeActions install typescript@3.7.2
31 silly decomposeActions postinstall typescript@3.7.2
32 silly decomposeActions finalize typescript@3.7.2
33 silly decomposeActions refresh-package-json typescript@3.7.2
34 silly install executeActions
35 silly doSerial global-install 8
36 verbose correctMkdir C:\Users\MUHAMMED ALİ\AppData\Roaming\npm-cache\_locks correctMkdir not in flight; initializing
37 verbose makeCacheDir UID & GID are irrelevant on win32
38 verbose lock using C:\Users\MUHAMMED ALİ\AppData\Roaming\npm-cache\_locks\staging-c0c42ac9b9cfe719.lock for C:\Users\MUHAMMED ALİ\AppData\Roaming\npm\node_modules\.staging
39 silly doParallel extract 1
40 silly extract typescript@3.7.2
41 silly tarball trying typescript@latest by hash: sha512-ml7V7JfiN2Xwvcer+XAf2csGO1bPBdRbFCkYBczNZggrBZ9c7G3riSUeJmqEU5uOtXNPMhE3n+R4FA/3YOAWOQ==
42 silly tarball no local data for typescript@latest. Extracting by manifest.
43 warn tar ENOENT: no such file or directory, open 'C:\Users\MUHAMMED ALİ\AppData\Roaming\npm\node_modules\.staging\typescript-21dd751b\bin\tsc'
44 warn tar ENOENT: no such file or directory, open 'C:\Users\MUHAMMED ALİ\AppData\Roaming\npm\node_modules\.staging\typescript-21dd751b\bin\tsserver'
45 warn tar ENOENT: no such file or directory, open 'C:\Users\MUHAMMED ALİ\AppData\Roaming\npm\node_modules\.staging\typescript-21dd751b\lib\cancellationToken.js'
46 warn tar ENOENT: no such file or directory, open 'C:\Users\MUHAMMED ALİ\AppData\Roaming\npm\node_modules\.staging\typescript-21dd751b\lib\cs\diagnosticMessages.generated.json'
47 timing npm Completed in 8323ms
48 error cb() never called!
49 error This is an error with npm itself. Please report this error at:
50 error <https://npm.community>
@CanPacis CanPacis closed this as completed Dec 4, 2019
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

1 participant