SurfSense/surfsense_web
2025-08-15 09:12:40 +02:00
..
.vscode Initial formatting using biome 2025-07-27 10:05:37 -07:00
app fix merge conflits 2025-08-15 09:12:40 +02:00
components add UI implementations 2025-08-15 09:12:40 +02:00
content/docs docs: updated info for kokoro 2025-08-13 17:57:33 -07:00
hooks check if a google calendar exixst before adding it , in the add page 2025-08-03 12:16:40 +02:00
lib Biome: fixes for hooks & lib directory 2025-07-27 10:44:27 -07:00
public chore: docs 2025-04-23 15:22:43 -07:00
.cursorrules feat: monorepo 2025-04-07 23:47:06 -07:00
.dockerignore feat: monorepo 2025-04-07 23:47:06 -07:00
.env.example feat: Add Docling support as ETL_SERVICE option 2025-07-20 11:42:55 +03:00
.gitignore updated .gitignore 2025-04-22 02:40:45 -07:00
biome.json Added config for biome.js 2025-07-26 20:52:13 -07:00
components.json Initial formatting using biome 2025-07-27 10:05:37 -07:00
Dockerfile fix: update Dockerfile to handle fumadocs-mdx postinstall error by copying config and content before installation 2025-04-24 18:23:11 -07:00
eslint.config.mjs Biome: fixes for eslint config 2025-07-27 11:47:38 -07:00
LICENSE feat: monorepo 2025-04-07 23:47:06 -07:00
mdx-components.tsx Initial formatting using biome 2025-07-27 10:05:37 -07:00
next.config.ts Added vecteezy path in next config iamges 2025-07-27 13:45:58 -07:00
package-lock.json feat: monorepo 2025-04-07 23:47:06 -07:00
package.json Fixed docker config to run on non-windows architectures 2025-08-01 10:34:01 -07:00
pnpm-lock.yaml Initial formatting using biome 2025-07-27 10:05:37 -07:00
postcss.config.mjs Initial formatting using biome 2025-07-27 10:05:37 -07:00
README.md feat: monorepo 2025-04-07 23:47:06 -07:00
source.config.ts Initial formatting using biome 2025-07-27 10:05:37 -07:00
tailwind.config.js Initial formatting using biome 2025-07-27 10:05:37 -07:00
tsconfig.json Initial formatting using biome 2025-07-27 10:05:37 -07:00

Next.js Token Handler Component

This project includes a reusable client component for Next.js that handles token storage from URL parameters.

TokenHandler Component

The TokenHandler component is designed to:

  1. Extract a token from URL parameters
  2. Store the token in localStorage
  3. Redirect the user to a specified path

Usage

import TokenHandler from '@/components/TokenHandler';

export default function AuthCallbackPage() {
  return (
    <div>
      <h1>Authentication Callback</h1>
      <TokenHandler 
        redirectPath="/dashboard" 
        tokenParamName="token" 
        storageKey="auth_token" 
      />
    </div>
  );
}

Props

The component accepts the following props:

  • redirectPath (optional): Path to redirect after storing token (default: '/')
  • tokenParamName (optional): Name of the URL parameter containing the token (default: 'token')
  • storageKey (optional): Key to use when storing in localStorage (default: 'auth_token')

Example URL

After authentication, redirect users to:

https://your-domain.com/auth/callback?token=your-auth-token

Implementation Details

  • Uses Next.js's useSearchParams hook to access URL parameters
  • Uses useRouter for client-side navigation after token storage
  • Includes error handling for localStorage operations
  • Displays a loading message while processing

Security Considerations

  • This implementation assumes the token is passed securely
  • Consider using HTTPS to prevent token interception
  • For enhanced security, consider using HTTP-only cookies instead of localStorage
  • The token in the URL might be visible in browser history and server logs

This is a Next.js project bootstrapped with create-next-app.

Getting Started

First, run the development server:

npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev

Open http://localhost:3000 with your browser to see the result.

You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.

This project uses next/font to automatically optimize and load Geist, a new font family for Vercel.

Learn More

To learn more about Next.js, take a look at the following resources:

You can check out the Next.js GitHub repository - your feedback and contributions are welcome!

Deploy on Vercel

The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.

Check out our Next.js deployment documentation for more details.