feat: add clerk authorized redirect origins

[ap-1]

No description provided.

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
web	🔄 Building (Inspect)	Visit Preview	💬 Add feedback	May 20, 2025 6:16pm

[Copilot]

Pull Request Overview

Adds Clerk authentication configuration by wrapping the Next.js root component with a ClerkProvider and whitelisting specific redirect origins, and introduces the Clerk package dependency.

• Wraps <Component> in ClerkProvider and sets allowedRedirectOrigins
• Adds @clerk/nextjs to project dependencies

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
src/pages/_app.tsx	Wraps the app in ClerkProvider with allowed redirect origins
package.json	Adds new dependency @clerk/nextjs@^6.19.5

Comments suppressed due to low confidence (2)

src/pages/_app.tsx:9

• [nitpick] You can combine multiple icons in a single call (e.g. library.add(faBars, faCircle, faCircleHollow)) to reduce repetitive invocations.

library.add(faBars);

src/pages/_app.tsx:14

• Introducing ClerkProvider with custom redirect origins adds new auth flow behavior; consider adding integration or CI tests to verify correct redirect handling.

<ClerkProvider

[Copilot]

Hardcoding redirect origins can make updates error-prone; consider extracting these URLs into environment variables or a configuration constant.

Suggested change

	allowedRedirectOrigins={[
	'https://www.cmucourses.com',
	'https://cmucourses.com',
	]}
	allowedRedirectOrigins={
	process.env.NEXT_PUBLIC_ALLOWED_REDIRECT_ORIGINS
	? process.env.NEXT_PUBLIC_ALLOWED_REDIRECT_ORIGINS.split(',')
	: []
	}

[Copilot]

The array for allowedRedirectOrigins is recreated on every render, which may trigger unnecessary re-renders; consider defining it outside the component scope.