A module cannot have multiple default exports Error [Fixed] | bobbyhadz (2024)

A module cannot have multiple default exports Error [Fixed]

# A module cannot have multiple default exports Error

The error "A module cannot have multiple default exports" occurs for 2reasons - having more than 1 default export in a file or having a glitch in yourIDE.

To solve the error, replace the second default export with a named export andreload your IDE if necessary.

Here is an example of how the error occurs.

Copied!
const a = 'bobby';// ⛔️ Error: A module cannot have multiple default exports.ts(2528)export default a; // 👈️ default exportconst b = 'hadz';export default b; // 👈️ default export

We can only have a single default export per file, so we have to move the seconddefault export to another file or convert it to a named export.

# Convert the second default export to a named export

Here is how you would convert the second export to a named export.

Copied!
const a = 'bobby';// 👇️ default exportexport default a;// 👇️ named exportexport const b = 'hadz';

Here is how you would import the variables into another file.

Copied!
// 👇️ default and named importimport a, { b } from './index';console.log(a); // 👉️ "bobby"console.log(b); // 👉️ "hadz"

We had to wrap the named import in curly braces. You can have only one defaultexport per file, but you can have as many named exports as necessary.

If you don't want to use a named export, move the second variable to aseparate file and make sure to stick to a maximum of 1 default export perfile.

You also don't have to think about which members are exported with a defaultor a named export.

# Only using named exports

Here is how you would convert the example above to use only named exports andimports.

Copied!
// 👇️ named exportexport const a = 'bobby';// 👇️ named exportexport const b = 'hadz';

And here is how you would import the named exports.

Copied!
// 👇️ named importsimport { a, b } from './index';console.log(a); // 👉️ "bobby"console.log(b); // 👉️ "hadz"

This is much better than having to remember which values you exported asdefault, and which you exported as named.

The less you have to think about implementation details, the more you can focuson domain-specific logic in your application.

# Restart your IDE

If none of the suggestions helped and you don't have multiple default exports ina single file, restart your code editor and your development server.

# Additional Resources

You can learn more about the related topics by checking out the followingtutorials:

• Module has no default export Error in TypeScript [Solved]
• Module can only be default-imported using esModuleInterop flag
• Module has no exported member error in TypeScript [Solved]
• ReferenceError: exports is not defined in TypeScript [Fixed]