ullas kunder

Designer & Developer

Named and default exports


The Joy of Imports and Exports in JavaScript

Welcome to the whimsical world of JavaScript exports and imports! 🚀 Today, we embark on a delightful journey to unravel the secrets of named and default exports, and we'll sprinkle in some tips on the best practices that make your code sing!

Once Upon a Time in the Export Kingdom

🌈 Named Exports: A Symphony of Harmony

In the magical land of JavaScript, named exports are like the individual musicians in an orchestra. Each module can export multiple values, functions, or objects, and they all get a chance to shine!

// magic.js
export const spellBook = ['Abracadabra', 'Wingardium Leviosa'];

export function castSpell(spell) {
  console.log(`Casting ${spell}! ✨`);
}

export const potionIngredients = {
  eyeOfNewt: 3,
  unicornHair: 1,
};

Behold! The magic.js module has bestowed upon us three marvelous exports: spellBook, castSpell, and potionIngredients. Now, other modules can import these enchanting elements and bask in the magic!

// wizard.js
import { spellBook, castSpell, potionIngredients } from './magic';

console.log(spellBook); // ['Abracadabra', 'Wingardium Leviosa']
castSpell('Expelliarmus'); // Casting Expelliarmus! ✨
console.log(potionIngredients); // { eyeOfNewt: 3, unicornHair: 1 }

🚀 Default Exports: The Star of the Show

In our magical symphony, the default export is the soloist, the star of the show! Only one value can be the default export in a module, and it doesn't need a fancy name when imported.

// wand.js
const wand = 'Elder Wand';
export default wand;

Prepare to be amazed! The wand.js module has a single, dazzling export: the Elder Wand. Let's bring this mystical artifact into another module's spotlight!

// sorcerer.js
import wand from './wand';

console.log(`The sorcerer wields the mighty ${wand}! 🪄`);

Choosing the Best Spell: Default vs. Named

🌟 Default Export: The Chosen One

Use default exports when there's a clear protagonist in your module. It simplifies imports and allows you to pick the "main character" of your module.

// Only one export in wand.js
export default wand;

🌈 Named Exports: The Ensemble Cast

Named exports shine when your module has multiple important entities to offer. It's like creating a team of heroes, each with their own strengths.

// Multiple exports in magic.js
export const spellBook = ['Abracadabra', 'Wingardium Leviosa'];
export function castSpell(spell) {
  console.log(`Casting ${spell}! ✨`);
}
export const potionIngredients = { eyeOfNewt: 3, unicornHair: 1 };

The Grand Finale: Importing Magic

🚀 The Full Ensemble: Named Imports

To harness the full power of named exports, import them by name. It's like inviting specific wizards to your magical gathering.

// wizard.js
import { spellBook, castSpell, potionIngredients } from './magic';

🌟 The Solo Act: Default Import

For default exports, a simple import statement is all you need. It's elegant, straightforward, and lets the star shine solo.

// sorcerer.js
import wand from './wand';

The Magical Encore: Best Practices

  1. Consistency is Key: Whether you choose named or default exports, stick to a consistent style across your project. A harmonious codebase is a joy to maintain.

  2. Mindful Naming: Give meaningful names to your exports. Make your code a delightful read, like a well-crafted spell.

  3. Organize the Orchestra: Group related exports in a module. A tidy module is a happy module.

  4. Default for Simplicity: If a module has a clear protagonist, embrace the default export. It makes imports clean and straightforward.

  5. Named for Flexibility: When your module features a diverse set of entities, let them shine as named exports. It's like creating a magical team!

And there you have it, dear reader! The magical world of named and default exports in JavaScript. May your code be enchanting, your imports be seamless, and your JavaScript adventures be full of joy and whimsy! 🌟🪄