Why components are the building blocks in Svelte - Quick Recap

Recall & Review

beginner

What is a component in Svelte?

A component in Svelte is a reusable piece of code that controls a part of the user interface. It includes HTML, CSS, and JavaScript bundled together.

beginner

Why are components called the building blocks of an app?

Because components let you build small, manageable parts that fit together to create the whole app, like building blocks in a toy set.

beginner

How do components help with code reuse?

You can use the same component many times in different places, so you don’t have to write the same code again and again.

intermediate

What role does component isolation play in development?

Each component works independently, so changes in one part don’t break others. This makes fixing bugs and adding features easier.

intermediate

How do components improve teamwork in development?

Different team members can work on different components at the same time without interfering with each other’s work.

What does a Svelte component usually contain?

A HTML, CSS, and JavaScript

B Only HTML

C Only JavaScript

D Only CSS

A Svelte component bundles HTML, CSS, and JavaScript together to create a reusable UI part.

Why is component reuse helpful?

A It hides the UI

B It saves time by avoiding repeated code

C It increases bugs

D It makes the app slower

Reusing components saves time and effort by not rewriting the same code multiple times.

How do components help when fixing bugs?

A By deleting all code

B By changing the whole app at once

C By isolating changes to one part

D By hiding errors

Components isolate code so fixing one part doesn’t affect others, making debugging easier.

What is a benefit of components for teamwork?

A Only one person can work on the app

B Components slow down the team

C Components prevent collaboration

D Team members can work on different parts independently

Components let team members work on separate parts without conflicts, improving collaboration.

Why are components called 'building blocks'?

A Because they combine to build the whole app

B Because they are made of plastic

C Because they are heavy

D Because they are only for decoration

Components are like blocks that fit together to create the full app interface.

Explain in your own words why components are considered the building blocks of an app.

Think about how toys like Lego blocks fit together to build something bigger.

Describe how using components can help a team work better on a Svelte app.

Imagine a group project where everyone has their own task to do.

Practice

1. Why are components considered the building blocks in Svelte?

easy

A. Because they break the app into small, manageable parts

B. Because they only handle CSS styling

C. Because they replace JavaScript functions

D. Because they are only used for routing

Solution

1. Step 1: Understand the role of components

   Components divide the app into smaller parts that are easier to manage and understand.

2. Step 2: Recognize the benefits of components

   This division helps in reusing code and updating parts without affecting the whole app.

3. Final Answer:

   Because they break the app into small, manageable parts -> Option A

4. Quick Check:

   Components = small parts [OK]

Hint: Components split app into pieces for easy management [OK]

Common Mistakes:

• Thinking components only handle CSS
• Believing components replace JavaScript functions
• Assuming components are only for routing

2. Which of the following is the correct way to define a Svelte component file?

easy

A. A JavaScript file with .js extension only

B. Separate files for HTML, CSS, and JavaScript only

C. A CSS file with .css extension only

D. A file combining HTML, CSS, and JavaScript in one .svelte file

Solution

1. Step 1: Identify Svelte component structure

   Svelte components combine HTML, CSS, and JavaScript in a single .svelte file for simplicity.

2. Step 2: Compare with other options

   Other options separate concerns or use only one language, which is not how Svelte components work.

3. Final Answer:

   A file combining HTML, CSS, and JavaScript in one .svelte file -> Option D

4. Quick Check:

   Svelte = combined file [OK]

Hint: Svelte uses one file for HTML, CSS, JS [OK]

Common Mistakes:

• Thinking Svelte requires separate files for each language
• Confusing Svelte components with plain JS or CSS files
• Assuming components are only JavaScript

3. Given this Svelte component code:

<script>
  export let name = 'Friend';
</script>
<h1>Hello {name}!</h1>

What will be displayed if used as <Greeting name="Anna" />?

medium

A. Hello {name}!

B. Hello Friend!

C. Hello Anna!

D. Error: name not defined

Solution

1. Step 1: Understand prop passing in Svelte

   The component exports a variable name with default 'Friend'. Passing name="Anna" overrides this default.

2. Step 2: Evaluate the rendered output

   The {name} in the template will show 'Anna' because the prop was passed.

3. Final Answer:

   Hello Anna! -> Option C

4. Quick Check:

   Prop passed = displayed value [OK]

Hint: Passed props override defaults in Svelte [OK]

Common Mistakes:

• Ignoring the passed prop and using default
• Thinking {name} prints literally
• Assuming an error occurs without explicit declaration

4. What is wrong with this Svelte component code?

<script>
  let count = 0
  function increment() {
    count++
  }
</script>
<button on:click="increment()">Click</button>
<p>Count: {count}</p>

medium

A. Missing semicolons cause error

B. Event handler syntax should not use quotes

C. count variable should be exported

D. Function increment must be async

Solution

1. Step 1: Check event handler syntax in Svelte

   In Svelte, event handlers use on:event={handler} without quotes around the handler.

2. Step 2: Identify the error in code

   The code uses on:click="increment()" with quotes, which is incorrect and causes a syntax error.

3. Final Answer:

   Event handler syntax should not use quotes -> Option B

4. Quick Check:

   Event handler = no quotes [OK]

Hint: Use curly braces, no quotes for event handlers [OK]

Common Mistakes:

• Adding quotes around event handlers
• Thinking semicolons are mandatory in Svelte
• Believing variables must be exported to update

5. You want to create a reusable button component in Svelte that changes its label based on a passed prop and applies a CSS style only inside the component. Which of these is the best approach?

hard

A. Create a .svelte file combining HTML, CSS scoped to the component, and export a label prop

B. Write HTML and CSS in separate files and import them into a JavaScript file

C. Use global CSS and hardcode the label inside the component without props

D. Create a JavaScript function that returns HTML string with inline styles

Solution

1. Step 1: Understand Svelte component best practices

   Svelte components combine HTML, CSS scoped locally, and JavaScript in one file, making them reusable and encapsulated.

2. Step 2: Match requirements to approach

   Exporting a label prop allows dynamic text, and scoped CSS ensures styles don't leak outside the component.

3. Final Answer:

   Create a .svelte file combining HTML, CSS scoped to the component, and export a label prop -> Option A

4. Quick Check:

   Reusable + scoped CSS + props = Create a .svelte file combining HTML, CSS scoped to the component, and export a label prop [OK]

Hint: Use .svelte file with props and scoped CSS [OK]

Common Mistakes:

• Using global CSS causing style conflicts
• Hardcoding labels losing reusability
• Separating files unnecessarily in Svelte