The latest updates on your projects. Learn more about Vercel for Git ↗︎

🦋 Changeset detected

Latest commit: ac022fb

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

!snapshot

!snapshot

I'm getting this error with @clerk/chrome-extension:

Uncaught Error: Cannot find module '@stripe/stripe-js'

Any suggestions?

Hi @wong2, please note that Clerk Billing is not available for Chrome Extensions due to limitations imposed by Chrome. Stripe requires remotely hosted code to function, which, for security purposes, causes Google to deny Chrome Store approvals.

Could you confirm for me that you’re not attempting to use Billing components?

Thank you!

@tmilewski Oh, I'm trying to use Clerk Billing in my extension, I'm using the PricingTable component.

Perhaps you should add a notice in the Chrome Extension docs? The PricingTable component is documented and exported from the package, so I thought it's ok to use it.

@wong2 I've added a PR to better catch this case in code here: #6179

I'll see what we can do about the documentation on two fronts:

1. Better indicate that the Clerk UI components (and related) sections of the sidebar are global and not framework-specific.
2. Add notices for the unsupported components.

@tmilewski Thanks!

Does this mean that the only way to use Billing in a Chrome extension is to enable syncHost and jump from the extension to the website to display the PricingTable? That way, once the payment is completed, the extension should be able to sync to the user's plan status, right?

@wong2 The answer there is "it depends." If you use a typical popup extension (or other type that you re-open) then, yes, everything should work as expected. If you're using an extension like a sidePanel, and it's persistent, then I would suggest trying out __experimental_syncHostListener. I haven't explicitly tested it against billing yet, but I believe it should work.

@tmilewski I will give it a try! My use case is the extension opens a persistent page (chrome-extension://<extension-id>/app.html).