Unable to accept npm invite because Create button is disabled

[GianMLP]

Select Topic Area

Bug

Body

Following an invite link in Chrome, I fill in my details, yet the Create an Account button remains disabled. The password meets the requirements. The EULA and Privacy Policy checkbox is checked. There is no text describing if there's an error. I've tried in Incognito mode as well.

Trying the same thing in Safari, the validation rules actually show up for the username.

Back in Chrome I use a lower case username, but the button is still disabled. That's when I notice that on Safari there is a Captcha test that never appears on Chrome. I disable my VPN and now the captcha test appears in Chrome!

I go through the test and apparently I already have an account with that username. When did that happen? I'm not in the org that I was invited to in the first place. So I click on the original invite link and it works, all is well.

So I solved my problem, but there's a number of issues with the invite flow that need to be addressed.

[ashmeet07]

This is an excellent and detailed report of issues with the npm invitation flow. The problems are primarily caused by the silent failure of the Captcha and inconsistent validation.

---

npm Invitation Flow Issues (Bug Report Summary) 🐛

1. Captcha Failure / VPN Interference (Critical Bug)

Symptom	Observed Behavior (Chrome/VPN)	Required Fix
Disabled "Create Account" Button	Button remains disabled even when all visible fields (password, EULA) are correctly filled.	The button's activation logic should be improved to clearly indicate missing requirements.
Missing Captcha Element	The Captcha fails to load silently when the user's connection (e.g., VPN) blocks it.	Implement a Fallback Notification: If the Captcha fails to load, the user must see a clear error message (e.g., "Captcha failed to load. Check your network or disable your VPN.") instead of simply having the "Create" button disabled.

---

2. Silent Client-Side Validation

Symptom	Observed Behavior (Chrome vs. Safari)	Required Fix
No Error Feedback	Incorrect input (e.g., invalid username casing) had no visible validation error in Chrome.	Ensure Cross-Browser Consistency: Implement robust client-side validation that provides immediate, clear, and visible error messages for all required fields in all supported browsers (Chrome, Safari, etc.).
Inconsistent Validation	Validation hints/rules appeared in Safari but failed to appear in Chrome.	All validation logic must execute reliably and consistently regardless of the browser.

---

3. Confusing Account Existence Check

Symptom	Observed Behavior	Recommended Flow
Login/Creation Conflict	After Captcha validation, the system stated the user already had an account with that username.	The flow for invitation links should check for existing accounts first. If an account exists: Prompt for Login $\rightarrow$ Accept Invite. Do not force the user through the account creation form if they are already registered.