fix(chrome-extension): Appropriately handle fulfilled, but null, cookie promises

[tmilewski]

Description

Depending on certain setups, we were receiving fulfulled, but null, promises. This updates that check.

Checklist

• npm test runs as expected.
• npm run build runs as expected.
• (If applicable) JSDoc comments have been added or updated for any package exports
• (If applicable) Documentation has been updated

Type of change

• 🐛 Bug fix
• 🌟 New feature
• 🔨 Breaking change
• 📖 Refactoring / dependency upgrade / documentation
• other:

[changeset-bot]

🦋 Changeset detected

Latest commit: 6146fa5

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

This PR includes changesets to release 1 package

Name	Type
@clerk/chrome-extension	Patch

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

[tmilewski]

!snapshot

[clerk-cookie]

Hey @tmilewski - the snapshot version command generated the following package versions:

Package	Version
@clerk/astro	1.0.2-snapshot.v6146fa5
@clerk/chrome-extension	1.1.6-snapshot.v6146fa5
@clerk/clerk-js	5.10.1-snapshot.v6146fa5
@clerk/clerk-expo	1.2.9-snapshot.v6146fa5
gatsby-plugin-clerk	5.0.0-beta.45
@clerk/localizations	2.5.1-snapshot.v6146fa5

Tip: Use the snippet copy button below to quickly install the required packages.
@clerk/astro

npm i @clerk/[email protected] --save-exact

@clerk/chrome-extension

npm i @clerk/[email protected] --save-exact

@clerk/clerk-js

npm i @clerk/[email protected] --save-exact

@clerk/clerk-expo

npm i @clerk/[email protected] --save-exact

gatsby-plugin-clerk

npm i [email protected] --save-exact

@clerk/localizations

npm i @clerk/[email protected] --save-exact

[royanger]

Working for customer who reported the issue.

[dimkl]

@tmilewski Why do we need this change? What does this affect? Was there an issue that this change fixes?

[tmilewski]

@dimkl It just affects the Chrome Extension. One person was seeing issues with a misconfigured manifest alongside a dev-in-prod scenario, this helps to mitigate that.