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.

Sign up for GitHub

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

Jump to bottom

ParseError: Unexpected token '<' at 1:1 in https://hastebin.com/documents #7

Open
sinjs opened this issue Jan 29, 2021 · 1 comment
Open

ParseError: Unexpected token '<' at 1:1 in https://hastebin.com/documents #7

sinjs opened this issue Jan 29, 2021 · 1 comment

Comments

@sinjs
Copy link

sinjs commented Jan 29, 2021

When testing your program by running

echo "test" | hastebin

I am getting this error:

(node:24913) UnhandledPromiseRejectionWarning: ParseError: Unexpected token '<' at 1:1 in https://hastebin.com/documents
<!DOCTYPE html>
^
    at /usr/lib/node_modules/hastebin/node_modules/got/index.js:120:14
    at BufferStream.<anonymous> (/usr/lib/node_modules/hastebin/node_modules/read-all-stream/index.js:64:3)
    at BufferStream.emit (events.js:327:22)
    at finishMaybe (/usr/lib/node_modules/hastebin/node_modules/readable-stream/lib/_stream_writable.js:630:14)
    at afterWrite (/usr/lib/node_modules/hastebin/node_modules/readable-stream/lib/_stream_writable.js:492:3)
    at processTicksAndRejections (internal/process/task_queues.js:82:21)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:24913) 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: 1)
(node:24913) [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.

The same via the node api
@rahatarmanahmed
Copy link
Owner

rahatarmanahmed commented Jan 29, 2021 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rahatarmanahmed @sinjs