fix(webapp): conditionally load Stripe only when publishable key exists

[cyphercodes]

Problem

The Nango dashboard renders a completely blank/black screen on self-hosted instances because stripe.js attempts to initialize with an empty string, throwing an unhandled error that kills the entire React app.

Fixes #5640

Changes

• Modified packages/webapp/src/utils/stripe.ts to conditionally call loadStripe() only when publicStripeKey is truthy
• Returns null instead of calling loadStripe("") when the key is empty

Testing

• This fix prevents the IntegrationError: Please call Stripe() with your publishable key. You used an empty string. error
• Self-hosted instances will now load the dashboard properly
• Cloud instances with a valid Stripe key continue to work normally

---

This PR updates Stripe initialization to avoid calling loadStripe() with an empty publishable key. When globalEnv.publicStripeKey is falsy, stripePromise now resolves to null, preventing the self-hosted dashboard crash caused by Stripe's empty-key error.

---

This summary was automatically generated by @propel-code-bot

[propel-code-bot]

Suggested change to keep stripePromise consistently a Promise to avoid null runtime errors.

Status: Changes Suggested | Risk: Medium

Issues Identified & Suggestions

• Ensure stripePromise is always a Promise to avoid null usage: packages/webapp/src/utils/stripe.ts

Review Details

📁 1 files reviewed | 💬 1 comments

Instruction Files

└── .claude/
    ├── agents/
    │   └── nango-docs-migrator.md
    └── skills

👍 / 👎 individual comments to help improve reviews for you

[propel-code-bot]

[Reliability] The stripePromise variable can now be null directly if stripePublishableKey is falsy. However, loadStripe() itself always returns a Promise<Stripe | null>. This change means stripePromise's type effectively changes from Promise<Stripe | null> to Promise<Stripe | null> | null. Any code consuming stripePromise that expects it to always be a Promise (e.g., by calling .then() or awaiting it) will now encounter a runtime TypeError: Cannot read properties of null (reading 'then') if the key is not present.

Suggested change

	export const stripePromise = stripePublishableKey ? loadStripe(stripePublishableKey) : null;
	export const stripePromise = stripePublishableKey ? loadStripe(stripePublishableKey) : Promise.resolve(null);

Context for Agents

[**Bug**] The `stripePromise` variable can now be `null` directly if `stripePublishableKey` is falsy. However, `loadStripe()` itself always returns a `Promise<Stripe | null>`. This change means `stripePromise`'s type effectively changes from `Promise<Stripe | null>` to `Promise<Stripe | null> | null`. Any code consuming `stripePromise` that expects it to always be a Promise (e.g., by calling `.then()` or `await`ing it) will now encounter a runtime `TypeError: Cannot read properties of null (reading 'then')` if the key is not present.

```suggestion
export const stripePromise = stripePublishableKey ? loadStripe(stripePublishableKey) : Promise.resolve(null);
```

File: packages/webapp/src/utils/stripe.ts
Line: 6

[cyphercodes]

Updated the fix to keep astripePromisea consistently as a Promise to avoid null runtime errors. Changed the fallback from anulla to aPromise.resolve(null)a as suggested by propel-code-bot.

[propel-code-bot]

Review found no issues; changes appear appropriate and well-scoped.

Status: No Issues Found | Risk: Low

Review Details

📁 1 files reviewed | 💬 0 comments

Instruction Files

└── .claude/
    ├── agents/
    │   └── nango-docs-migrator.md
    └── skills

[cyphercodes]

Fixed, thanks for the review!