ESM Module Patterns FAQs

Question 1

How does this skill handle Node.js built-in modules?

Accepted Answer

It promotes the use of the 'node:' prefix (e.g., import fs from 'node:fs'), which is the modern standard for identifying built-in modules and avoiding naming conflicts.

Question 2

What is the benefit of named exports over default exports?

Accepted Answer

Named exports are more explicit, provide better IDE autocompletion, and are more reliable for tree-shaking, which results in smaller production bundles.

Question 3

Can I use this skill to convert CommonJS projects?

Accepted Answer

Yes, it provides specific patterns, replacements for globals like __dirname, and configuration settings to successfully migrate from require() to native import/export syntax.

Question 4

Why does this skill require .js extensions in TypeScript imports?

Accepted Answer

Node.js native ESM requires explicit file extensions. Since TypeScript preserves these strings during compilation, using .js ensures the compiled output is valid ESM code that runs natively in Node.js.

Question 5

What are barrel files and does this skill support them?

Accepted Answer

Barrel files are index.ts files used to re-export multiple modules from a single directory. This skill provides patterns for creating clean, maintainable barrel files.

ESM Module Patterns

About

Key Features

Use Cases

ESM Module Patterns

About

Key Features

Use Cases