vercel with astro framework throws bug

[wanghsinche]

Describe the bug

TypeError: Class extends value undefined is not a constructor or null
    at (entry.mjs:77:4827)
    at (render:middleware.js:1:17)

vercel API failed, but the static page works.
**It also works well in my local machine, weird. **
vercel node version is 18.x
the stripe package version is "stripe": "^12.3.0"

To Reproduce

page/api/stripe.ts

import type { APIRoute } from 'astro';
import Stripe from 'stripe';

const stripeKey: string = import.meta.env.STRIPE_APIKEY;
const webhookSecret: string = import.meta.env.STRIPE_WEBHOOK_SECRET;

export const post: APIRoute = async ({ request }) => {
  const signature = request.headers.get('Stripe-Signature');

  const stripe = new Stripe(stripeKey, {
    // This is needed to use the Fetch API rather than relying on the Node http
    // package.
    apiVersion: '2022-11-15',
  });

  return new Response(JSON.stringify({ msg: 'ok' }), { status: 200 });
};

Env:

vercel API failed, but the static page works. 
**It also works well in my local machine, weird. **
vercel node version is 18.x
the stripe package version is  "stripe": "^12.3.0"

Expected behavior

it should work in vercel

Code snippets

// pages/api/stripe.ts

import type { APIRoute } from 'astro';
import Stripe from 'stripe';

const stripeKey: string = import.meta.env.STRIPE_APIKEY;
const webhookSecret: string = import.meta.env.STRIPE_WEBHOOK_SECRET;

export const post: APIRoute = async ({ request }) => {
  const signature = request.headers.get('Stripe-Signature');

  const stripe = new Stripe(stripeKey, {
    // This is needed to use the Fetch API rather than relying on the Node http
    // package.
    apiVersion: '2022-11-15',
  });

  return new Response(JSON.stringify({ msg: 'ok' }), { status: 200 });
};

OS

linux

Node version

Node 18.x

Library version

12.3.0

API version

2022-11-15

Additional context

No response

[anniel-stripe]

Hi @wanghsinche , this appears to be the same issue as #1732 that is caused by an internal class extending the Event Web API, which the Vercel edge runtime doesn't support yet. In the meantime, you can use a polyfill (event-target-polyfill) for the Event API as suggested in vercel/edge-runtime#293.

[wanghsinche]

Hi @wanghsinche , this appears to be the same issue as #1732 that is caused by an internal class extending the Event Web API, which the Vercel edge runtime doesn't support yet. In the meantime, you can use a polyfill (event-target-polyfill) for the Event API as suggested in vercel/edge-runtime#293.

It works! Thank you so much and so quick reply!!! it is not easy to locate the reason. I struggled with it for a whole night without any progress. 😂

[anniel-stripe]

Glad it worked out! I'll close this issue as completed.