-
-
Notifications
You must be signed in to change notification settings - Fork 532
feat: new auth & payment system #1617
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@blocknote/ariakit
@blocknote/code-block
@blocknote/core
@blocknote/mantine
@blocknote/react
@blocknote/server-util
@blocknote/shadcn
@blocknote/xl-docx-exporter
@blocknote/xl-multi-column
@blocknote/xl-odt-exporter
@blocknote/xl-pdf-exporter
commit: |
imo
wdyt? We also need to think about what to do with current sponsors. If we can easily detect sponsors when people sign in with github, that would be great. However, I wouldn't spend more than 2-3 hours on this. If we can't make it work we can hardcode a list of sponsors or sth |
For the auth system I chose to go with better-auth and for the payment system, I chose to go with polar.sh.
There is an already existing integration between the two, maintained by the polar team, as a better-auth plugin.
It's documented on both sides polar's docs and better-auth's docs.
Why Better-auth?
Why Polar?
This PR implements an integration for our Next.js application, it uses the better-auth Next.js integration, and then uses the polar better-auth integration on top of that.
Things to sort out
Demo
Screen.Recording.2025-04-18.at.17.55.34.mp4