Optional parameters in Svelte - Performance & Optimization

Performance: Optional parameters

LOW IMPACT

Optional parameters affect how components receive and handle data, impacting initial rendering and reactivity updates.

Passing optional parameters to a Svelte component

Svelte

<script>
  export let title = "Default Title";
  export let subtitle = null;
</script>

<h1>{title}</h1>
{#if subtitle}
  <h2>{subtitle}</h2>
{/if}

Default values reduce undefined checks and prevent unnecessary reactive updates.

📈 Performance GainReduces reactive triggers and improves interaction responsiveness

Passing optional parameters to a Svelte component

Svelte

<script>
  export let title;
  export let subtitle;
</script>

<h1>{title}</h1>
{#if subtitle}
  <h2>{subtitle}</h2>
{/if}

Not providing default values means undefined parameters cause extra checks and potential reactivity triggers.

📉 Performance CostTriggers extra reactive updates when parameters are undefined or missing

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
No default for optional params	Extra reactive checks	Multiple reflows if params change	Higher paint cost due to re-renders	[X] Bad
Default values for optional params	Minimal reactive triggers	Single reflow on change	Lower paint cost with stable updates	[OK] Good

Rendering Pipeline

Optional parameters flow through the component initialization and reactive update stages. Proper defaults reduce unnecessary reactive recalculations and DOM updates.

→Component Initialization

→Reactive Update

→DOM Update

⚠️ BottleneckReactive Update stage due to unnecessary reactivity triggers from undefined parameters

Core Web Vital Affected

INP

Optional parameters affect how components receive and handle data, impacting initial rendering and reactivity updates.

Optimization Tips

1Always assign default values to optional parameters in Svelte components.

2Avoid undefined optional parameters to reduce reactive triggers.

3Check performance in DevTools to confirm fewer reactive updates.

Performance Quiz - 3 Questions

What is the main performance benefit of using default values for optional parameters in Svelte components?

A It increases the bundle size significantly.

B It reduces unnecessary reactive updates and improves interaction responsiveness.

C It delays the initial component rendering.

D It causes more DOM nodes to be created.

DevTools: Performance

How to check: Record a performance profile while interacting with the component. Look for reactive updates and DOM changes triggered by parameter changes.

What to look for: Fewer reactive updates and shorter scripting times indicate better handling of optional parameters.

Practice

1. In Svelte, how do you make a component prop optional?

easy

A. Use export let propName = defaultValue;

B. Use let propName; without export

C. Use export const propName; without a value

D. Use function propName() {} inside the component

Solution

1. Step 1: Understand Svelte prop declaration

   Props are declared with export let to receive values from outside.

2. Step 2: Assign default value to make prop optional

   Assigning a default value like = defaultValue means the prop is optional and uses that value if none is passed.

3. Final Answer:

   Use export let propName = defaultValue; -> Option A

4. Quick Check:

   Optional prop = export let with default [OK]

Hint: Add = defaultValue after export let to make prop optional [OK]

Common Mistakes:

• Forgetting to export the prop
• Not assigning a default value
• Using const instead of let for props

2. Which of the following is the correct syntax to define an optional parameter in a JavaScript function inside a Svelte component?

easy

A. function greet(name: 'Guest') { console.log(name); }

B. function greet(name) { console.log(name || 'Guest'); }

C. function greet(name?) { console.log(name); }

D. function greet(name = 'Guest') { console.log(name); }

Solution

1. Step 1: Recall JavaScript default parameter syntax

   Default values are assigned using = value in the parameter list.

2. Step 2: Identify correct syntax

   function greet(name = 'Guest') { console.log(name); } uses name = 'Guest', which is valid and makes the parameter optional.

3. Final Answer:

   function greet(name = 'Guest') { console.log(name); } -> Option D

4. Quick Check:

   Default parameter = param = value [OK]

Hint: Use param = defaultValue in function signature for optional params [OK]

Common Mistakes:

• Using TypeScript syntax like name?
• Using colon instead of equals for default
• Using logical OR inside function body instead of default param

3. What will be the output of this Svelte component code?

 <script>
  export let greeting = 'Hello';
  export let name;
</script>

<p>{greeting}, {name || 'Friend'}!</p>

If used as <Component /> with no props passed?

medium

A. Hello, Friend!

B. Hello, undefined!

C. , Friend!

D. undefined, Friend!

Solution

1. Step 1: Check default values of props

   greeting has default 'Hello', name is undefined because no prop passed.

2. Step 2: Evaluate expression in template

   {name || 'Friend'} uses 'Friend' because name is falsy (undefined).

3. Final Answer:

   Hello, Friend! -> Option A

4. Quick Check:

   Default greeting + fallback name = Hello, Friend! [OK]

Hint: Use || to provide fallback for undefined props [OK]

Common Mistakes:

• Expecting undefined to print as string
• Forgetting default value for greeting
• Assuming name defaults to empty string

4. Identify the error in this Svelte component code that tries to make a prop optional:

<script>
  export let count;
  if (count === undefined) {
    count = 10;
  }
</script>

medium

A. The if condition should check for null instead of undefined

B. The default value must be assigned during export, not later

C. You cannot assign to an exported prop inside the script after declaration

D. There is no error; this code works fine

Solution

1. Step 1: Understand Svelte prop reactivity rules

   Exported props are reactive and should not be reassigned directly inside the script after declaration.

2. Step 2: Identify correct way to set default

   Default values must be assigned during export, like export let count = 10;, not by reassigning later.

3. Final Answer:

   You cannot assign to an exported prop inside the script after declaration -> Option C

4. Quick Check:

   Default props assigned during export only [OK]

Hint: Assign default value in export let, not by reassigning later [OK]

Common Mistakes:

• Trying to reassign exported props inside script
• Checking wrong condition for default
• Assuming reassignment updates prop externally

5. You want to create a Svelte component that accepts an optional size prop with default 'medium' and an optional color prop with default 'blue'. Which code correctly implements this and uses both props in the template?

hard

A. <script>
let size = 'medium';
let color = 'blue';
</script>

<div style="font-size: {size}; color: {color};">Styled Text</div>

B. <script>
export let size = 'medium';
export let color = 'blue';
</script>

<div style="font-size: {size}; color: {color};">Styled Text</div>

C. <script>
export const size = 'medium';
export const color = 'blue';
</script>

<div style="font-size: {size}; color: {color};">Styled Text</div>

D. <script>
export let size;
export let color;
size ||= 'medium';
color ||= 'blue';
</script>

<div style="font-size: {size}; color: {color};">Styled Text</div>

Solution

1. Step 1: Check how to declare optional props with defaults

   Props must be declared with export let and assigned default values directly.

2. Step 2: Verify usage in template

   Using {size} and {color} inside style attribute is correct.

3. Final Answer:

   <script> export let size = 'medium'; export let color = 'blue'; </script> <div style="font-size: {size}; color: {color};">Styled Text</div> -> Option B

4. Quick Check:

   export let with default + use in template = correct [OK]

Hint: Use export let with defaults and reference props in template [OK]

Common Mistakes:

• Not exporting props
• Using const instead of let for props
• Trying to assign defaults after declaration