Component naming conventions in Svelte - Step-by-Step Execution

Concept Flow - Component naming conventions

Start: Create Component File

↓

Name Component File

↓

Use PascalCase Naming

↓

Export Component

↓

Import Component Using Same Name

↓

Use Component in Parent

↓

Render with Consistent Naming

↓

End

This flow shows how to name and use Svelte components consistently using PascalCase for clarity and convention.

Execution Sample

Svelte

/* File: UserProfile.svelte */
<script>
  export let name;
</script>
<h1>{name}</h1>

A simple Svelte component named UserProfile that displays a name passed as a prop.

Execution Table

Step	Action	File/Component Name	Naming Convention	Result
1	Create component file	UserProfile.svelte	PascalCase	File created with PascalCase name
2	Write component code	UserProfile.svelte	PascalCase	Component exports 'name' prop and renders it
3	Import component in parent	App.svelte	PascalCase	Import UserProfile from './UserProfile.svelte'
4	Use component in parent	App.svelte	PascalCase	<UserProfile name="Alice" /> renders correctly
5	Render output	Browser	PascalCase	Displays heading with 'Alice'
6	Exit	-	-	Component naming consistent and renders as expected

💡 Component naming follows PascalCase, ensuring clarity and proper import/use in Svelte.

Variable Tracker

Variable	Start	After Step 2	After Step 4	Final
name	undefined	"Alice"	"Alice"	"Alice"

Key Moments - 2 Insights

Why do we use PascalCase for component file names and usage?

PascalCase helps distinguish components from regular HTML tags and files, making imports and usage clear, as shown in execution_table steps 1 and 3.

What happens if the component file name and import name do not match in case?

Svelte and many systems are case-sensitive, so mismatched casing can cause import errors or components not rendering, as implied in step 3.

Visual Quiz - 3 Questions

Look at the execution table, what is the component file name created at step 1?

A userProfile.svelte

B UserProfile.svelte

C userprofile.svelte

D user_profile.svelte

💡 Hint

Check the 'File/Component Name' column at step 1 in the execution_table.

At which step is the component imported into the parent file?

A Step 3

B Step 2

C Step 4

D Step 5

💡 Hint

Look for the 'Import component in parent' action in the execution_table.

If the component was named 'userprofile.svelte' instead of 'UserProfile.svelte', what issue might occur?

A No issue, it works the same

B Component renders twice

C Import errors due to case sensitivity

D Component props stop working

💡 Hint

Refer to key_moments about case sensitivity and naming conventions.

Concept Snapshot

Component Naming Conventions in Svelte:
- Use PascalCase for component file names (e.g., UserProfile.svelte)
- Export props with 'export let'
- Import components using the same PascalCase name
- Use components in markup with PascalCase tags
- Consistent naming avoids import errors and improves clarity

Full Transcript

This lesson shows how to name Svelte components using PascalCase. We start by creating a component file named UserProfile.svelte. Inside, we export a prop called 'name' and display it in an h1 tag. We then import this component into a parent file using the same PascalCase name. Using the component in the parent with <UserProfile name="Alice" /> renders the heading with 'Alice'. Following PascalCase naming helps avoid errors and keeps code clear. Case sensitivity matters for imports and usage. This visual trace helps beginners see each step from file creation to rendering output.

Practice

1. Which naming style is recommended for Svelte component files and their names?

easy

A. kebab-case (e.g., my-component.svelte)

B. snake_case (e.g., my_component.svelte)

C. PascalCase (e.g., MyComponent.svelte)

D. all lowercase (e.g., mycomponent.svelte)

Solution

1. Step 1: Understand Svelte naming conventions

   Svelte recommends using PascalCase for component names and file names to clearly distinguish components from regular HTML tags.

2. Step 2: Compare naming styles

   PascalCase capitalizes the first letter of each word, making component names easy to read and recognize, unlike snake_case, kebab-case, or all lowercase.

3. Final Answer:

   PascalCase (e.g., MyComponent.svelte) -> Option C

4. Quick Check:

   Component names use PascalCase [OK]

Hint: Always capitalize each word in component names [OK]

Common Mistakes:

• Using kebab-case which is for HTML attributes
• Using snake_case which is uncommon in Svelte
• Using all lowercase which looks like regular HTML tags

2. Which of the following is a correct Svelte component file name?

easy

A. userprofile.svelte

B. user_profile.svelte

C. user-profile.svelte

D. UserProfile.svelte

Solution

1. Step 1: Check file naming rules for Svelte components

   Svelte components should be named using PascalCase to clearly identify them as components.

2. Step 2: Identify the PascalCase option

   Among the options, only UserProfile.svelte uses PascalCase correctly.

3. Final Answer:

   UserProfile.svelte -> Option D

4. Quick Check:

   PascalCase file name = UserProfile.svelte [OK]

Hint: Look for capital letters starting each word in the file name [OK]

Common Mistakes:

• Using lowercase or underscores instead of PascalCase
• Confusing kebab-case with component file naming
• Mixing styles inconsistently

3. Given the component file named LoginForm.svelte, which is the correct way to import and use it in another Svelte file?

medium

A. import LoginForm from './LoginForm.svelte';
<LoginForm />

B. import loginform from './LoginForm.svelte';
<LoginForm />

C. import LoginForm from './loginform.svelte';
<loginForm />

D. import loginForm from './LoginForm.svelte';
<loginForm />

Solution

1. Step 1: Match import name with component file name

   The import name should match the PascalCase component file name exactly, including capitalization.

2. Step 2: Use the imported component with correct casing

   In Svelte, component tags must start with uppercase letters matching the import name.

3. Final Answer:

   import LoginForm from './LoginForm.svelte'; <LoginForm /> -> Option A

4. Quick Check:

   Import and usage use PascalCase consistently [OK]

Hint: Import and use components with exact PascalCase names [OK]

Common Mistakes:

• Importing with lowercase names
• Using lowercase component tags
• Mismatching import path casing

4. What is wrong with this Svelte component file name and usage?

Filename: userprofile.svelte
Usage: <UserProfile />

medium

A. The filename should be PascalCase to match the component usage.

B. The component tag should be lowercase to match the filename.

C. The filename should use kebab-case instead of lowercase.

D. There is no issue; this is valid Svelte usage.

Solution

1. Step 1: Check filename casing

   The filename userprofile.svelte is all lowercase, which is not recommended for Svelte components.

2. Step 2: Check component usage casing

   The usage <UserProfile /> uses PascalCase, which expects the filename to match in PascalCase.

3. Final Answer:

   The filename should be PascalCase to match the component usage. -> Option A

4. Quick Check:

   Filename and usage casing must match PascalCase [OK]

Hint: Filename and usage must both be PascalCase [OK]

Common Mistakes:

• Using lowercase filenames with PascalCase tags
• Assuming kebab-case is valid for component files
• Ignoring case sensitivity in imports

5. You have two components: NavBar.svelte and navBar.svelte. What problem might this cause in a Svelte project on a case-sensitive file system?

hard

A. The project will fail to compile due to duplicate component names.

B. Only one component will be recognized; the other will be ignored or cause confusion.

C. Both components will work fine since Svelte ignores filename case.

D. The components will merge automatically into one component.

Solution

1. Step 1: Understand case sensitivity in file systems

   On case-sensitive systems (like Linux), NavBar.svelte and navBar.svelte are different files but can cause confusion in imports.

2. Step 2: Recognize Svelte import and usage issues

   Importing components with inconsistent casing can cause one component to be ignored or cause runtime errors because Svelte expects consistent PascalCase naming.

3. Final Answer:

   Only one component will be recognized; the other will be ignored or cause confusion. -> Option B

4. Quick Check:

   Case-sensitive filenames cause import confusion [OK]

Hint: Avoid similar names differing only by case [OK]

Common Mistakes:

• Assuming case-insensitive systems behave the same everywhere
• Using inconsistent casing in imports and filenames
• Expecting automatic merging of components