@salesforce/templates 66.7.6 → 66.7.8

package/lib/templates/project/reactexternalapp/AGENT.md

@@ -19,7 +19,7 @@ Replace `<appName>` with the actual folder name found under `uiBundles/`. The so
 ├── sfdx-project.json
 ├── package.json                         # SFDX root scripts 
 ├── scripts/
-│   ├── setup-cli.mjs                    # One-command setup (deploy, schema, build)
+│   ├── org-setup.mjs                    # One-time org setup (deploy, schema, build)
 │   └── graphql-search.sh               # Schema entity lookup
 ├── config/
 │   └── project-scratch-def.json
@@ -45,7 +45,7 @@ Replace `<appName>` with the actual folder name found under `uiBundles/`. The so
     └── data/                            # Sample data for import (optional)
 ```
 
-## Web application source structure
+## UI Bundle source structure
 
 All application code lives inside the UI Bundle's `src/` directory:
 
@@ -93,11 +93,13 @@ Used for SFDX metadata tooling. Scripts here target LWC/Aura, not the React app.
 | `npm run prettier` | Format metadata files |
 | `npm run prettier:verify` | Check Prettier |
 
-**One-command setup:** `node scripts/setup-cli.mjs --target-org <alias>` runs login, deploy, permset assignment, data import, GraphQL schema/codegen, UI Bundle build, and optionally the dev server. Use `--help` for all flags.
+**One-time org setup:** `node scripts/org-setup.mjs --target-org <alias>` runs login, deploy, permset assignment, data import, GraphQL schema/codegen, UI Bundle build, and optionally the dev server. Use `--help` for all flags.
 
-### 2. Web app directory (primary workspace)
+### 2. UI Bundle directory (primary workspace)
 
-**Always `cd` into the UI Bundle directory for dev/build/lint/test:**
+**ALL dev, build, lint, and test commands MUST be run from inside the UI Bundle directory (`<sfdx-source>/uiBundles/<appName>/`). Never run them from the project root.**
+
+Resolve the correct path from `sfdx-project.json` before running any command. Do not hardcode the path.
 
 | Command | Purpose |
 |---------|---------|
@@ -109,13 +111,17 @@ Used for SFDX metadata tooling. Scripts here target LWC/Aura, not the React app.
 | `npm run graphql:codegen` | Generate GraphQL types from schema |
 | `npm run graphql:schema` | Fetch GraphQL schema from org |
 
-**Before completing any change:** run `npm run build` and `npm run lint` from the UI Bundle directory. Both must pass with zero errors.
+**After every task, without exception:**
+1. Run `npm run build` from the UI Bundle directory — must pass with zero errors.
+2. Run `npm run lint` from the UI Bundle directory — must pass with zero errors.
+3. Run `npm run dev` to start the dev server so the user can verify the result.
 
+Do not consider a task complete until all three steps have been run successfully.
 ## Development conventions
 
 ### UI
 
-- **Component library:** shadcn/ui primitives in `src/components/ui/`. Always use these over raw HTML equivalents.
+- **Component library:** shadcn/ui primitives in `src/components/ui/`. Always use these over raw HTML equivalents. **Before importing any component, verify both the file exists in `src/components/ui/` AND the named export exists within that file.** Never assume a component or export is available — read the file to confirm the exact exports before importing.
 - **Styling:** Tailwind CSS only. No inline `style={{}}`. Use `cn()` from `@/lib/utils` for conditional classes.
 - **Icons:** Lucide React.
 - **Path alias:** `@/*` maps to `src/*`. Use it for all imports.
@@ -140,6 +146,10 @@ Used for SFDX metadata tooling. Scripts here target LWC/Aura, not the React app.
 
 ### Data access (Salesforce)
 
+**Before writing any code that connects to Salesforce, you MUST invoke the `using-ui-bundle-salesforce-data` skill. Do not write any data access code without consulting it first.**
+
+This applies to: GraphQL queries/mutations, REST calls, SDK initialization, custom hooks that fetch data, or any code that imports from `@salesforce/sdk-data`.
+
 - **All data access uses the Data SDK** (`@salesforce/sdk-data`) via `createDataSDK()`.
 - **Never** use `fetch()` or `axios` directly for Salesforce data.
 - **GraphQL is preferred** for record operations (`sdk.graphql`). Use `sdk.fetch` only when GraphQL cannot cover the case (UI API REST, Apex REST, Connect REST, Einstein LLM).
@@ -149,25 +159,74 @@ Used for SFDX metadata tooling. Scripts here target LWC/Aura, not the React app.
 - Use `__SF_API_VERSION__` global for API version in REST calls.
 - **Blocked APIs:** Enterprise REST query endpoint (`/query` with SOQL), `@AuraEnabled` Apex, Chatter API.
 
+#### Permitted APIs
+
+| API | Method | Endpoints / Use Case |
+|-----|--------|----------------------|
+| GraphQL | `sdk.graphql` | All record queries and mutations via `uiapi { }` namespace |
+| UI API REST | `sdk.fetch` | `/services/data/v{ver}/ui-api/records/{id}` |
+| Apex REST | `sdk.fetch` | `/services/apexrest/{resource}` |
+| Connect REST | `sdk.fetch` | `/services/data/v{ver}/connect/...` |
+| Einstein LLM | `sdk.fetch` | `/services/data/v{ver}/einstein/llm/prompt/generations` |
+
+Any endpoint not listed above is not permitted.
+
+#### GraphQL non-negotiable rules
+
+1. **Schema is the single source of truth** — every entity and field name must be confirmed via the schema search script before use. Never guess.
+2. **`@optional` on all record fields** — FLS causes entire queries to fail if any field is inaccessible. Apply to every scalar, parent, and child relationship field.
+3. **Correct mutation syntax** — mutations wrap under `uiapi(input: { allOrNone: true/false })`, not bare `uiapi { ... }`.
+4. **Explicit `first:` in every query** — omitting it silently defaults to 10 records. Always include `pageInfo { hasNextPage endCursor }` for paginated queries.
+5. **SOQL-derived execution limits** — max 10 subqueries per request, max 5 levels of child-to-parent traversal, max 1 level parent-to-child, max 2,000 records per subquery.
+6. **HTTP 200 does not mean success** — Salesforce returns HTTP 200 even on failure. Always check the `errors` array in the response body.
+
+#### GraphQL inline queries
+Must use the `gql` template tag from `@salesforce/sdk-data` — plain template strings bypass `@graphql-eslint` schema validation. For complex queries, use external `.graphql` files with codegen.
+
+#### Current user info
+Use GraphQL (`uiapi { currentUser { Id Name { value } } }`), not Chatter (`/chatter/users/me`).
+
+#### Schema file (`schema.graphql`)
+
+The `schema.graphql` file at the SFDX project root is the source of truth for all entity and field name lookups. It is 265K+ lines — never open or parse it directly. Use the schema search script instead.
+
+- **Generate/refresh:** Run `npm run graphql:schema` from the UI bundle directory
+- **When to regenerate:** After any metadata deployment that changes objects, fields, or permission sets
+- **Custom objects** only appear in the schema after metadata deployment AND permission set assignment
+- **After regenerating:** Always re-run `npm run graphql:codegen` and `npm run build` (schema changes may affect generated types)
+
 ### CSP trusted sites
 
 Any external domain the app calls (APIs, CDNs, fonts) must have a `.cspTrustedSite-meta.xml` file under `<sfdx-source>/cspTrustedSites/`. Unregistered domains are blocked at runtime. Each subdomain needs its own entry. URLs must be HTTPS with no trailing slash, no path, and no wildcards.
 
+## Building and launching the app
+
+All build, dev, and test commands run from the UI Bundle directory. Before running any command, read the UI Bundle's `package.json` to confirm available scripts — do not assume script names.
+
+Typical scripts found in the UI Bundle:
+
+| Command | Purpose |
+|---------|---------|
+| `npm run build` | TypeScript check + Vite production build |
+| `npm run dev` | Start Vite dev server |
+| `npm run lint` | ESLint |
+| `npm run test` | Vitest unit tests |
+| `npm run graphql:codegen` | Generate GraphQL types |
+| `npm run graphql:schema` | Fetch GraphQL schema from org |
+
+If dependencies have not been installed yet, run `npm install` in the UI Bundle directory first. Alternatively, run `npm run sf-project-setup` from the project root — it resolves the UI Bundle directory automatically and runs install, build, and dev in sequence.
+
+**After any JavaScript or TypeScript change, run `npm run build` to validate the change.** If the build fails, read the error output, identify the cause, fix it, and run `npm run build` again. Do not move on until the build passes.
+
 ## Deploying
 
 **Deployment order matters.** Metadata (objects, permission sets) must be deployed before fetching the GraphQL schema. After any metadata deployment that changes objects, fields, or permissions, re-run schema fetch and codegen.
 
-**Recommended sequence:**
+**Deployment steps:**
 
 1. Authenticate to the target org
 2. Build the UI Bundle (`npm run build` in the UI Bundle directory)
 3. Deploy metadata (`sf project deploy start --source-dir <packageDir> --target-org <alias>`)
-4. Assign permission sets
-5. Import data (only with user confirmation)
-6. Fetch GraphQL schema + run codegen (`npm run graphql:schema && npm run graphql:codegen`)
-7. Rebuild the UI Bundle (schema changes may affect generated types)
-
-**Or use the one-command setup:** `node scripts/setup-cli.mjs --target-org <alias>`
 
 ```bash
 # Deploy UI Bundle only
@@ -177,17 +236,17 @@ sf project deploy start --source-dir <sfdx-source>/ui-bundles --target-org <alia
 sf project deploy start --source-dir <packageDir> --target-org <alias>
 ```
 
-## Skills
+**Do not open the app after deployment.** Do not run `sf org open`, do not guess the runtime URL, and do not construct paths like `/s/<appName>`. Deployment is complete when the `sf project deploy start` command succeeds.
 
-Check for available skills before implementing any of the following:
+## Post-deployment org setup
 
-| Area | When to consult |
-|------|----------------|
-| UI generation | Building pages, components, modifying header/footer/layout |
-| Salesforce data access | Reading/writing records, GraphQL queries, REST calls |
-| Metadata and deployment | Scaffolding apps, configuring CSP, deployment sequencing |
-| Feature installation | Before building something from scratch — check if a pre-built feature exists |
-| File upload | Adding file upload with Salesforce ContentVersion |
-| Agentforce conversation | Adding or modifying the Agentforce chat widget |
+These steps apply after a fresh deployment to configure the org. They are not part of routine deployment.
+
+1. Assign permission sets
+2. Import data (only with user confirmation)
+3. Fetch GraphQL schema + run codegen (`npm run graphql:schema && npm run graphql:codegen`)
+4. Rebuild the UI Bundle (`npm run build` — schema changes may affect generated types)
+
+## Skills
 
-Skills are the authoritative source for detailed patterns, constraints, and code examples in each area. This file provides project-level orientation; skills provide implementation depth.
+Before starting any task, check whether a relevant skill exists. If one does, invoke it before writing any code or making any implementation decision. Skills are the authoritative source for patterns, constraints, and code examples.

package/lib/templates/project/reactexternalapp/CHANGELOG.md

@@ -3,6 +3,132 @@
 All notable changes to this project will be documented in this file.
 See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
 
+## [1.120.2](https://github.com/salesforce-experience-platform-emu/webapps/compare/v1.120.1...v1.120.2) (2026-04-01)
+
+**Note:** Version bump only for package @salesforce/ui-bundle-template-base-sfdx-project
+
+
+
+
+
+## [1.120.1](https://github.com/salesforce-experience-platform-emu/webapps/compare/v1.120.0...v1.120.1) (2026-04-01)
+
+**Note:** Version bump only for package @salesforce/ui-bundle-template-base-sfdx-project
+
+
+
+
+
+# [1.120.0](https://github.com/salesforce-experience-platform-emu/webapps/compare/v1.119.6...v1.120.0) (2026-04-01)
+
+**Note:** Version bump only for package @salesforce/ui-bundle-template-base-sfdx-project
+
+
+
+
+
+## [1.119.6](https://github.com/salesforce-experience-platform-emu/webapps/compare/v1.119.5...v1.119.6) (2026-04-01)
+
+**Note:** Version bump only for package @salesforce/ui-bundle-template-base-sfdx-project
+
+
+
+
+
+## [1.119.5](https://github.com/salesforce-experience-platform-emu/webapps/compare/v1.119.4...v1.119.5) (2026-03-31)
+
+**Note:** Version bump only for package @salesforce/ui-bundle-template-base-sfdx-project
+
+
+
+
+
+## [1.119.4](https://github.com/salesforce-experience-platform-emu/webapps/compare/v1.119.3...v1.119.4) (2026-03-31)
+
+
+### Bug Fixes
+
+* replace undefined WEBAPPLICATIONS_DIR with UIBUNDLES_DIR in org-setup ([#398](https://github.com/salesforce-experience-platform-emu/webapps/issues/398)) ([615d499](https://github.com/salesforce-experience-platform-emu/webapps/commit/615d49976fd4b92a840d25db79591e2818938a92))
+
+
+
+
+
+## [1.119.3](https://github.com/salesforce-experience-platform-emu/webapps/compare/v1.119.2...v1.119.3) (2026-03-31)
+
+**Note:** Version bump only for package @salesforce/ui-bundle-template-base-sfdx-project
+
+
+
+
+
+## [1.119.2](https://github.com/salesforce-experience-platform-emu/webapps/compare/v1.119.1...v1.119.2) (2026-03-31)
+
+**Note:** Version bump only for package @salesforce/ui-bundle-template-base-sfdx-project
+
+
+
+
+
+## [1.119.1](https://github.com/salesforce-experience-platform-emu/webapps/compare/v1.119.0...v1.119.1) (2026-03-31)
+
+**Note:** Version bump only for package @salesforce/ui-bundle-template-base-sfdx-project
+
+
+
+
+
+# [1.119.0](https://github.com/salesforce-experience-platform-emu/webapps/compare/v1.118.4...v1.119.0) (2026-03-31)
+
+**Note:** Version bump only for package @salesforce/ui-bundle-template-base-sfdx-project
+
+
+
+
+
+## [1.118.4](https://github.com/salesforce-experience-platform-emu/webapps/compare/v1.118.3...v1.118.4) (2026-03-31)
+
+**Note:** Version bump only for package @salesforce/ui-bundle-template-base-sfdx-project
+
+
+
+
+
+## [1.118.3](https://github.com/salesforce-experience-platform-emu/webapps/compare/v1.118.2...v1.118.3) (2026-03-31)
+
+**Note:** Version bump only for package @salesforce/ui-bundle-template-base-sfdx-project
+
+
+
+
+
+## [1.118.2](https://github.com/salesforce-experience-platform-emu/webapps/compare/v1.118.1...v1.118.2) (2026-03-31)
+
+
+### Bug Fixes
+
+* (@W-21734559) addresses missing .gitignore within template apps for vibes welcome experience ([#383](https://github.com/salesforce-experience-platform-emu/webapps/issues/383)) ([b8a35cf](https://github.com/salesforce-experience-platform-emu/webapps/commit/b8a35cf5352c231ccaa0797df88e64ee1c20a02a))
+
+
+
+
+
+## [1.118.1](https://github.com/salesforce-experience-platform-emu/webapps/compare/v1.118.0...v1.118.1) (2026-03-31)
+
+**Note:** Version bump only for package @salesforce/ui-bundle-template-base-sfdx-project
+
+
+
+
+
+# [1.118.0](https://github.com/salesforce-experience-platform-emu/webapps/compare/v1.117.5...v1.118.0) (2026-03-30)
+
+**Note:** Version bump only for package @salesforce/ui-bundle-template-base-sfdx-project
+
+
+
+
+
 ## [1.117.5](https://github.com/salesforce-experience-platform-emu/webapps/compare/v1.117.4...v1.117.5) (2026-03-30)
 
 **Note:** Version bump only for package @salesforce/ui-bundle-template-base-sfdx-project

package/lib/templates/project/reactexternalapp/README.md

@@ -15,15 +15,38 @@ An external React starter template for customer-facing apps on the Salesforce pl
 
 ## Getting started
 
-Navigate to the UI Bundle and install dependencies:
+Install project dependencies and start the local dev server:
 
 ```bash
-cd force-app/main/default/uiBundles/reactexternalapp
 npm install
-npm run dev
+npm run sf-project-setup
 ```
 
-Opens at http://localhost:5173 by default. For build and test instructions, see the [UI Bundle README](force-app/main/default/uiBundles/reactexternalapp/README.md).
+This installs the UI Bundle dependencies, builds the app, and opens the dev server at http://localhost:5173. For manual build and test instructions, see the [UI Bundle README](force-app/main/default/uiBundles/reactexternalapp/README.md).
+
+## Add features
+
+Use the features CLI to install additional UI features into the UI Bundle.
+
+List all available features:
+
+```bash
+npx @salesforce/ui-bundle-features-experimental list
+```
+
+Get details about a specific feature (description, dependencies, files, and integration examples):
+
+```bash
+npx @salesforce/ui-bundle-features-experimental describe <feature-name>
+```
+
+Install a feature:
+
+```bash
+npx @salesforce/ui-bundle-features-experimental install <feature-name> --ui-bundle-dir reactexternalapp
+```
+
+After installation, the CLI will list any `__example__` files that need manual integration. Read each example file to see the integration pattern, apply it to the target file, then delete the example file.
 
 ## Deploy
 
@@ -38,7 +61,7 @@ sf project deploy start --source-dir force-app --target-org <alias>
 
 ```bash
 cd force-app/main/default/uiBundles/reactexternalapp && npm install && npm run build && cd -
-sf project deploy start --source-dir force-app/main/default/ui-bundles --target-org <alias>
+sf project deploy start --source-dir force-app/main/default/uiBundles --target-org <alias>
 ```
 
 ### Deploy Experience Cloud site only
@@ -60,6 +83,38 @@ sf project deploy start --source-dir force-app/main/default/classes --target-org
 
 Replace `<alias>` with your target org alias.
 
+## Setup scripts
+
+Two npm scripts at the project root streamline getting started and deployment.
+
+**`npm run sf-project-setup`** — installs the UI Bundle dependencies, builds the app, and starts the dev server (see [Getting started](#getting-started)).
+
+**`npm run setup`** — runs the full deployment setup in one command: org login (if needed), UI Bundle build, deploy metadata, fetch GraphQL schema, run codegen, and optionally start the dev server:
+
+```bash
+npm run setup -- --target-org <alias>
+```
+
+Running without flags presents an interactive step picker. Pass `--yes` to skip it and run all steps immediately:
+
+```bash
+npm run setup -- --target-org <alias> --yes
+```
+
+Common options:
+
+| Option                    | Description                                    |
+| ------------------------- | ---------------------------------------------- |
+| `--skip-login`            | Skip browser login (org already authenticated) |
+| `--skip-deploy`           | Do not deploy metadata                         |
+| `--skip-graphql`          | Skip GraphQL schema fetch and codegen          |
+| `--skip-ui-bundle-build`  | Skip `npm install` and UI Bundle build         |
+| `--skip-dev`              | Do not start the dev server at the end         |
+| `--ui-bundle-name <name>` | UI Bundle folder name when multiple exist      |
+| `-y, --yes`               | Skip interactive step picker; run all steps    |
+
+For all options: `npm run setup -- --help`.
+
 ## Configure Your Salesforce DX Project
 
 The `sfdx-project.json` file contains useful configuration information for your project. See [Salesforce DX Project Configuration](https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_ws_config.htm) in the _Salesforce DX Developer Guide_ for details about this file.

package/lib/templates/project/reactexternalapp/_p_/_m_/_w_/_a_/package.json

@@ -3,6 +3,9 @@
   "private": true,
   "version": "1.59.0",
   "type": "module",
+  "engines": {
+    "node": ">=22"
+  },
   "scripts": {
     "dev": "vite",
     "dev:design": "vite --mode design",
@@ -15,8 +18,8 @@
     "graphql:schema": "node scripts/get-graphql-schema.mjs"
   },
   "dependencies": {
-    "@salesforce/sdk-data": "^1.117.5",
-    "@salesforce/ui-bundle": "^1.117.5",
+    "@salesforce/sdk-data": "^1.120.2",
+    "@salesforce/ui-bundle": "^1.120.2",
     "@tailwindcss/vite": "^4.1.17",
     "class-variance-authority": "^0.7.1",
     "clsx": "^2.1.1",
@@ -43,7 +46,7 @@
     "@graphql-eslint/eslint-plugin": "^4.1.0",
     "@graphql-tools/utils": "^11.0.0",
     "@playwright/test": "^1.49.0",
-    "@salesforce/vite-plugin-ui-bundle": "^1.117.5",
+    "@salesforce/vite-plugin-ui-bundle": "^1.120.2",
     "@testing-library/jest-dom": "^6.6.3",
     "@testing-library/react": "^16.1.0",
     "@testing-library/user-event": "^14.5.2",

package/lib/templates/project/reactexternalapp/_p_/_m_/_w_/_a_/src/_f_/_os_/utils/filterUtils.ts

@@ -385,7 +385,16 @@ function buildSingleFilter<TFilter>(
 			if (!value) return null;
 			const searchFields = config?.searchFields ?? [];
 			if (searchFields.length === 0) return null;
-			const clauses = searchFields.map((f) => ({ [f]: { like: `%${value}%` } }) as TFilter);
+			// Supports dot-notation for relationship fields (e.g. "User__r.Name")
+			// by building nested filter objects: { User__r: { Name: { like: "%x%" } } }
+			const clauses = searchFields.map((f) => {
+				const parts = f.split(".");
+				let clause: Record<string, unknown> = { like: `%${value}%` };
+				for (let i = parts.length - 1; i >= 0; i--) {
+					clause = { [parts[i]]: clause };
+				}
+				return clause as TFilter;
+			});
 			if (clauses.length === 1) return clauses[0];
 			return { or: clauses } as TFilter;
 		}

package/lib/templates/project/reactexternalapp/_p_/_m_/_w_/_a_/src/_f_/authentication/menu/AuthMenu.tsx

@@ -0,0 +1,93 @@
+import { CircleUser, LogIn, LogOut, UserPen, UserPlus } from "lucide-react";
+import { Link } from "react-router";
+import { useAuth } from "../context/AuthContext";
+import { ROUTES } from "../authenticationConfig";
+import { Button } from "../../../components/ui/button";
+import { Skeleton } from "../../../components/ui/skeleton";
+import {
+	DropdownMenu,
+	DropdownMenuContent,
+	DropdownMenuItem,
+	DropdownMenuLabel,
+	DropdownMenuSeparator,
+	DropdownMenuTrigger,
+} from "../../../components/ui/dropdown-menu";
+
+interface User {
+	readonly id: string;
+	readonly name: string;
+}
+
+export interface AuthMenuProps {
+	/** Custom trigger button for the authenticated user's dropdown */
+	trigger?: (user: User) => React.ReactNode;
+	/** Content rendered instead of the dropdown when the user is not logged in (e.g. a standalone Sign In button) */
+	guestContent?: React.ReactNode;
+	/** Extra menu items inserted after "Edit Profile" and before "Sign Out" */
+	menuItems?: React.ReactNode;
+	/** CSS class applied to the DropdownMenuContent wrapper */
+	className?: string;
+}
+
+export function AuthMenu({ trigger, guestContent, menuItems, className }: AuthMenuProps) {
+	const { user, isAuthenticated, loading, logout } = useAuth();
+
+	if (loading) {
+		return <Skeleton className="size-8 rounded-full" />;
+	}
+
+	if (!isAuthenticated && guestContent) {
+		return <>{guestContent}</>;
+	}
+
+	const defaultTrigger = (
+		<Button variant="ghost" size="icon" aria-label="User menu">
+			<CircleUser className="size-6" />
+		</Button>
+	);
+
+	const triggerNode = (isAuthenticated && user && trigger?.(user)) || defaultTrigger;
+
+	return (
+		<DropdownMenu>
+			<DropdownMenuTrigger asChild>{triggerNode}</DropdownMenuTrigger>
+
+			<DropdownMenuContent align="end" className={className ?? "w-48"}>
+				{isAuthenticated ? (
+					<>
+						<DropdownMenuLabel className="truncate">{user?.name}</DropdownMenuLabel>
+						<DropdownMenuSeparator />
+						<DropdownMenuItem asChild>
+							<Link to={ROUTES.PROFILE.PATH}>
+								<UserPen className="size-4" />
+								Edit Profile
+							</Link>
+						</DropdownMenuItem>
+						{menuItems}
+						<DropdownMenuItem onClick={() => logout()}>
+							<LogOut className="size-4" />
+							Sign Out
+						</DropdownMenuItem>
+					</>
+				) : (
+					<>
+						<DropdownMenuItem asChild>
+							<Link to={ROUTES.LOGIN.PATH}>
+								<LogIn className="size-4" />
+								Log In
+							</Link>
+						</DropdownMenuItem>
+						<DropdownMenuItem asChild>
+							<Link to={ROUTES.REGISTER.PATH}>
+								<UserPlus className="size-4" />
+								Register
+							</Link>
+						</DropdownMenuItem>
+					</>
+				)}
+			</DropdownMenuContent>
+		</DropdownMenu>
+	);
+}
+
+export default AuthMenu;