Comparing changes

…er and validator (#2693) ### Changes This PR completes the migration from the deprecated jest-environment-jsdom-global package to the standard jest-environment-jsdom, fixing all test failures and resolving security vulnerabilities. ### Package Updates - Removed deprecated `jest-environment-jsdom-global` dependency - Using `jest-environment-jsdom@30.2.0` (already at target version) - Updated `validator` from `^13.6.0` to `^13.15.22` (security fix) - Keeping `auth0-js@9.29.0` (latest v9.x) - Keeping `@auth0/component-cdn-uploader@2.4.2` ### Test Infrastructure Changes - Created custom Jest environment to expose `jsdom` instance - Enhanced `setURL()` utility with dual-approach `window.location` mocking - Updated 2 snapshot files - Cleaned up unnecessary code in setup-tests.js ### Testing - No functional changes in production code. - All test suites continue to pass with the updated setup. - Minor snapshot changes due to rendering differences in updated jsdom and Jest versions. ### Checklist * [ ] I have read the [Auth0 general contribution guidelines](https://github.com/auth0/open-source-template/blob/master/GENERAL-CONTRIBUTING.md) * [ ] I have read the [Auth0 Code of Conduct](https://github.com/auth0/open-source-template/blob/master/CODE-OF-CONDUCT.md) * [ ] All code quality tools/guidelines have been run/followed * [ ] All relevant assets have been compiled

Bumps [form-data](https://github.com/form-data/form-data) from 2.5.3 to 2.5.5. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/form-data/form-data/blob/master/CHANGELOG.md">form-data's changelog</a>.</em></p> <blockquote> <h2><a href="https://github.com/form-data/form-data/compare/v2.5.4...v2.5.5">v2.5.5</a> - 2025-07-18</h2> <h3>Commits</h3> <ul> <li>[meta] actually ensure the readme backup isn’t published <a href="https://github.com/form-data/form-data/commit/10626c0a9b78c7d3fcaa51772265015ee0afc25c"><code>10626c0</code></a></li> <li>[Fix] use proper dependency <a href="https://github.com/form-data/form-data/commit/026abe5c5c0489d8a2ccb59d5cfd14fb63078377"><code>026abe5</code></a></li> </ul> <h2><a href="https://github.com/form-data/form-data/compare/v2.5.3...v2.5.4">v2.5.4</a> - 2025-07-17</h2> <h3>Fixed</h3> <ul> <li>[Fix] <code>append</code>: avoid a crash on nullish values <a href="https://redirect.github.com/form-data/form-data/issues/577"><code>[#577](https://github.com/form-data/form-data/issues/577)</code></a></li> </ul> <h3>Commits</h3> <ul> <li>[eslint] update linting config <a href="https://github.com/form-data/form-data/commit/8bf2492e0555d41ff58fa04c91593af998f87a3c"><code>8bf2492</code></a></li> <li>[meta] add <code>auto-changelog</code> <a href="https://github.com/form-data/form-data/commit/b5101ad3d5f73cfd0143aae3735b92826fd731ea"><code>b5101ad</code></a></li> <li>[Tests] handle predict-v8-randomness failures in node < 17 and node > 23 <a href="https://github.com/form-data/form-data/commit/0e93122358414942393d9c2dc434ae69e58be7c8"><code>0e93122</code></a></li> <li>[Fix] Switch to using <code>crypto</code> random for boundary values <a href="https://github.com/form-data/form-data/commit/b88316c94bb004323669cd3639dc8bb8262539eb"><code>b88316c</code></a></li> <li>[Fix] validate boundary type in <code>setBoundary()</code> method <a href="https://github.com/form-data/form-data/commit/131ae5efa30b9c608add4faef3befb38aa2e1bf1"><code>131ae5e</code></a></li> <li>[Tests] Switch to newer v8 prediction library; enable node 24 testing <a href="https://github.com/form-data/form-data/commit/c97cfbed9eb6d2d4b5d53090f69ded4bf9fd8a21"><code>c97cfbe</code></a></li> <li>[Refactor] use <code>hasown</code> <a href="https://github.com/form-data/form-data/commit/97ac9c208be0b83faeee04bb3faef1ed3474ee4c"><code>97ac9c2</code></a></li> <li>[meta] remove local commit hooks <a href="https://github.com/form-data/form-data/commit/be99d4eea5ce47139c23c1f0914596194019d7fb"><code>be99d4e</code></a></li> <li>[Dev Deps] remove unused deps <a href="https://github.com/form-data/form-data/commit/ddbc89b6d6d64f730bcb27cb33b7544068466a05"><code>ddbc89b</code></a></li> <li>[meta] fix scripts to use prepublishOnly <a href="https://github.com/form-data/form-data/commit/e351a97e9f6c57c74ffd01625e83b09de805d08a"><code>e351a97</code></a></li> <li>[Dev Deps] remove unused script <a href="https://github.com/form-data/form-data/commit/8f233664842da5bd605ce85541defc713d1d1e0a"><code>8f23366</code></a></li> <li>[Dev Deps] add missing peer dep <a href="https://github.com/form-data/form-data/commit/02ff026fda71f9943cfdd5754727c628adb8d135"><code>02ff026</code></a></li> <li>[meta] fix readme capitalization <a href="https://github.com/form-data/form-data/commit/2fd5f61ebfb526cd015fb8e7b8b8c1add4a38872"><code>2fd5f61</code></a></li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/form-data/form-data/commit/40de5a74209992979f6695d894c1d554ddb72f29"><code>40de5a7</code></a> v2.5.5</li> <li><a href="https://github.com/form-data/form-data/commit/026abe5c5c0489d8a2ccb59d5cfd14fb63078377"><code>026abe5</code></a> [Fix] use proper dependency</li> <li><a href="https://github.com/form-data/form-data/commit/10626c0a9b78c7d3fcaa51772265015ee0afc25c"><code>10626c0</code></a> [meta] actually ensure the readme backup isn’t published</li> <li><a href="https://github.com/form-data/form-data/commit/efe6c2693159084b18c58648e77203d1d810395b"><code>efe6c26</code></a> v2.5.4</li> <li><a href="https://github.com/form-data/form-data/commit/c97cfbed9eb6d2d4b5d53090f69ded4bf9fd8a21"><code>c97cfbe</code></a> [Tests] Switch to newer v8 prediction library; enable node 24 testing</li> <li><a href="https://github.com/form-data/form-data/commit/0e93122358414942393d9c2dc434ae69e58be7c8"><code>0e93122</code></a> [Tests] handle predict-v8-randomness failures in node < 17 and node > 23</li> <li><a href="https://github.com/form-data/form-data/commit/b88316c94bb004323669cd3639dc8bb8262539eb"><code>b88316c</code></a> [Fix] Switch to using <code>crypto</code> random for boundary values</li> <li><a href="https://github.com/form-data/form-data/commit/b70869dad20175aad0230ad5f1d030fb76232df8"><code>b70869d</code></a> [Fix] <code>append</code>: avoid a crash on nullish values</li> <li><a href="https://github.com/form-data/form-data/commit/131ae5efa30b9c608add4faef3befb38aa2e1bf1"><code>131ae5e</code></a> [Fix] validate boundary type in <code>setBoundary()</code> method</li> <li><a href="https://github.com/form-data/form-data/commit/8bf2492e0555d41ff58fa04c91593af998f87a3c"><code>8bf2492</code></a> [eslint] update linting config</li> <li>Additional commits viewable in <a href="https://github.com/form-data/form-data/compare/v2.5.3...v2.5.5">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=form-data&package-manager=npm_and_yarn&previous-version=2.5.3&new-version=2.5.5)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/auth0/lock/network/alerts). </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

… between Login and Sign-up tabs (#2697) ### Changes Fixes a bug where connectionResolver callback receives the wrong field value when users switch between Login and Sign-up tabs that have different field types (username vs email). Closes #2631 ### Root Cause The bug was in `src/ui/box/container.jsx` in the `checkConnectionResolver()` method at line 80: **BEFORE** (buggy code) `const userInputValue = c.getFieldValue(lock, 'username') || c.getFieldValue(lock, 'email'); ` This code always prioritized the username field over email, regardless of which screen (Login vs Sign-up) was currently active. Since both field values exist in the global lock state, it would retrieve the Login username even when on the Sign-up screen. ### Solution Modified checkConnectionResolver() to check which screen is currently active and prioritize the appropriate field: **AFTER** (fixed code) ``` const isSignUpScreen = screenName && screenName.includes('signUp'); const userInputValue = databaseUsernameValue(lock, isSignUpScreen ? { emailFirst: true } : {}); ``` ### Testing Manual testing performed - - Verified bug exists in original code - Applied fix and verified bug is resolved - Tested multiple scenarios: - Sign-up with email (email prioritized) - Sign-up with username only (username used) - Login with username (username prioritized) - Login with email (email used) - Switch from Login to Sign-up with pre-filled fields (correct field used) ### Checklist * [x] I have read the [Auth0 general contribution guidelines](https://github.com/auth0/open-source-template/blob/master/GENERAL-CONTRIBUTING.md) * [x] I have read the [Auth0 Code of Conduct](https://github.com/auth0/open-source-template/blob/master/CODE-OF-CONDUCT.md) * [x] All code quality tools/guidelines have been run/followed * [x] All relevant assets have been compiled

**Fixed** - Fix: connectionResolver receives incorrect field value when switching between Login and Sign-up tabs [\#2697](#2697) ([ankita10119](https://github.com/ankita10119))

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Comparing changes

Open a pull request

Commits on Nov 28, 2025

Commits on Dec 3, 2025

This comparison is taking too long to generate.

Uh oh!