For those experiencing this bug, you can add this to your next.config.js:

const nextConfig = {
  // ...
  transpilePackages: ["@stripe/firestore-stripe-payments"],
};

Edit: You will need to restart the server and might still get an error in the console, but the package should still work normally.

I was able to reproduce this issue on all versions v0.0.3 to v0.0.6 with a next-js starter project.

├── @stripe/firestore-stripe-payments@0.0.3
├── next@12.0.10
├── react@17.0.2
└── react-dom@17.0.2

Couldn’t find any specific config changes that could cause this in firestore-stripe-payments codebase. However, I was able to fix the error by adding the following to next.config.js.

const withTM = require('next-transpile-modules')([
  '@stripe/firestore-stripe-payments'
]);

/** @type {import('next').NextConfig} */
module.exports = withTM({
  reactStrictMode: true,
});

Let us know if using next-transpile-modules in next.config.js could be a workaround until we find the root cause for this issue. Thanks!

FYI: @lemuel-stripe @cjavilla-stripe

With the sdk update, you need to change the workaround to :

const nextConfig = {
  ...
  transpilePackages: ["@invertase/firestore-stripe-payments"],
};

Same issue here, starting a new project that only has npm i firebase and npm i @stripe/firestore-stripe-payments with import getStripePayments from '@stripe/firestore-stripe-payments' and running the file with node <filename>.js is enough to reproduce the issue.