[PR #5189] [MERGED] feat(social-provider): add wechat social provider #22736

Closed
opened 2026-04-15 21:14:40 -05:00 by GiteaMirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/5189
Author: @Eric-Song-Nop
Created: 10/9/2025
Status: Merged
Merged: 3/11/2026
Merged by: @himself65

Base: canaryHead: feat/wechat-provider


📝 Commits (5)

  • 32a031a feat: add wechat social provider
  • 2d62e10 fix: removed dead code
  • 105ec45 docs: add WeChat social provider documentation
  • d5e0382 fix: address review issues in wechat social provider
  • 41750f4 fix: address cspell lint errors in wechat provider

📊 Changes

5 files changed (+312 additions, -0 deletions)

View changed files

📝 .cspell/third-party.txt (+1 -0)
docs/content/docs/authentication/wechat.mdx (+77 -0)
📝 landing/components/sidebar-content.tsx (+18 -0)
📝 packages/core/src/social-providers/index.ts (+3 -0)
packages/core/src/social-providers/wechat.ts (+213 -0)

📄 Description

This pull request introduces support for WeChat QR code scan login as a new social provider, and should resolve #4508 . The changes include the addition of the TikTok provider implementation.

Considerations

When doing use info querying, the WeChat app requires to carry the openid of the user, which is not part of the standard OAuth2 workflow, thus I am carrying the open id string in token for getUserInfo parameter and return type from validateAuthorizationCode and refreshAccessToken

The implementation is tested locally and should work.


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/better-auth/better-auth/pull/5189 **Author:** [@Eric-Song-Nop](https://github.com/Eric-Song-Nop) **Created:** 10/9/2025 **Status:** ✅ Merged **Merged:** 3/11/2026 **Merged by:** [@himself65](https://github.com/himself65) **Base:** `canary` ← **Head:** `feat/wechat-provider` --- ### 📝 Commits (5) - [`32a031a`](https://github.com/better-auth/better-auth/commit/32a031a3fb290c692cded06e8bc6a194bc9508a8) feat: add wechat social provider - [`2d62e10`](https://github.com/better-auth/better-auth/commit/2d62e10672166a638fca35f6b4bf1788045ba159) fix: removed dead code - [`105ec45`](https://github.com/better-auth/better-auth/commit/105ec452ce7a359bbd1271380e55a931b68d9321) docs: add WeChat social provider documentation - [`d5e0382`](https://github.com/better-auth/better-auth/commit/d5e0382973d398216301c73667cedf7ba58fc228) fix: address review issues in wechat social provider - [`41750f4`](https://github.com/better-auth/better-auth/commit/41750f45244b00279348f4eb8540a4d5e06d3bcb) fix: address cspell lint errors in wechat provider ### 📊 Changes **5 files changed** (+312 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `.cspell/third-party.txt` (+1 -0) ➕ `docs/content/docs/authentication/wechat.mdx` (+77 -0) 📝 `landing/components/sidebar-content.tsx` (+18 -0) 📝 `packages/core/src/social-providers/index.ts` (+3 -0) ➕ `packages/core/src/social-providers/wechat.ts` (+213 -0) </details> ### 📄 Description This pull request introduces support for WeChat QR code scan login as a new social provider, and should resolve #4508 . The changes include the addition of the TikTok provider implementation. ## Considerations When doing use info querying, the WeChat app requires to carry the openid of the user, which is not part of the standard OAuth2 workflow, thus I am carrying the open id string in token for getUserInfo parameter and return type from `validateAuthorizationCode` and `refreshAccessToken` The implementation is tested locally and should work. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-15 21:14:40 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#22736