You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hey, i experienced weird issue with nextjs, better-auth and million/lint. when using better-auth in my nextjs app (which has MillionLint wrapper in config), the headers in the request been removed for some reason and social auth callback failed bc of that.
What version of
million
are you using?3.1.0
Are you using an SSR adapter? If so, which one?
None
What package manager are you using?
pnpm
What operating system are you using?
Mac
What browser are you using?
Chrome
Describe the Bug
hey, i experienced weird issue with nextjs, better-auth and million/lint. when using better-auth in my nextjs app (which has MillionLint wrapper in config), the headers in the request been removed for some reason and social auth callback failed bc of that.
![Image](https://private-user-images.githubusercontent.com/29498872/411419736-da090f49-f6ff-492e-89fe-b8f2f1092aa4.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkzMzUzMzgsIm5iZiI6MTczOTMzNTAzOCwicGF0aCI6Ii8yOTQ5ODg3Mi80MTE0MTk3MzYtZGEwOTBmNDktZjZmZi00OTJlLTg5ZmUtYjhmMmYxMDkyYWE0LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjEyVDA0MzcxOFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWNmMjdkMjMzODFiMTE0OTk3MjZhNDFiM2QzMDM2YTFjN2Y3NzdiNGY5ZTZiMzRjYWM1YjllYmE1YjMwOGE4ZWMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.uLd40lMk0-B6D5hau_W-MZVQSsq2PLfsPYQ2yCSiDUw)
removing this MillionLint.next wrapper - fixed it.
What's the expected result?
It should not remove headers.
Link to Minimal Reproducible Example
https://github.com/better-auth/better-auth/tree/main/demo/nextjs (we need to wrap next config with MillionLint)
Participation
The text was updated successfully, but these errors were encountered: