Skip to content
This repository has been archived by the owner on Oct 28, 2022. It is now read-only.

Only absolute URLs are supported #12

Open
aryeharmon opened this issue Oct 5, 2020 · 1 comment
Open

Only absolute URLs are supported #12

aryeharmon opened this issue Oct 5, 2020 · 1 comment

Comments

@aryeharmon
Copy link

getting the follwoing error while running index.js

(node:7395) UnhandledPromiseRejectionWarning: TypeError: Only absolute URLs are supported
    at getNodeRequestOptions (/mnt/sdc/Code/telegram-channel-scraper/node_modules/node-fetch/lib/index.js:1257:9)
    at /mnt/sdc/Code/telegram-channel-scraper/node_modules/node-fetch/lib/index.js:1322:19
    at new Promise (<anonymous>)
    at fetch (/mnt/sdc/Code/telegram-channel-scraper/node_modules/node-fetch/lib/index.js:1319:9)
    at sendToServer (/mnt/sdc/Code/telegram-channel-scraper/chat-history.js:77:26)
    at chatHistory (/mnt/sdc/Code/telegram-channel-scraper/chat-history.js:56:24)
    at async run (/mnt/sdc/Code/telegram-channel-scraper/index.js:7:3)
(node:7395) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:7395) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

@cyvitor
Copy link

cyvitor commented Mar 10, 2021

i've got the same issue

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants