[Deno] Invalid JSON received from the Stripe API

Describe the bug

stripe.accounts.createLoginLink throws error when executed in Deno environment.

To Reproduce

1. Create index.ts file
2. Add code
3. Run via Deno
4. Get error

Expected behavior

Request to execute successfully

Code snippets

// errors
const loginLink = await stripe.accounts.createLoginLink('acct_1LZWJGPPxRBiNZOx')

// works fine
const loginLink = await fetch(
  `https://api.stripe.com/v1/accounts/${'acct_1LZWJGPPxRBiNZOx'}/login_links`,
  {
    method: 'POST',
    headers: {
      Authorization: `Bearer ${Deno.env.get('STRIPE_API_KEY')}`,
    },
  }
).then((res) => res.json())

OS

macOS 11.06.1

Node version

Deno version: { deno: “1.20.3”, v8: “10.0.139.6”, typescript: “4.6.2” }

Library version

https://esm.sh/stripe@9.6.0?target=deno&no-check

API version

2020-08-27

Additional context

Related discussion on StripeDev Discord

Potentially related to https://github.com/stripe/stripe-node/issues/954 ?

[dcr-stripe]

The root cause issue here is Deno injects its own Content-Length header despite stripe-node providing a value for it, so the end request has this header twice and nginx returns a 400. I’ve filed https://github.com/denoland/deno/issues/15545 on the Deno side for this.

I’ll investigate to see if we can fix this from the Stripe side in the interim.

[dcr-stripe]

Hi @thorwebdev - thanks for the patience here!

I’ve released the fix under stripe-node@10.4.0-beta.1 . It now works for me. Could you try it out with your code just to double check, and if all works, I’ll release it to the main stable channel?

You can try this out using:

import Stripe from "https://esm.sh/stripe@10.4.0-beta.1?target=deno";

Thanks!