Static site generation with Nuxt in Vue - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to enable static site generation in Nuxt.

Vue

export default {
  target: '[1]'
}

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

Auniversal

Bstatic

Cserver

Ddynamic

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'server' instead of 'static' disables static generation.

Confusing 'universal' with static target.

Setting target to static tells Nuxt to generate a fully static site.

2fill in blank

medium

Complete the code to define a static route for pre-rendering in Nuxt.

Vue

export default {
  generate: {
    routes: [1]
  }
}

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

A['/about', '/contact']

B'/about, /contact'

C{'/about', '/contact'}

D['about', 'contact']

Attempts:

3 left

💡 Hint

Common Mistakes

Using a string instead of an array.

Omitting the leading slash in route paths.

The routes property expects an array of strings with leading slashes for paths.

3fill in blank

hard

Fix the error in the Nuxt config to correctly generate static pages.

Vue

export default {
  target: 'static',
  generate: {
    fallback: [1]
  }
}

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

Afalse

Bnull

Ctrue

D'404.html'

Attempts:

3 left

💡 Hint

Common Mistakes

Using boolean values instead of a filename string.

Setting fallback to null disables fallback page.

The fallback option should be a string naming the fallback HTML file for unknown routes.

4fill in blank

hard

Fill both blanks to create a dynamic route for static generation with params.

Vue

export default {
  generate: {
    routes() {
      return ['1', '2', '3'].map(id => `/user/[1]`)
    },
    fallback: [2]
  }
}

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

A${id}

Bfalse

C'404.html'

Did

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'id' without ${} inside template strings.

Setting fallback to a string instead of boolean.

Use template literals with ${id} to insert the id in the route string. Setting fallback to false disables fallback pages.

5fill in blank

hard

Fill all three blanks to generate a static site with custom routes and fallback.

Vue

export default {
  target: '[1]',
  generate: {
    routes: ['home', 'blog', 'contact'].map(page => `/$[2]`),
    fallback: [3]
  }
}

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

Astatic

Bpage

C'404.html'

Dpages

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong variable name inside template string.

Setting fallback to boolean instead of filename string.

Set target to 'static' for static generation. Use the variable 'page' inside the template string to build routes. Set fallback to '404.html' for unknown routes.

Practice

1. What does static site generation (SSG) in Nuxt do before users visit the site?

easy

A. Requires a server to render pages on demand

B. Generates pages dynamically on each user request

C. Builds all pages ahead of time as static files

D. Only builds the homepage statically

Solution

1. Step 1: Understand static site generation concept

   Static site generation means creating all pages before users visit, so they are ready as static files.

2. Step 2: Apply to Nuxt behavior

   Nuxt with static target builds all pages ahead, not on demand or partially.

3. Final Answer:

   Builds all pages ahead of time as static files -> Option C

4. Quick Check:

   SSG = Pre-build pages [OK]

Hint: SSG means pre-building pages before user visits [OK]

Common Mistakes:

• Confusing static generation with server-side rendering
• Thinking pages build on each request
• Assuming only homepage is static

2. Which Nuxt configuration option enables static site generation?

easy

A. target: 'static'

B. mode: 'universal'

C. ssr: false

D. buildModules: ['@nuxt/static']

Solution

1. Step 1: Identify Nuxt config for static generation

   Nuxt uses target: 'static' to enable static site generation.

2. Step 2: Check other options

   ssr: false disables server-side rendering but does not enable static generation; mode is deprecated; buildModules with '@nuxt/static' is invalid.

3. Final Answer:

   target: 'static' -> Option A

4. Quick Check:

   Static target = 'static' [OK]

Hint: Look for target set to 'static' in config [OK]

Common Mistakes:

• Using ssr: false instead of target: 'static'
• Confusing mode with target
• Assuming buildModules enables static

3. Given this Nuxt config snippet, what will be the output folder after running nuxt generate?

export default {
  target: 'static',
  generate: {
    dir: 'public'
  }
}

medium

A. A folder named 'build' will be created

B. A folder named 'dist' will be created

C. No folder will be created automatically

D. A folder named 'public' will be created

Solution

1. Step 1: Understand generate.dir option

   The generate.dir option sets the output folder for static files.

2. Step 2: Apply config values

   Since dir: 'public' is set, the static files will be generated inside a folder named 'public'.

3. Final Answer:

   A folder named 'public' will be created -> Option D

4. Quick Check:

   generate.dir = output folder [OK]

Hint: generate.dir sets output folder name [OK]

Common Mistakes:

• Assuming default 'dist' folder is always used
• Confusing generate.dir with buildDir
• Thinking no folder is created

4. You run nuxt generate but your dynamic routes are missing from the static site. What is the likely cause?

medium

A. You forgot to add the dynamic routes in generate.routes

B. You set target to 'server' instead of 'static'

C. You did not install the Nitro preset

D. You used ssr: false in config

Solution

1. Step 1: Understand dynamic routes in static generation

   Nuxt needs explicit dynamic routes listed in generate.routes to pre-build them.

2. Step 2: Check other options

   target: 'server' disables static generation but does not explain missing dynamic routes if static is used; Nitro preset is internal; ssr: false disables SSR but not related to dynamic routes generation.

3. Final Answer:

   You forgot to add the dynamic routes in generate.routes -> Option A

4. Quick Check:

   Dynamic routes need generate.routes [OK]

Hint: Add dynamic routes in generate.routes to include them [OK]

Common Mistakes:

• Assuming dynamic routes are auto-detected
• Confusing ssr: false with static target
• Thinking Nitro preset fixes missing routes

5. You want to build a blog with Nuxt static generation. Your posts are fetched from an API at build time. Which approach correctly generates static pages for each post?

hard

A. Fetch posts only on client side with mounted() and rely on client rendering

B. Use asyncData to fetch posts and list them, then add dynamic routes in generate.routes to pre-build each post page

C. Set ssr: false and generate pages dynamically on server

D. Use fetch() in components without configuring generate.routes

Solution

1. Step 1: Fetch posts at build time

   Using asyncData fetches posts during build, enabling static generation.

2. Step 2: Configure dynamic routes for posts

   Adding post URLs in generate.routes tells Nuxt to pre-build each post page as static HTML.

3. Step 3: Evaluate other options

   Client-side fetching delays content and is not static; ssr: false disables server rendering; fetch() without generate.routes won't pre-build dynamic pages.

4. Final Answer:

   Use asyncData and generate.routes to pre-build each post page -> Option B

5. Quick Check:

   asyncData + generate.routes = static dynamic pages [OK]

Hint: Use asyncData and generate.routes for static dynamic pages [OK]

Common Mistakes:

• Fetching posts only on client side
• Not adding dynamic routes in generate.routes
• Disabling SSR with ssr: false