Geolocation and edge logic in NextJS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the Next.js geolocation hook.

NextJS

import { [1] } from 'next/navigation';

Drag options to blanks, or click blank then click option'

AuseGeolocation

BuseRouter

CusePathname

DuseSearchParams

Attempts:

3 left

💡 Hint

Common Mistakes

Using useRouter instead of useGeolocation.

Importing from 'next/router' instead of 'next/navigation'.

The useGeolocation hook is used to access geolocation data in Next.js edge components.

2fill in blank

medium

Complete the code to get the user's current position inside a React component.

NextJS

const position = [1]();

Drag options to blanks, or click blank then click option'

AuseGeolocation

BuseRouter

CuseState

DuseEffect

Attempts:

3 left

💡 Hint

Common Mistakes

Using useState or useEffect instead of useGeolocation.

Trying to call useRouter to get position.

The useGeolocation hook returns the user's current position in Next.js edge components.

3fill in blank

hard

Fix the error in the edge function export to enable geolocation support.

NextJS

export const runtime = [1];

Drag options to blanks, or click blank then click option'

A'client'

B'nodejs'

C'server'

D'edge'

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'nodejs' or 'server' disables edge features.

Using 'client' is not a valid runtime value.

Setting runtime to 'edge' enables edge functions which support geolocation in Next.js.

4fill in blank

hard

Fill both blanks to create a server action that uses geolocation and returns the country code.

NextJS

export const getCountry = async () => {
  const { country } = await fetch('/api/geo').then(res => res.json());
  return country [1] 'US' ? 'USA' : 'Other';
};

export const runtime = [2];

Drag options to blanks, or click blank then click option'

A===

B!==

C'edge'

D'server'

Attempts:

3 left

💡 Hint

Common Mistakes

Using !== instead of === causes wrong logic.

Setting runtime to 'server' disables edge features.

The code compares the country code with 'US' using strict equality ===. The runtime must be set to 'edge' to support geolocation.

5fill in blank

hard

Fill all three blanks to create a Next.js server component that fetches geolocation and displays the city.

NextJS

import React from 'react';

export const runtime = [1];

export default async function GeoCity() {
  const res = await fetch('/api/geo');
  const data = await res.json();
  const city = data.[2] ?? 'Unknown';

  return <p>Your city is: [3]</p>;
}

Drag options to blanks, or click blank then click option'

A'edge'

Bcity

C{city}

D'server'

Attempts:

3 left

💡 Hint

Common Mistakes

Setting runtime to 'server' disables edge features.

Using quotes around city in JSX instead of curly braces.

Accessing data.city as a string instead of a key.

The runtime is set to 'edge' for geolocation support. The city is accessed from the data object by the key city. The JSX expression uses curly braces {city} to display the city value.

Practice

1. What is the main purpose of using geolocation in a Next.js app with edge logic?

easy

A. To manage user authentication

B. To improve server-side rendering speed

C. To store user data securely

D. To customize content based on the user's location

Solution

1. Step 1: Understand geolocation usage

   Geolocation helps identify where a user is accessing the app from.

2. Step 2: Connect geolocation with edge logic

   Edge logic runs code near the user to customize responses quickly, often based on location.

3. Final Answer:

   To customize content based on the user's location -> Option D

4. Quick Check:

   Geolocation = Customize content [OK]

Hint: Geolocation customizes content by user location [OK]

Common Mistakes:

• Confusing geolocation with authentication
• Thinking geolocation improves rendering speed directly
• Assuming geolocation stores user data

2. Which of the following is the correct way to access the user's country code in Next.js middleware using edge logic?

easy

A. const country = request.geo.country

B. const country = request.location.countryCode

C. const country = request.headers['x-country']

D. const country = request.geoCode.country

Solution

1. Step 1: Recall Next.js middleware geo API

   Next.js provides a geo object on the request with location info.

2. Step 2: Identify correct property for country code

   The correct property is request.geo.country to get the country code.

3. Final Answer:

   const country = request.geo.country -> Option A

4. Quick Check:

   request.geo.country = country code [OK]

Hint: Use request.geo.country to get country code [OK]

Common Mistakes:

• Using incorrect property names like geoCode or location
• Trying to get country from headers without custom setup
• Confusing geo with location objects

3. Given this Next.js middleware code snippet, what will be the redirect URL if the user is from 'US'?

export function middleware(request) {
  const country = request.geo?.country || 'unknown';
  if (country === 'US') {
    return Response.redirect(new URL('/us-home', request.url));
  }
  return Response.next();
}

medium

A. /unknown

B. /home

C. /us-home

D. /

Solution

1. Step 1: Check country value from request

   The code sets country to request.geo?.country or 'unknown'. For a US user, it is 'US'.

2. Step 2: Analyze redirect condition

   If country is 'US', the middleware redirects to '/us-home'. Otherwise, it continues normally.

3. Final Answer:

   /us-home -> Option C

4. Quick Check:

   Country 'US' triggers redirect to /us-home [OK]

Hint: Country 'US' redirects to /us-home [OK]

Common Mistakes:

• Ignoring the redirect condition
• Assuming default path is used for US
• Confusing Response.next() with redirect

4. Identify the error in this Next.js middleware code that tries to redirect users from Canada to '/ca-home':

export function middleware(request) {
  const country = request.geo.country;
  if (country = 'CA') {
    return Response.redirect(new URL('/ca-home', request.url));
  }
  return Response.next();
}

medium

A. Missing optional chaining on request.geo

B. Using assignment '=' instead of comparison '===' in the if condition

C. Response.redirect should be Response.redirectTo

D. URL constructor is used incorrectly

Solution

1. Step 1: Check the if condition syntax

   The condition uses country = 'CA', which assigns 'CA' instead of comparing.

2. Step 2: Identify correct comparison operator

   It should use === to compare values, not =.

3. Final Answer:

   Using assignment '=' instead of comparison '===' in the if condition -> Option B

4. Quick Check:

   Use '===' for comparison, not '=' [OK]

Hint: Use '===' for comparison, not '=' [OK]

Common Mistakes:

• Confusing assignment and comparison operators
• Thinking Response.redirectTo exists
• Overlooking optional chaining necessity

5. You want to serve different homepage content for users from Europe and Asia using Next.js edge middleware. Which approach correctly implements this logic?

export function middleware(request) {
  const country = request.geo?.country || '';
  const europeCountries = ['FR', 'DE', 'IT'];
  const asiaCountries = ['JP', 'CN', 'IN'];

  if (europeCountries.includes(country)) {
    return Response.redirect(new URL('/eu-home', request.url));
  } else if (asiaCountries.includes(country)) {
    return Response.redirect(new URL('/asia-home', request.url));
  }
  return Response.next();
}

hard

A. This code correctly redirects European and Asian users to their homepages

B. The includes method cannot be used on arrays in middleware

C. The country variable should be fetched from request.headers instead

D. Response.redirect requires a status code as second argument

Solution

1. Step 1: Verify country detection and arrays

   The code safely gets country with optional chaining and defines arrays for Europe and Asia countries.

2. Step 2: Check redirect logic

   It uses includes to check membership and redirects accordingly, else continues normally.

3. Final Answer:

   This code correctly redirects European and Asian users to their homepages -> Option A

4. Quick Check:

   Array.includes works and redirects correctly [OK]

Hint: Use array.includes to check country and redirect [OK]

Common Mistakes:

• Thinking includes is not allowed in middleware
• Trying to get country from headers without setup
• Assuming Response.redirect needs status code