Vue CLI and Vite setup - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Vite's default production build output folder

Which folder does Vite use by default for its production build output?

A dist

B output

C public

D build

💡 Hint

Think about the folder name you see after running the build command in Vite.

Vite outputs production build files into the dist folder by default.

❓ component_behavior

intermediate

Behavior of hot module replacement (HMR) in Vue CLI vs Vite

Which statement correctly describes how hot module replacement (HMR) behaves differently between Vue CLI and Vite during development?

A Vue CLI uses native ES modules for HMR, Vite bundles code before serving.

B Vite disables HMR by default, Vue CLI enables it automatically.

C Vite provides faster HMR by using native ES modules, while Vue CLI bundles code before serving.

D Both Vue CLI and Vite use the same bundler and have identical HMR speeds.

💡 Hint

Consider how Vite serves files during development compared to Vue CLI.

Vite uses native ES modules in the browser for development, enabling faster HMR without rebundling. Vue CLI bundles code with webpack before serving, which is slower for HMR.

📝 Syntax

advanced

Correct command to create a new Vue 3 project using Vite

Which command correctly creates a new Vue 3 project using Vite with npm?

A npm install vite create my-vue-app --template vue

B npm init vue@latest my-vue-app

C vue create my-vue-app --template vite

D npm create vite@latest my-vue-app -- --template vue

💡 Hint

Vite uses a special npm create command with a template option.

The correct way to create a Vue 3 project with Vite is using npm create vite@latest my-vue-app -- --template vue. Other commands are either Vue CLI commands or invalid.

🔧 Debug

advanced

Error when running 'vue serve' in a Vite project

You run 'vue serve' inside a project created with Vite and get an error saying the command is not found. Why does this happen?

A 'vue serve' is a Vue CLI command and is not available in Vite projects.

B You need to install the 'vue-serve' package separately for Vite projects.

C The command should be 'vite serve' instead of 'vue serve'.

D 'vue serve' only works if you have Vue 2 installed.

💡 Hint

Think about which tool provides the 'vue serve' command.

'vue serve' is a command provided by Vue CLI's global tools and is not part of Vite. Vite uses 'vite' commands for serving projects.

❓ lifecycle

expert

How Vue CLI and Vite handle environment variables during build

Which statement correctly describes how Vue CLI and Vite handle environment variables during the build process?

A Vite requires variables to be prefixed with VUE_APP_, Vue CLI requires VITE_ prefix

B Vue CLI loads variables from .env files prefixed with VUE_APP_, Vite loads variables prefixed with VITE_

C Both Vue CLI and Vite load all variables from .env files without any prefix requirement

D Neither Vue CLI nor Vite support environment variables from .env files

💡 Hint

Look at the prefixes required by each tool for environment variables to be exposed.

Vue CLI exposes environment variables that start with VUE_APP_. Vite exposes variables starting with VITE_. This prevents accidental exposure of sensitive data.

Practice

1. What is the main purpose of Vue CLI and Vite in Vue development?

easy

A. To quickly create and manage Vue projects with build tools

B. To write Vue components without JavaScript

C. To replace Vue Router for navigation

D. To convert Vue code into plain HTML only

Solution

1. Step 1: Understand Vue CLI and Vite roles

   Both Vue CLI and Vite are tools to start Vue projects easily and provide build and development features.

2. Step 2: Identify their main purpose

   They help set up projects quickly with live reload and bundling, not replacing Vue Router or removing JavaScript.

3. Final Answer:

   To quickly create and manage Vue projects with build tools -> Option A

4. Quick Check:

   Vue CLI and Vite purpose = C [OK]

Hint: Think: tools to start and build Vue apps fast [OK]

Common Mistakes:

• Confusing Vue CLI with Vue Router
• Thinking Vite removes JavaScript
• Believing these tools only output HTML

2. Which command correctly creates a new Vue project using Vite?

easy

A. vue create my-vue-app

B. npm create vite@latest my-vue-app -- --template vue

C. npm install vite vue

D. vite new project vue

Solution

1. Step 1: Recall Vite project creation syntax

   The official way to create a Vue project with Vite is using npm create vite@latest with the --template vue flag.

2. Step 2: Compare options

   npm create vite@latest my-vue-app -- --template vue matches this syntax. vue create my-vue-app is Vue CLI syntax. Options C and D are incorrect commands.

3. Final Answer:

   npm create vite@latest my-vue-app -- --template vue -> Option B

4. Quick Check:

   Vite create command = B [OK]

Hint: Vite uses 'npm create vite@latest' with template flag [OK]

Common Mistakes:

• Using 'vue create' for Vite projects
• Trying to install Vite and Vue separately to create project
• Using invalid commands like 'vite new'

3. Given this command run in a terminal: vue create my-app, what will happen?

medium

A. It installs Vue globally on the system

B. It instantly creates a Vue project without prompts

C. It starts an interactive setup to create a Vue project

D. It runs the Vue development server immediately

Solution

1. Step 1: Understand 'vue create' command behavior

   The vue create command from Vue CLI launches an interactive prompt to select project options.

2. Step 2: Analyze other options

   It does not create instantly without prompts, nor does it install Vue globally or start the server immediately.

3. Final Answer:

   It starts an interactive setup to create a Vue project -> Option C

4. Quick Check:

   vue create = interactive setup [OK]

Hint: vue create prompts you to choose project options [OK]

Common Mistakes:

• Thinking it creates project instantly
• Confusing with npm install commands
• Expecting it to start the server automatically

4. You run npm run dev in a Vite project but get an error saying 'command not found'. What is the likely cause?

medium

A. You forgot to run npm install to install dependencies

B. You need to use vue serve instead

C. The dev script is only for Vue CLI projects

D. You must run vite build before npm run dev

Solution

1. Step 1: Understand npm scripts and dependencies

   The npm run dev command runs the dev server script defined in package.json. If dependencies are missing, the script may fail.

2. Step 2: Identify cause of 'command not found'

   Not running npm install means dependencies like Vite are missing, causing the error.

3. Final Answer:

   You forgot to run npm install to install dependencies -> Option A

4. Quick Check:

   Missing dependencies cause 'command not found' [OK]

Hint: Always run npm install before npm run dev [OK]

Common Mistakes:

• Using Vue CLI commands in Vite projects
• Trying to build before dev without install
• Assuming dev script is only for Vue CLI

5. You want to switch a Vue project from Vue CLI to Vite. Which step is essential to start this migration?

hard

A. Just change the start script in package.json to use Vite

B. Run vue upgrade vite to convert automatically

C. Replace vue.config.js with vite.config.js without changing files

D. Create a new Vite project and move your source files into it

Solution

1. Step 1: Understand migration approach

   Vue CLI and Vite have different setups. The safest way is to create a new Vite project and move your source code there.

2. Step 2: Evaluate other options

   There is no automatic vue upgrade vite command. Simply replacing config files or scripts won't work due to different build systems.

3. Final Answer:

   Create a new Vite project and move your source files into it -> Option D

4. Quick Check:

   Migration starts with new Vite project + source move [OK]

Hint: Start fresh Vite project, then copy your code [OK]

Common Mistakes:

• Expecting automatic conversion commands
• Only changing config files without new setup
• Assuming changing scripts is enough