@i_am_daniele or everyone!
I have tried many times to install Autohook on my CentOS 7, I copied paste the log below:
what should I do?, I need to investigate the webhook issues that we are currently facing with.
0 info it worked if it ends with ok
1 verbose cli [ ‘/usr/bin/node’, ‘/usr/bin/npm’, ‘i’, ‘-g’, ‘twitter-autohook’ ]
2 info using npm@6.14.12
3 info using node@v10.24.1
4 verbose npm-session 994a4b8cbef3f095
5 silly install loadCurrentTree
6 silly install readGlobalPackageData
7 http fetch GET 304 https://registry.npmjs.org/twitter-autohook 966ms (from cache)
8 silly pacote tag manifest for twitter-autohook@latest fetched in 976ms
9 timing stage:loadCurrentTree Completed in 994ms
10 silly install loadIdealTree
11 silly install cloneCurrentTreeToIdealTree
12 timing stage:loadIdealTree:cloneCurrentTree Completed in 0ms
13 silly install loadShrinkwrap
14 timing stage:loadIdealTree:loadShrinkwrap Completed in 2ms
15 silly install loadAllDepsIntoIdealTree
16 silly resolveWithNewModule twitter-autohook@1.7.2 checking installable status
17 http fetch GET 200 https://registry.npmjs.org/dotenv 53ms (from cache)
18 silly pacote range manifest for dotenv@^8.0.0 fetched in 63ms
19 silly resolveWithNewModule dotenv@8.6.0 checking installable status
20 http fetch GET 304 https://registry.npmjs.org/commander 71ms (from cache)
21 silly pacote range manifest for commander@^2.20.0 fetched in 75ms
22 silly resolveWithNewModule commander@2.20.3 checking installable status
23 http fetch GET 304 https://registry.npmjs.org/needle 110ms (from cache)
24 silly pacote range manifest for needle@^2.3.3 fetched in 113ms
25 silly resolveWithNewModule needle@2.9.1 checking installable status
26 http fetch GET 304 https://registry.npmjs.org/ngrok 935ms (from cache)
27 silly pacote range manifest for ngrok@^3.2.1 fetched in 939ms
28 silly resolveWithNewModule ngrok@3.4.1 checking installable status
29 http fetch GET 304 https://registry.npmjs.org/nock 979ms (from cache)
30 silly pacote range manifest for nock@^12.0.2 fetched in 997ms
31 silly resolveWithNewModule nock@12.0.3 checking installable status
32 http fetch GET 200 https://registry.npmjs.org/debug 9ms (from cache)
33 silly pacote range manifest for debug@^3.2.6 fetched in 15ms
34 silly resolveWithNewModule debug@3.2.7 checking installable status
35 http fetch GET 304 https://registry.npmjs.org/iconv-lite 33ms (from cache)
36 silly pacote range manifest for iconv-lite@^0.4.4 fetched in 35ms
37 silly resolveWithNewModule iconv-lite@0.4.24 checking installable status
38 http fetch GET 304 https://registry.npmjs.org/sax 43ms (from cache)
39 silly pacote range manifest for sax@^1.2.4 fetched in 45ms
40 silly resolveWithNewModule sax@1.2.4 checking installable status
41 http fetch GET 304 https://registry.npmjs.org/ms 37ms (from cache)
42 silly pacote range manifest for ms@^2.1.1 fetched in 38ms
43 silly resolveWithNewModule ms@2.1.3 checking installable status
44 http fetch GET 304 https://registry.npmjs.org/safer-buffer 44ms (from cache)
45 silly pacote range manifest for safer-buffer@>= 2.1.2 < 3 fetched in 45ms
46 silly resolveWithNewModule safer-buffer@2.1.2 checking installable status
Did you have any success using GitHub - twitterdev/account-activity-dashboard: Sample web app and helper scripts to get started with the premium Account Activity API ?
The log you have doesn’t have an obvious error, so it’s hard to say why it’s not installed properly. Maybe the issue is with the npm environment?
1 Like
system
Closed
#4
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
