ES Modules import and export in Node.js - Performance & Optimization

Performance: ES Modules import and export

MEDIUM IMPACT

This concept affects the initial load time and parsing speed of JavaScript modules in the browser or Node.js environment.

Importing only needed functions from a module

Node.js

import { calculate } from './utils.js';
const result = calculate();

Imports only the needed function, enabling tree shaking and smaller bundle size.

📈 Performance Gainreduces bundle size, faster parsing and execution

Importing only needed functions from a module

Node.js

import * as utils from './utils.js';
const result = utils.calculate();

Imports the entire module even if only one function is used, increasing bundle size and load time.

📉 Performance Costadds unnecessary KBs to bundle, blocks parsing longer

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Import entire module with *	N/A	N/A	Increases script parsing time	[X] Bad
Import specific exports statically	N/A	N/A	Smaller script size, faster parsing	[OK] Good
Dynamic import for rarely used code	N/A	N/A	Defers loading, improves initial paint	[OK] Good
Static import of large unused modules	N/A	N/A	Blocks initial load, increases LCP	[X] Bad

Rendering Pipeline

ES Modules are parsed and linked before execution. Static imports allow the browser or Node.js to build a dependency graph and optimize loading. Dynamic imports defer loading until needed, reducing blocking time.

→Parsing

→Script Evaluation

→Network Loading

⚠️ BottleneckNetwork Loading and Parsing of large modules

Core Web Vital Affected

LCP

This concept affects the initial load time and parsing speed of JavaScript modules in the browser or Node.js environment.

Optimization Tips

1Use static named imports to enable tree shaking and reduce bundle size.

2Use dynamic imports to defer loading of rarely used code and improve initial load time.

3Avoid importing entire large modules if only a small part is needed.

Performance Quiz - 3 Questions

What is the main benefit of using static named imports in ES Modules?

A Blocks rendering until all modules load

B Enables tree shaking to reduce bundle size

C Allows importing modules dynamically at runtime

D Automatically caches modules in the browser

DevTools: Network and Performance panels

How to check: Open DevTools, go to Network tab, filter by JS files to see module sizes and load order. Use Performance tab to record page load and check script parsing and execution times.

What to look for: Look for large module files blocking the main thread and long script evaluation times that delay first contentful paint.

Practice

1. What is the main purpose of using export and import in Node.js ES Modules?

easy

A. To create new variables inside a file

B. To run JavaScript code faster in Node.js

C. To convert JavaScript code into another language

D. To share code between different files by exporting and importing parts

Solution

1. Step 1: Understand the role of export

   The export keyword allows parts of a file (like functions or variables) to be shared with other files.

2. Step 2: Understand the role of import

   The import keyword is used to bring those shared parts into another file to use them.

3. Final Answer:

   To share code between different files by exporting and importing parts -> Option D

4. Quick Check:

   Export and import = share code [OK]

Hint: Export shares code, import uses it elsewhere [OK]

Common Mistakes:

• Thinking export/import changes code speed
• Confusing export with variable creation
• Believing export/import converts languages

2. Which of the following is the correct syntax to export a function named greet in an ES Module file?

easy

A. export function greet() {}

B. module.exports = greet;

C. export = greet;

D. exports.greet = function() {}

Solution

1. Step 1: Identify ES Module export syntax

   In ES Modules, use export function functionName() {} to export a function.

2. Step 2: Check other options for CommonJS syntax

   Options B and D use CommonJS style, not ES Modules. export = greet; is invalid syntax.

3. Final Answer:

   export function greet() {} -> Option A

4. Quick Check:

   ES Modules export function = export function [OK]

Hint: Use 'export function' for ES Modules exports [OK]

Common Mistakes:

• Using CommonJS syntax in ES Modules
• Writing invalid export syntax
• Confusing export default with named export

3. Given the following files, what will be logged when running node main.js?

// utils.js
export const value = 5;
export function double(x) { return x * 2; }

// main.js
import { value, double } from './utils.js';
console.log(double(value));

medium

A. 10

B. 5

C. undefined

D. SyntaxError

Solution

1. Step 1: Understand the imports and exports

   The file utils.js exports a constant value = 5 and a function double that multiplies input by 2.

2. Step 2: Trace the code in main.js

   It imports value and double, then calls double(value) which is double(5), returning 10.

3. Final Answer:

   10 -> Option A

4. Quick Check:

   double(5) = 10 [OK]

Hint: Import exports correctly, then call functions with values [OK]

Common Mistakes:

• Forgetting to add .js extension in import
• Confusing export default with named exports
• Expecting value instead of double(value)

4. What is the error in the following code snippet?

// math.js
export function add(a, b) { return a + b; }

// app.js
import { add } from './math';
console.log(add(2, 3));

medium

A. Function add is not exported correctly

B. Cannot import named exports with curly braces

C. Missing file extension in import statement

D. Using CommonJS syntax in ES Modules

Solution

1. Step 1: Check import statement syntax

   The import statement uses import { add } from './math'; but misses the .js extension required in Node.js ES Modules.

2. Step 2: Confirm export syntax is correct

   The function add is correctly exported with export function add(), so no error there.

3. Final Answer:

   Missing file extension in import statement -> Option C

4. Quick Check:

   Node.js ES Modules need file extensions [OK]

Hint: Always include .js extension in ES Module imports [OK]

Common Mistakes:

• Omitting file extensions in import paths
• Confusing CommonJS and ES Module syntax
• Assuming named exports don't use curly braces

5. You have two files:

// data.js
const secret = 'hidden';
export const visible = 'shown';
export default function getSecret() { return secret; }

// index.js
import getSecret, { visible } from './data.js';
console.log(visible);
console.log(getSecret());

What will be the output when running node index.js?

hard

A. SyntaxError due to mixed import syntax

B. shownhidden

C. shownundefined

D. hiddenshown

Solution

1. Step 1: Understand default and named exports

   getSecret is the default export function returning secret. visible is a named export with value 'shown'.

2. Step 2: Analyze import and console.log calls

   import getSecret, { visible } correctly imports default and named exports. Logging visible prints 'shown'. Calling getSecret() returns 'hidden'.

3. Final Answer:

   shown
   hidden -> Option B

4. Quick Check:

   Default + named import works = shown, hidden [OK]

Hint: Default import first, named imports in braces [OK]

Common Mistakes:

• Mixing default and named imports incorrectly
• Expecting secret variable to be exported directly
• Confusing order of import syntax