Deployment to static hosting in Vue

Introduction

Deployment to static hosting means putting your Vue app online where anyone can visit it. It makes your app available without needing a server to run code.

You want to share your Vue website with friends or users.

You have a simple app that does not need a backend server.

You want fast loading pages from a simple hosting service.

You want to publish a portfolio or blog built with Vue.

You want to test your app on the internet before adding backend features.

Syntax

Vue

npm run build
# Then upload the contents of the 'dist' folder to your static host

The 'npm run build' command creates optimized files for production.

The 'dist' folder contains all files needed to serve your app.

Examples

Build your Vue app and deploy the 'dist' folder to popular static hosts like Netlify or Vercel.

Vue

npm run build
# Upload 'dist' folder to Netlify or Vercel

Use GitHub Pages by pushing the 'dist' files to a special branch for hosting.

Vue

npm run build
# Copy 'dist' folder contents to GitHub Pages branch

Firebase Hosting can serve your Vue app by uploading the build folder with their tools.

Vue

npm run build
# Upload 'dist' folder to Firebase Hosting using Firebase CLI

Sample Program

This simple Vue component shows a welcome message. After building with npm run build, you upload the dist folder to your static host.

Vue

<template>
  <main>
    <h1>Welcome to My Vue App</h1>
    <p>This app is ready for static hosting!</p>
  </main>
</template>

<script setup>
// No special code needed for deployment
</script>

<style scoped>
main {
  font-family: Arial, sans-serif;
  padding: 2rem;
  text-align: center;
}
</style>

Important Notes

Make sure your vue.config.js has the correct publicPath if your app is not at the root URL.

Static hosts only serve files; dynamic server code won't run here.

Use browser DevTools to check network and console for errors after deployment.

Summary

Build your Vue app with npm run build to prepare files for static hosting.

Upload the dist folder contents to a static hosting service like Netlify, GitHub Pages, or Firebase Hosting.

Static hosting is great for fast, simple Vue apps without backend needs.

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