DEV Community

Cover image for Import and Rename Named Exports

Import and Rename Named Exports

chantastic profile image Michael Chan Originally published at on ・2 min read

JavaScript Modules have a syntax for remaning named exports, at import.

import { exportedName as localName } from "";
Enter fullscreen mode Exit fullscreen mode

I think about this as "given name" and "nickname". Michael Chan is the name my creators gave me but — on this site — I go by chantastic.

import { michaelChan as chantastic } from "./michael-chan.mjs";
Enter fullscreen mode Exit fullscreen mode

This is one of two tools we have for avoiding naming collisions between modules.

Rename named exports to avoid a collision #

In my last post — Import Named Exports — we imported two functions from the string-utils module: hype and chant.

import { hype, chant } from "./string-utils.mjs";
Enter fullscreen mode Exit fullscreen mode

What if the modules we're working in already has a hype function? Are we stuck stuck? Do we have to refactor our code to consider the new module?


We use the as keyword to rename named exports locally.

- import { hype, chant } from "./string-utils.mjs";+ import {+ hype as hypeText,+ chant+ } from "./string-utils.mjs";
Enter fullscreen mode Exit fullscreen mode

With as, we have full control of the module we're working in.

We can assign named exports to any free, local identifier.

My take #

The as keyword gives us a way to avoid naming collisions, or use a name that's more contextually accurate. This is great for working with modules in a codebase and the larger npm ecosystem.

However, I find this to be a less ideal form collision avoidance than importing all of a module's contents into a single variable.

But we'll cover that in a future post 😅.

Go pro #

This is part of a course I'm build on modules at

When live, members get access to this and other courses on React.

Join for videos

Discussion (0)

Editor guide