Deployment to static hosting in Vue - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to build the Vue app for production.

Vue

npm run [1]

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

Aserve

Bstart

Cbuild

Ddev

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'serve' instead of 'build' will start a local server, not build files.

Using 'dev' runs the development server, not production build.

Running npm run build creates the optimized files for static hosting.

2fill in blank

medium

Complete the code to serve the built files locally for testing.

Vue

npx [1] dist

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

Avue-cli-service

Bhttp-server

Cnpm

Dserve

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'npm dist' is invalid.

Using 'vue-cli-service' requires extra arguments.

npx http-server dist serves the static files locally for preview.

3fill in blank

hard

Fix the error in the Vue config to set the correct base path for static hosting.

Vue

export default {
  [1]: '/my-app/'
}

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

AassetsDir

BbaseUrl

CoutputDir

DpublicPath

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'baseUrl' is deprecated and won't work in Vue 3.

Setting 'outputDir' changes build folder, not base path.

The publicPath option sets the base URL for the app when deployed.

4fill in blank

hard

Fill both blanks to configure the Vue app to output files to a folder named 'static' and set assets directory to 'assets'.

Vue

export default {
  outputDir: '[1]',
  assetsDir: '[2]'
}

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

Astatic

Bdist

Cassets

Dpublic

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing 'dist' with 'static' for outputDir.

Setting assetsDir to 'dist' is incorrect.

outputDir sets the build folder name, and assetsDir sets the folder for static assets inside it.

5fill in blank

hard

Fill all three blanks to create a simple GitHub Pages deployment script in package.json scripts.

Vue

"scripts": {
  "predeploy": "npm run [1]",
  "deploy": "gh-pages -d [2] --branch [3]"
}

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

Abuild

Bdist

Cgh-pages

Dmain

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'serve' instead of 'build' in predeploy.

Deploying from wrong folder or branch.

The predeploy script builds the app, and deploy publishes the dist folder to the gh-pages branch using gh-pages.

Practice

1. What is the main purpose of running npm run build in a Vue project before deployment?

easy

A. To start the development server for testing

B. To create optimized static files ready for hosting

C. To install project dependencies

D. To generate backend API endpoints

Solution

1. Step 1: Understand the build command role

   npm run build compiles Vue files into static assets like HTML, CSS, and JS.

2. Step 2: Identify deployment needs

   Static hosting requires these optimized files to serve the app efficiently.

3. Final Answer:

   To create optimized static files ready for hosting -> Option B

4. Quick Check:

   Build creates static files = A [OK]

Hint: Build command prepares files for static hosting [OK]

Common Mistakes:

• Confusing build with starting dev server
• Thinking build installs dependencies
• Expecting backend code generation

2. Which folder should you upload to your static hosting service after building a Vue app?

easy

A. dist

B. src

C. node_modules

D. public

Solution

1. Step 1: Identify build output folder

   Vue's build process outputs static files into the dist folder.

2. Step 2: Understand hosting requirements

   Static hosts serve files from the dist folder contents, not source or dependencies.

3. Final Answer:

   dist -> Option A

4. Quick Check:

   Upload dist folder = B [OK]

Hint: Upload the dist folder contents for deployment [OK]

Common Mistakes:

• Uploading source code instead of built files
• Uploading node_modules which is unnecessary
• Uploading public folder only

3. After deploying a Vue app's dist folder to GitHub Pages, what will happen if you visit the site URL?

medium

A. You will see the raw source code files

B. You will get a server error because GitHub Pages doesn't support Vue

C. You will see the Vue app running as expected

D. You will be redirected to the Vue CLI homepage

Solution

1. Step 1: Understand GitHub Pages hosting

   GitHub Pages serves static files, perfect for Vue apps built into static assets.

2. Step 2: Predict site behavior

   Visiting the URL loads the static files, so the Vue app runs normally in the browser.

3. Final Answer:

   You will see the Vue app running as expected -> Option C

4. Quick Check:

   Static hosting runs Vue app = A [OK]

Hint: Static hosting runs built Vue app directly [OK]

Common Mistakes:

• Thinking GitHub Pages can't host Vue apps
• Expecting server errors on static hosts
• Confusing source code with built app

4. You deployed your Vue app to Firebase Hosting but the app shows a blank page. What is the most likely cause?

medium

A. You did not configure Firebase to serve the dist folder

B. You uploaded the src folder instead of dist

C. You used the wrong Firebase project ID

D. You forgot to run npm run build before deploying

Solution

1. Step 1: Check build and upload correctness

   Assuming build and upload are correct, the blank page often means Firebase isn't serving the right folder.

2. Step 2: Verify Firebase hosting config

   Firebase needs firebase.json to point to dist as the public directory to serve files.

3. Final Answer:

   You did not configure Firebase to serve the dist folder -> Option A

4. Quick Check:

   Firebase config public folder = D [OK]

Hint: Check Firebase public folder setting matches dist [OK]

Common Mistakes:

• Uploading wrong folder but blaming build
• Ignoring firebase.json public directory setting
• Assuming project ID causes blank page

5. You want to deploy a Vue app with client-side routing to Netlify. Which step is essential to ensure routing works correctly on page reload?

hard

A. Rename dist folder to public

B. Disable JavaScript in the browser

C. Use server-side rendering instead of static hosting

D. Add a _redirects file with /index.html 200 rule

Solution

1. Step 1: Understand client-side routing issue

   On reload, Netlify tries to find the route as a file and fails without redirect.

2. Step 2: Use Netlify redirect rule

   Adding a _redirects file with /index.html 200 tells Netlify to serve index.html for all routes.

3. Final Answer:

   Add a _redirects file with /index.html 200 rule -> Option D

4. Quick Check:

   Redirect rule fixes routing reload = C [OK]

Hint: Use _redirects file for client-side routing on Netlify [OK]

Common Mistakes:

• Ignoring redirect rules causing 404 on reload
• Thinking JavaScript disabling helps routing
• Confusing folder names for deployment