fix(clerk-js): Enable captcha for development instances

[issuedat]

Description

Enables captcha for development instances.

Previously captcha was only usable on production instances and with recent changes, we now allow development instances running on localhost or other domains to also use captcha for parity with production.

We now rely on the value in the environment to determine if captcha is enabled or not (userSettings.signUp.captcha_enabled). For current development instances, it is disabled by default so this will be a no-op.

Checklist

• [x] pnpm test runs as expected.
• [x] pnpm 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: 752670e23b0de2e1f64a7480257942312af17db8

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

This PR includes changesets to release 3 packages

| Name | Type | | ----------------------- | ----- | | @clerk/clerk-js | Patch | | @clerk/chrome-extension | Patch | | @clerk/clerk-expo | 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

[vercel[bot]]

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

Name	Status	Preview	Comments	Updated (UTC)
clerk-js-sandbox	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 21, 2024 9:33am