UnhandledPromiseRejectionWarning when trying to increase quota

Been getting the following error for the past few days whenever I try to increase Warp+ quota:

PS > cf-warp 10
Prepare faking Warp+ referrer for 10 times.
(node:9748) UnhandledPromiseRejectionWarning: SyntaxError: Unexpected token e in JSON at position 0
at JSON.parse ()
at module.exports (O:\bin\node_14_13_0_npm_6_14_8\node_modules\cf-warp\lib\register.js:30:14)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async module.exports (O:\bin\node_14_13_0_npm_6_14_8\node_modules\cf-warp\lib\ref.js:4:2)
at async O:\bin\node_14_13_0_npm_6_14_8\node_modules\cf-warp\cli.js:83:4
(Use `node --trace-warnings ...` to show where the warning was created)
(node:9748) 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:9748) [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.

Quota doesn't seem to increase.

Reproduce the issue with `cf-warp 10` and start at `lib/register.js:30`, where the reported JSON.parse failure occurs. Trace how `lib/ref.js` and `cli.js` invoke it, then verify the response handling and error behavior. Done means the command no longer emits an unhandled rejection and the quota increase completes or reports a clear failure.

Written by the indexing model from the issue text.