Why Project structure in Svelte? - Purpose & Use Cases

The Big Idea

What if your Svelte app could feel as neat and easy to navigate as a well-organized kitchen?

The Scenario

Imagine building a Svelte app by placing all your files randomly in one folder without any order.

As your app grows, finding components, styles, or scripts becomes a frustrating treasure hunt.

The Problem

Without a clear project structure, your code becomes messy and hard to maintain.

It's easy to lose track of where things are, causing bugs and slowing down development.

The Solution

Using a well-organized project structure groups related files logically.

This makes your Svelte app easier to understand, update, and scale smoothly.

Before vs After

✗ Before

App.svelte, Button.svelte, styles.css all in one folder

✓ After

src/components/Button.svelte, src/routes/Home.svelte, src/styles/global.css

What It Enables

A clear project structure lets you build bigger apps confidently and collaborate easily with others.

Real Life Example

Think of your project like a kitchen: if all utensils and ingredients are scattered, cooking is slow and stressful.

Organizing them in drawers and shelves speeds up cooking and keeps things pleasant.

Key Takeaways

Messy files slow you down and cause confusion.

A good project structure organizes your code logically.

This helps you build and maintain Svelte apps faster and better.

Practice

1. In a Svelte project, where should you place reusable components that can be used across multiple pages?

easy

A. static/components

B. src/routes

C. src/lib

D. public/assets

Solution

1. Step 1: Understand folder purpose

   src/lib is designed for reusable components and utilities.

2. Step 2: Compare with other folders

   src/routes holds pages, public/assets is for static files, and static/components is not a standard folder.

3. Final Answer:

   src/lib -> Option C

4. Quick Check:

   Reusable components = src/lib [OK]

Hint: Reusable parts go in src/lib folder [OK]

Common Mistakes:

• Putting reusable components in src/routes
• Using public folder for components
• Creating non-standard folders like static/components

2. Which of the following is the correct folder to place page files in a SvelteKit project?

easy

A. src/pages

B. src/lib

C. public/pages

D. src/routes

Solution

1. Step 1: Identify the folder for pages

   In SvelteKit, src/routes is the folder where page components live.

2. Step 2: Check other options

   src/lib is for reusable components, public/pages and src/pages are not standard folders for pages.

3. Final Answer:

   src/routes -> Option D

4. Quick Check:

   Pages go in src/routes [OK]

Hint: Pages always go in src/routes in SvelteKit [OK]

Common Mistakes:

• Confusing src/lib with src/routes
• Placing pages in public folder
• Using non-standard src/pages folder

3. Given the following SvelteKit project structure:

project/
├─ public/
│  └─ logo.png
├─ src/
│  ├─ lib/
│  │  └─ Button.svelte
│  └─ routes/
│     └─ index.svelte

Where should you import the Button.svelte component to use it on the homepage?

medium

A. From ./Button.svelte inside src/routes/index.svelte

B. From ../lib/Button.svelte inside src/routes/index.svelte

C. From ../../public/logo.png inside src/routes/index.svelte

D. From public/Button.svelte inside src/routes/index.svelte

Solution

1. Step 1: Understand folder hierarchy

   src/routes/index.svelte is one level deeper than src/lib/Button.svelte, so import path is ../lib/Button.svelte.

2. Step 2: Eliminate wrong paths

   ../../public/logo.png is for static assets, not components; ./Button.svelte assumes Button is in routes folder; public/Button.svelte is incorrect location.

3. Final Answer:

   From ../lib/Button.svelte inside src/routes/index.svelte -> Option B

4. Quick Check:

   Import reusable components with relative path ../lib [OK]

Hint: Use relative path ../lib to import components from routes [OK]

Common Mistakes:

• Trying to import components from public folder
• Using wrong relative path like ./Button.svelte
• Confusing static assets with components

4. You placed an image file inside src/lib/images and tried to use it in your SvelteKit page, but it doesn't load in the browser. What is the most likely reason?

medium

A. Static assets must be inside the public folder to be served correctly.

B. Images must be imported from src/routes folder only.

C. You need to rename the image file to have a .svelte extension.

D. The image file size is too large to load.

Solution

1. Step 1: Understand static asset serving

   SvelteKit serves static files only from the public folder, so files in src/lib/images are not accessible directly.

2. Step 2: Check other options

   Images don't belong in src/routes, renaming to .svelte is incorrect, and file size doesn't prevent loading if path is correct.

3. Final Answer:

   Static assets must be inside the public folder to be served correctly. -> Option A

4. Quick Check:

   Static files go in public folder [OK]

Hint: Put images in public folder to load in browser [OK]

Common Mistakes:

• Placing images inside src/lib or src/routes
• Renaming images as .svelte files
• Assuming large file size causes loading failure

5. You want to organize your SvelteKit project so that:
1. All page routes are inside src/routes.
2. Reusable UI components are inside src/lib/components.
3. Static assets like images and fonts are inside public/assets.

Which folder structure below correctly reflects this setup?

hard

A. project/
├─ public/
│ └─ assets/
│ ├─ images/
│ └─ fonts/
├─ src/
│ ├─ lib/
│ │ └─ components/
│ │ └─ Button.svelte
│ └─ routes/
│ └─ index.svelte

B. project/
├─ src/
│ ├─ assets/
│ │ ├─ images/
│ │ └─ fonts/
│ ├─ components/
│ │ └─ Button.svelte
│ └─ pages/
│ └─ index.svelte

C. project/
├─ public/
│ └─ components/
│ └─ Button.svelte
├─ src/
│ ├─ lib/
│ └─ routes/
│ └─ index.svelte

D. project/
├─ public/
│ └─ assets/
│ └─ Button.svelte
├─ src/
│ ├─ lib/
│ └─ routes/
│ └─ index.svelte

Solution

1. Step 1: Verify static assets location

   Static assets like images and fonts must be inside public/assets to be served correctly.

2. Step 2: Check reusable components and routes

   Reusable components go inside src/lib/components, and pages go inside src/routes.

3. Step 3: Match folder structure

   project/
   ├─ public/
   │  └─ assets/
   │     ├─ images/
   │     └─ fonts/
   ├─ src/
   │  ├─ lib/
   │  │  └─ components/
   │  │     └─ Button.svelte
   │  └─ routes/
   │     └─ index.svelte

   matches all requirements exactly; other options place assets or components incorrectly.

4. Final Answer:

   Option A folder structure -> Option A

5. Quick Check:

   Correct folder setup =

   project/
   ├─ public/
   │  └─ assets/
   │     ├─ images/
   │     └─ fonts/
   ├─ src/
   │  ├─ lib/
   │  │  └─ components/
   │  │     └─ Button.svelte
   │  └─ routes/
   │     └─ index.svelte

   [OK]

Hint: Static assets in public, components in src/lib, pages in src/routes [OK]

Common Mistakes:

• Putting static assets inside src folder
• Placing components in public folder
• Using non-standard folders like pages instead of routes