Vercel and Netlify deployment in Svelte - Step-by-Step Execution

Concept Flow - Vercel and Netlify deployment

Write Svelte app code

↓

Build app locally

↓

Push code to GitHub

↓

Connect GitHub repo to Vercel or Netlify

↓

Platform builds app automatically

↓

Platform deploys app to web

↓

App is live at platform URL

This flow shows how you write your Svelte app, push it to GitHub, then connect and deploy it automatically on Vercel or Netlify.

Execution Sample

Svelte

npm run build
vercel --prod
# or
netlify deploy --prod --dir=build

Build your Svelte app and deploy it to Vercel or Netlify using their CLI commands.

Execution Table

Step	Action	Command/Process	Result
1	Build app locally	npm run build	Generates production-ready files in 'build' or 'dist' folder
2	Push code to GitHub	git push origin main	Code uploaded to GitHub repository
3	Connect repo to platform	Vercel or Netlify dashboard	Platform links to GitHub repo for deployment
4	Platform builds app	Automatic build on push	Platform runs build commands and prepares app
5	Platform deploys app	Automatic deployment	App is hosted and accessible via platform URL
6	Access live app	Open URL in browser	App loads and runs live on the internet

💡 Deployment completes when the app is live and accessible on the platform URL

Variable Tracker

Variable	Start	After Build	After Push	After Connect	After Deploy	Final
app_code	Written locally	Built files created	Code on GitHub	Repo linked to platform	App deployed	App live on URL
build_files	None	Created in build folder	None	Created by platform	Deployed to server	Serving live app

Key Moments - 3 Insights

Why do we need to push code to GitHub before deploying?

Platforms like Vercel and Netlify watch your GitHub repo to automatically build and deploy your app when you push code, as shown in execution_table step 3.

What happens if the build command fails on the platform?

The deployment stops and the app won't go live because the platform can't create the production files needed, as seen in execution_table step 4.

Can you deploy without building locally first?

Yes, platforms run the build automatically after connecting your repo, so local build is optional but helpful for testing, as shown in steps 1 and 4.

Visual Quiz - 3 Questions

Look at the execution_table, what is the result after step 2 (Push code to GitHub)?

A App is live on platform URL

B Platform builds app automatically

C Code uploaded to GitHub repository

D Build files created locally

💡 Hint

Check the 'Result' column for step 2 in the execution_table.

At which step does the platform link your GitHub repo for deployment?

A Step 1

B Step 3

C Step 5

D Step 6

💡 Hint

Look at the 'Action' column in execution_table for connecting repo.

If you skip pushing code to GitHub, what will happen in the deployment flow?

A Platform cannot build or deploy the app

B Build files will be created locally

C Platform will still deploy the app

D App will be live immediately

💡 Hint

Refer to the importance of step 2 in the execution_table and key_moments.

Concept Snapshot

Vercel and Netlify deployment flow:
1. Write and build your Svelte app locally.
2. Push code to GitHub repository.
3. Connect GitHub repo to Vercel or Netlify.
4. Platform auto-builds and deploys your app.
5. Your app is live at the platform URL.
Use platform dashboards or CLI for deployment commands.

Full Transcript

To deploy a Svelte app on Vercel or Netlify, first write your app code and build it locally using 'npm run build'. Then push your code to GitHub. Next, connect your GitHub repository to Vercel or Netlify via their dashboard. The platform will automatically build your app and deploy it to their servers. Finally, your app becomes live and accessible through the platform's URL. This process automates deployment and hosting, making your app available on the internet quickly and easily.

Practice

1. What is the main purpose of using Vercel or Netlify with a Svelte app?

easy

A. To write Svelte code faster using special editors

B. To easily deploy and host the app online with automatic updates

C. To convert Svelte code into plain HTML manually

D. To debug Svelte apps without running them

Solution

1. Step 1: Understand deployment platforms

   Vercel and Netlify are services that host web apps and update them automatically when code changes.

2. Step 2: Connect with Svelte app workflow

   They connect to your Git repo, build your Svelte app, and publish it online without manual steps.

3. Final Answer:

   To easily deploy and host the app online with automatic updates -> Option B

4. Quick Check:

   Deployment = Easy hosting and updates [OK]

Hint: Think: Vercel/Netlify = online hosting + auto updates [OK]

Common Mistakes:

• Confusing deployment with coding or debugging tools
• Thinking they convert code manually
• Assuming they only help with writing code

2. Which of the following is the correct step to deploy a Svelte app on Netlify?

easy

A. Set build command to 'npm run start' and publish directory to 'public'

B. Upload your Svelte files manually without any build settings

C. Connect Git repo and set build command to 'npm run build' with publish directory 'public/build'

D. Connect your Git repository, set build command to 'npm run build', and publish directory to 'build'

Solution

1. Step 1: Identify Netlify build settings for Svelte

   Netlify needs the build command 'npm run build' to compile the app and the publish directory where the built files are stored.

2. Step 2: Know Svelte's default build output

   Svelte outputs built files in 'public/build', so this should be the publish directory.

3. Final Answer:

   Connect Git repo and set build command to 'npm run build' with publish directory 'public/build' -> Option C

4. Quick Check:

   Netlify build = 'npm run build' + 'public/build' [OK]

Hint: Remember: build command builds, publish points to output folder [OK]

Common Mistakes:

• Using 'npm run start' instead of 'npm run build'
• Setting publish directory to 'build' instead of 'public/build'
• Uploading files manually without build

3. Given this Vercel deployment setting for a Svelte app:
Build Command: npm run build
Output Directory: build
What will happen when you push new code to Git?

medium

A. Vercel will build the app and deploy files from the 'build' folder

B. Vercel will fail because the output directory should be 'public/build'

C. Vercel will deploy the app but with old code only

D. Vercel will skip build and deploy source files directly

Solution

1. Step 1: Understand Vercel build and output settings

   Vercel runs the build command to create production files, then deploys from the specified output directory.

2. Step 2: Check if 'build' is valid output directory

   In many Svelte setups, the build output is in 'build' or 'public/build'. If 'build' is correct, deployment succeeds.

3. Final Answer:

   Vercel will build the app and deploy files from the 'build' folder -> Option A

4. Quick Check:

   Build + correct output folder = successful deploy [OK]

Hint: Build command + correct output folder = deploy success [OK]

Common Mistakes:

• Assuming output directory must be 'public/build' always
• Thinking Vercel deploys source files without build
• Confusing build failure with deployment failure

4. You deployed a Svelte app on Netlify but the site shows a 404 error after deployment. What is the most likely cause?

medium

A. The build command is set to 'npm run start' instead of 'npm run build'

B. The Git repository is empty and has no code

C. You forgot to connect your Git repo to Netlify

D. The publish directory is set incorrectly, so Netlify can't find the built files

Solution

1. Step 1: Analyze 404 error cause on Netlify

   A 404 after deployment usually means Netlify can't find the files to serve, often due to wrong publish directory.

2. Step 2: Check common misconfigurations

   If the publish directory is wrong, Netlify deploys an empty or wrong folder, causing 404 errors.

3. Final Answer:

   The publish directory is set incorrectly, so Netlify can't find the built files -> Option D

4. Quick Check:

   404 on deploy = wrong publish directory [OK]

Hint: 404 after deploy? Check publish directory first [OK]

Common Mistakes:

• Assuming empty Git repo causes 404 (usually build fails first)
• Forgetting to connect Git repo (would block deploy)
• Confusing build command with publish directory

5. You want to deploy a Svelte app on Vercel with these requirements:
- Use GitHub repo
- Automatically rebuild on push
- Serve from 'public' folder
Which setup is correct?

hard

A. Connect GitHub repo, set build command 'npm run build', output directory 'public'

B. Connect GitHub repo, set build command 'npm run dev', output directory 'public/build'

C. Connect GitHub repo, set build command 'npm run build', output directory 'public/build'

D. Connect GitHub repo, no build command, output directory 'public'

Solution

1. Step 1: Understand Vercel deployment with GitHub

   Connecting GitHub repo enables automatic rebuilds on push. The build command must create production files.

2. Step 2: Identify correct build command and output folder

   'npm run build' builds the app. To serve from 'public' folder as required, output directory must be 'public'.

3. Final Answer:

   Connect GitHub repo, set build command 'npm run build', output directory 'public' -> Option A

4. Quick Check:

   GitHub + build + 'public' output folder = proper deploy [OK]

Hint: Build with 'npm run build' and output 'public' [OK]

Common Mistakes:

• Using 'npm run dev' which is for local development
• Setting output directory to 'public/build' instead of 'public'
• Skipping build command causing no production files