JustalK / PORNHUB-API

A powerful and complete scrapper for the very famous pornhub.com. This javascript module for node give you the possibility, through an API with many options, to scrap any information out of a page or the search page.
MIT License
130 stars 29 forks source link

[BUG] Installation took over 12 hours and error #41

Closed beesuns closed 3 years ago

beesuns commented 3 years ago

Describe the bug Kali Linux: Linux kali 5.9.0-kali4-amd64 #1 SMP Debian 5.9.11-1kali1 (2020-12-01) x86_64 GNU/Linux It took over 12 hours to install and gave error information:

npm install @justalk/pornhub-api
npm WARN ERESOLVE overriding peer dependency
npm WARN Found: eslint@undefined
npm WARN node_modules/xo/node_modules/eslint
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer eslint@">=7.0.0" from eslint-config-prettier@7.0.0
npm WARN node_modules/xo/node_modules/eslint-config-prettier
npm WARN   eslint-config-prettier@"^7.0.0" from xo@0.36.1
npm WARN   node_modules/xo
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! Found: eslint@undefined
npm ERR! node_modules/eslint
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@">=7.11.0" from eslint-config-xo@0.33.1
npm ERR! node_modules/eslint-config-xo
npm ERR!   eslint-config-xo@"^0.33.1" from xo@0.36.1
npm ERR!   node_modules/xo
npm ERR!     dev xo@"*" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /home/kali/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/kali/.npm/_logs/2020-12-18T02_39_13_065Z-debug.log

To Reproduce Same thing when I tried to install the second time.

.npm/eresolve-report.txt

cat .npm/eresolve-report.txt
# npm resolution error report

2020-12-18T02:50:00.486Z

Found: eslint@undefined
node_modules/eslint

Could not resolve dependency:
peer eslint@">=7.11.0" from eslint-config-xo@0.33.1
node_modules/eslint-config-xo
  eslint-config-xo@"^0.33.1" from xo@0.36.1
  node_modules/xo
    dev xo@"*" from the root project

Fix the upstream dependency conflict, or retry
this command with --force, or --legacy-peer-deps
to accept an incorrect (and potentially broken) dependency resolution.

Raw JSON explanation object:

{
  "code": "ERESOLVE",
  "current": {
    "name": "eslint",
    "errors": [
      {
        "code": "FETCH_ERROR",
        "errno": "FETCH_ERROR",
        "type": "invalid-json",
        "requiredBy": "."
      }
    ],
    "package": {},
    "location": "node_modules/eslint",
    "dependents": []
  },
  "edge": {
    "type": "peer",
    "name": "eslint",
    "spec": ">=7.11.0",
    "error": "INVALID",
    "from": {
      "name": "eslint-config-xo",
      "version": "0.33.1",
      "location": "node_modules/eslint-config-xo",
      "dependents": [
        {
          "type": "prod",
          "name": "eslint-config-xo",
          "spec": "^0.33.1",
          "from": {
            "name": "xo",
            "version": "0.36.1",
            "location": "node_modules/xo",
            "dependents": [
              {
                "type": "dev",
                "name": "xo",
                "spec": "*",
                "from": {
                  "location": "/home/kali/Downloads/PORNHUB-API-3.4"
                }
              }
            ]
          }
        }
      ]
    }
  },
  "peerConflict": null,
  "strictPeerDeps": false,
  "force": false
}
JustalK commented 3 years ago

Merry Christmas !

Noted, I will look that today (23 December) and come back to you.

beesuns commented 3 years ago

Merry Christmas !

Noted, I will look that today (23 December) and come back to you.

Merry Christmas! I was looking forward to your reply.

JustalK commented 3 years ago

Hello beesuns,

Sorry for the waiting time, I was really busy. Can you share the package.json of your project. The problem is there. It's not on this project.

For the 12 hours, It might be npm experiencing some problem or your connection.