Folder structure best practices in React - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import a component from the correct folder.

React

import Header from './[1]/Header';

Drag options to blanks, or click blank then click option'

Ahooks

Bcomponents

Cassets

Dutils

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'utils' or 'hooks' folder for components.

Importing from 'assets' which is for images or styles.

The components folder is the best place to keep React components like Header.

2fill in blank

medium

Complete the code to export a component as default from its file.

React

export default [1];

Drag options to blanks, or click blank then click option'

AReact

BuseEffect

CHeader

Dindex

Attempts:

3 left

💡 Hint

Common Mistakes

Exporting React or hooks instead of the component.

Using 'index' which is usually a file name, not a component.

The component name Header should be exported as default to be imported elsewhere easily.

3fill in blank

hard

Fix the error in the import statement to follow folder structure best practices.

React

import [1] from '../[1]/utils';

Drag options to blanks, or click blank then click option'

Ahooks

Bcomponents

Cassets

Dhelpers

Attempts:

3 left

💡 Hint

Common Mistakes

Importing utils from components folder.

Using assets folder for code imports.

The helpers or utils folder is the right place for utility functions, not components or assets.

4fill in blank

hard

Fill both blanks to create a folder structure for a feature with components and hooks.

React

src/[1]/[2]/useFeatureHook.js

Drag options to blanks, or click blank then click option'

Afeatures

Bcomponents

Chooks

Dutils

Attempts:

3 left

💡 Hint

Common Mistakes

Placing hooks directly under components folder.

Using utils folder for feature hooks.

Feature-specific hooks go inside the hooks folder within the features folder.

5fill in blank

hard

Fill all three blanks to create an index file exporting components from a folder.

React

export { default as [1] } from './[2]';
export { default as [3] } from './[3]';

Drag options to blanks, or click blank then click option'

AHeader

CFooter

DInput

Attempts:

3 left

💡 Hint

Common Mistakes

Mismatching export names and paths.

Exporting components not present in the folder.

The index file exports components by name and path. Here, Header and Footer are exported correctly.

Practice

1. What is the main reason to organize React files into folders like components, pages, and hooks?

easy

A. To make the app run faster

B. To reduce the file size of the app

C. To keep the project easy to understand and maintain

D. To avoid using React hooks

Solution

1. Step 1: Understand folder organization purpose

   Folders like components and hooks group related files by their role.

2. Step 2: Recognize benefits of clear structure

   This grouping makes the project easier to read and maintain for developers.

3. Final Answer:

   To keep the project easy to understand and maintain -> Option C

4. Quick Check:

   Folder organization = easier maintenance [OK]

Hint: Folders group related files for clarity and ease [OK]

Common Mistakes:

• Thinking folder structure affects app speed
• Confusing file size with organization
• Believing hooks folder is optional for React hooks

2. Which of the following is the correct way to organize a React project folder for components?

easy

A. Put all components in a single components folder

B. Scatter components randomly in the root folder

C. Put components inside the public folder

D. Put components inside the node_modules folder

Solution

1. Step 1: Identify standard folder for components

   React projects usually keep components in a dedicated components folder.

2. Step 2: Avoid incorrect placements

   Components should not be in public or node_modules folders, which serve other purposes.

3. Final Answer:

   Put all components in a single components folder -> Option A

4. Quick Check:

   Components folder = centralized components [OK]

Hint: Keep components together in one folder [OK]

Common Mistakes:

• Placing components in public folder
• Scattering components without structure
• Modifying node_modules folder

3. Given this folder structure:

src/
  components/
    Button.jsx
  hooks/
    useToggle.js
  pages/
    Home.jsx

Which file would you expect to find the custom React hook?

medium

A. src/components/Button.jsx

B. src/pages/Home.jsx

C. src/index.js

D. src/hooks/useToggle.js

Solution

1. Step 1: Understand folder naming conventions

   Custom hooks are usually placed in the hooks folder.

2. Step 2: Match file to folder purpose

   The file useToggle.js inside hooks matches the custom hook naming pattern.

3. Final Answer:

   src/hooks/useToggle.js -> Option D

4. Quick Check:

   Custom hooks in hooks folder = useToggle.js [OK]

Hint: Hooks go in the hooks folder [OK]

Common Mistakes:

• Looking for hooks in components folder
• Confusing pages folder with hooks
• Assuming index.js contains hooks

4. You see this folder structure in a React project:

src/
  components/
    Header.jsx
  utils/
    helpers.js
  Header.jsx

What is the main problem here?

medium

A. Having a utils folder is not recommended

B. Duplicate Header.jsx file in root and components folder causes confusion

C. Components should be inside utils folder

D. Files should not have .jsx extension

Solution

1. Step 1: Identify duplicate file names

   There are two Header.jsx files: one in components and one in root.

2. Step 2: Understand confusion caused by duplicates

   This duplication can confuse developers and cause import errors.

3. Final Answer:

   Duplicate Header.jsx file in root and components folder causes confusion -> Option B

4. Quick Check:

   Duplicate filenames = confusion [OK]

Hint: Avoid duplicate filenames in different folders [OK]

Common Mistakes:

• Thinking utils folder is bad practice
• Believing components belong in utils
• Ignoring file extensions importance

5. You are building a large React app. Which folder structure best supports growth and easy maintenance?

hard

A. Organize by feature: each feature folder contains components, hooks, and styles

B. Put all files in one big folder to avoid complexity

C. Separate files only by file type, ignoring features

D. Keep all components and hooks mixed in the root folder

Solution

1. Step 1: Understand feature-based organization

   Grouping by feature means each feature folder holds all related files, making it easier to find and update.

2. Step 2: Compare with other structures

   Flat or type-only folders become hard to manage as app grows, causing confusion.

3. Final Answer:

   Organize by feature: each feature folder contains components, hooks, and styles -> Option A

4. Quick Check:

   Feature folders = scalable and maintainable [OK]

Hint: Group by feature for scalable projects [OK]

Common Mistakes:

• Using one big folder causes clutter
• Separating only by file type slows feature updates
• Mixing all files in root is confusing