fix: change API domain for twitter provider

[Leechael]

☕️ Reasoning

Switch X.com (former Twitter) API domain from twitter.com to x.com. When users switching between different accounts on x.com, the twitter.com/i/oauth2 endpoint still functional but not yet sync with up-to-date log in state. That's means:

• The user previously logged in to twitter.com with account A.
• Now, when visiting twitter.com, there is a forced redirect to x.com.
• The user switches to account B on x.com.
• The user then comes to our app and signs in with their Twitter account.
• However, the authentication confirmation page shows account A instead of account B.

🧢 Checklist

• Documentation
• Tests
• Ready to be merged

🎫 Affected issues

Fixes:

• Twitter auth is degraded since they changed to x.com  #10967
• Domain Changes in Twitter #10988

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
auth-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 31, 2024 8:26am

1 Ignored Deployment

Name	Status	Preview	Comments	Updated (UTC)
next-auth-docs	⬜️ Ignored (Inspect)	Visit Preview		May 31, 2024 8:26am

[vercel]

@Leechael is attempting to deploy a commit to the authjs Team on Vercel.

A member of the Team first needs to authorize it.

[k-taro56]

#10972

[k-taro56]

I think we need to think about renaming the provider name.

[Leechael]

I think we need to think about renaming the provider name.

That change might introduce breaking changes, Some users experienced unexpected behaviors after upgrading the next-auth.js.

If we going to rename the provider name, please considering in next big release version, not a minor bug fix.

[ndom91]

Yeah I've floating renaming the provider in general to the team. Lets see what they say 👍

[jellohouse]

Is this already fixed in the latest "next-auth": "^5.0.0-beta.19" release?

I tried to upgrade but it's still going to twitter.com

[mrienstra]

@jellohouse, last release of next-auth was June 1st, this PR was merged June 2nd, it was the second merge into main to "miss the boat": next-auth@5.0.0-beta.19...main

Just for convenience, relevant docs on installing a specific GitHub commit: npm, pnpm, yarn.

Edit: those changes were released in @auth/core@0.33.0, this worked for me (using pnpm):

  "pnpm": {
    "overrides": {
      "@auth/core": "0.33.0"
    }
  },