Re-exporting modules in Typescript - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does re-exporting modules mean in TypeScript?

Re-exporting modules means exporting something from one module again through another module, so you can gather exports in one place for easier imports.

beginner

How do you re-export all exports from another module?

Use export * from './module'; to re-export everything that the other module exports.

beginner

How can you re-export a specific export from another module?

Use export { name } from './module'; to re-export only the named export.

intermediate

Why use re-exporting in a project?

It helps organize code by creating a single entry point to import many things, making imports cleaner and easier to manage.

intermediate

Can you rename exports while re-exporting? How?

Yes, you can rename exports using export { originalName as newName } from './module';.

Which syntax re-exports all exports from a module named 'utils'?

A export * from './utils';

B import * from './utils';

C export { * } from './utils';

D import { * } from './utils';

The correct syntax to re-export all exports is export * from './utils';.

How do you re-export only the 'calculate' function from 'math.ts'?

A export * from './math';

B import { calculate } from './math';

C export { calculate } from './math';

D export calculate from './math';

Use export { calculate } from './math'; to re-export only the 'calculate' function.

What is the benefit of re-exporting modules?

A To rename files automatically

B To make code run faster

C To avoid using imports

D To create a single place to import many exports

Re-exporting helps organize imports by gathering exports in one place.

Can you rename an export while re-exporting it?

A Yes, using 'as' keyword

B No, renaming is not allowed

C Only if you import first

D Only for default exports

You can rename exports using export { originalName as newName } from './module';.

Which statement is true about re-exporting?

A It only works with default exports

B It allows combining exports from multiple modules into one

C It disables tree shaking

D It duplicates code in the output

Re-exporting lets you combine exports from different modules into a single module.

Explain how re-exporting modules works and why it is useful in TypeScript projects.

Think about how you can collect exports from many files into one place.

Describe the difference between re-exporting all exports and re-exporting specific exports from a module.

Consider when you want everything vs. only some parts.

Practice

1. What is the main purpose of re-exporting modules in TypeScript?

easy

A. To organize and simplify imports by sharing exports from one place

B. To create new variables inside a module

C. To run code automatically when a module loads

D. To prevent modules from being imported multiple times

Solution

1. Step 1: Understand re-exporting concept

   Re-exporting means exporting items from one module through another to simplify imports.

2. Step 2: Identify the main benefit

   This helps organize code and makes importing easier by centralizing exports.

3. Final Answer:

   To organize and simplify imports by sharing exports from one place -> Option A

4. Quick Check:

   Re-exporting = Simplify imports [OK]

Hint: Re-exporting centralizes exports for easier imports [OK]

Common Mistakes:

• Thinking re-exporting creates new variables
• Confusing re-exporting with running code
• Believing it prevents multiple imports

2. Which of the following is the correct syntax to re-export everything from a module named utils.ts?

easy

A. export all from './utils';

B. export * from './utils';

C. import * from './utils';

D. re-export * from './utils';

Solution

1. Step 1: Recall correct re-export syntax

   To re-export all exports from a module, use export * from 'module';.

2. Step 2: Match syntax with options

   export * from './utils'; matches the correct syntax exactly.

3. Final Answer:

   export * from './utils'; -> Option B

4. Quick Check:

   Re-export all = export * from [OK]

Hint: Use 'export * from' to re-export all [OK]

Common Mistakes:

• Using 'import * from' instead of 'export * from'
• Writing 'export all from' which is invalid
• Using 're-export' keyword which doesn't exist

3. Given the following files, what will be the output of console.log in main.ts?

// mathUtils.ts
export const pi = 3.14;
export const e = 2.71;

// index.ts
export { pi } from './mathUtils';

// main.ts
import { pi, e } from './index';
console.log(pi, e);

medium

A. 3.14 2.71

B. 3.14 undefined

C. undefined 2.71

D. Error: 'e' is not exported from './index'

Solution

1. Step 1: Analyze exports in index.ts

   Only pi is re-exported from mathUtils.ts. e is not exported.

2. Step 2: Check import in main.ts

   Trying to import both pi and e from index.ts causes an error because e is missing.

3. Final Answer:

   Error: 'e' is not exported from './index' -> Option D

4. Quick Check:

   Missing export causes import error [OK]

Hint: Only re-exported items can be imported [OK]

Common Mistakes:

• Assuming all original exports are re-exported
• Expecting undefined instead of error
• Ignoring missing export errors

4. Identify the error in this re-exporting code snippet:

// helpers.ts
export function greet() { return 'Hello'; }

// index.ts
export { greet } from './helpers';
export { greet } from './helpers';

medium

A. Duplicate export of 'greet' causes a syntax error

B. Missing semicolon after export statements

C. Cannot re-export functions, only variables

D. No error, code works fine

Solution

1. Step 1: Check for duplicate exports

   The code exports greet twice from the same module, causing a duplicate export.

2. Step 2: Understand TypeScript rules

   Duplicate exports of the same name cause syntax errors because they conflict.

3. Final Answer:

   Duplicate export of 'greet' causes a syntax error -> Option A

4. Quick Check:

   Duplicate exports = syntax error [OK]

Hint: Avoid exporting same name twice in one module [OK]

Common Mistakes:

• Ignoring duplicate export errors
• Thinking missing semicolons cause error
• Believing functions can't be re-exported

5. You have two modules: colors.ts exporting red and blue, and shapes.ts exporting circle and square. How can you create a single index.ts that re-exports only red and circle with new names primaryRed and roundShape?

hard

A. import { red, circle } from './colors'; export { red as primaryRed, circle as roundShape };

B. export * from './colors'; export * from './shapes';

C. export { red as primaryRed } from './colors'; export { circle as roundShape } from './shapes';

D. export { primaryRed, roundShape } from './colors', './shapes';

Solution

1. Step 1: Understand renaming during re-export

   You can rename exports using export { originalName as newName } syntax.

2. Step 2: Apply to given modules

   Re-export red as primaryRed from colors.ts and circle as roundShape from shapes.ts.

3. Final Answer:

   export { red as primaryRed } from './colors'; export { circle as roundShape } from './shapes'; -> Option C

4. Quick Check:

   Rename exports with 'as' keyword [OK]

Hint: Use 'export { oldName as newName }' to rename exports [OK]

Common Mistakes:

• Using import instead of export for re-exporting
• Trying to export multiple modules in one statement incorrectly
• Not renaming exports properly