fix(chrome-extension): Clear JWT on init, prior to polling

[tmilewski]

Description

An extension can wind up in a state where it doesn't have the latest JWT. To prevent this, we clear the current JWT and poll for the latest from the origin.

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

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

[changeset-bot[bot]]

🦋 Changeset detected

Latest commit: b5b62c937a59b2b88906008f4e45aa8da3ea3da1

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	0.0.2-snapshot.v3195533
@clerk/chrome-extension	1.1.3-snapshot.v3195533
@clerk/clerk-js	5.8.1-snapshot.v3195533
@clerk/clerk-expo	1.2.6-snapshot.v3195533
gatsby-plugin-clerk	5.0.0-beta.45
@clerk/testing	1.1.10-snapshot.v3195533

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

npm i @clerk/astro@0.0.2-snapshot.v3195533 --save-exact

@clerk/chrome-extension

npm i @clerk/chrome-extension@1.1.3-snapshot.v3195533 --save-exact

@clerk/clerk-js

npm i @clerk/clerk-js@5.8.1-snapshot.v3195533 --save-exact

@clerk/clerk-expo

npm i @clerk/clerk-expo@1.2.6-snapshot.v3195533 --save-exact

gatsby-plugin-clerk

npm i gatsby-plugin-clerk@5.0.0-beta.45 --save-exact

@clerk/testing

npm i @clerk/testing@1.1.10-snapshot.v3195533 --save-exact