postFeaturedDD

Before ES6 came into play, we used multiple script tags in a single HTML file to import different JavaScript files like this:
<pre><code class="lang-html">&lt;script type="text/javascript" src="home.js"&gt;&lt;/script&gt;
&lt;script type="text/javascript" src="profile.js"&gt;&lt;/script&gt;
&lt;script type="text/javascript" src="user.js"&gt;&lt;/script&gt;
</code></pre>
So, if we had a variable with the same name in different JavaScript files, it would create a naming conflict and the value you were expecting would not be the actual value you got.
ES6 has fixed this issue with the concept of modules.
Every JavaScript file we write in ES6 is known as a module. The variables and functions we declare in each file are not available to other files until we specifically export them from that file and import them into another file.
So the functions and variables defined in the file are private to each file and can’t be accessed outside the file until we export them.
There are two types of exports:
<ul>
<li>Named Exports: There can be multiple named exports in a single file</li>
<li>Default Exports: There can be only one default export in a single file</li>
</ul>
<h2 id="named-exports-in-javascript">Named Exports in JavaScript</h2>
To export a single value as a named export, we export it like this:
<pre><code class="lang-js">export const temp = "This is some dummy text";
</code></pre>
If we have multiple things to export, we can write an export statement on a separate line instead of in front of a variable declaration. We specify the things to export in curly brackets.
<pre><code class="lang-js">const temp1 = "This is some dummy text1";
const temp2 = "This is some dummy text2";

export { temp1, temp2 };
</code></pre>
Note that the export syntax is not an object literal syntax. So in ES6, to export something we can't use key-value pairs like this:
<pre><code class="lang-js"> // This is invalid syntax of export in ES6

export { key1: value1, key2: value2 }
</code></pre>
To import the things we exported as a named export, we use the following syntax:
<pre><code class="lang-js">import { temp1, temp2 } from './filename';
</code></pre>
Note that while importing something from the file, we don't need to add the <code>.js</code> extension to the filename as it's considered by default.
<pre><code class="lang-js">// import from functions.js file from current directory 
import { temp1, temp2 } from './functions';

// import from functions.js file from parent of current directory
import { temp1 } from '../functions';
</code></pre>
Here's a <a target="_blank" href="https://codesandbox.io/s/hardcore-pond-q4cjx">Code Sandbox demo</a>.
One thing to note is that the name used while exporting has to match the name we use while importing.
So if you are exporting as:
<pre><code class="lang-js">// constants.js
export const PI = 3.14159;
</code></pre>
then while importing you have to use the same name used while exporting:
<pre><code class="lang-js">import { PI } from './constants';
</code></pre>
You can't use any other name like this:
<pre><code class="lang-js">import { PiValue } from './constants'; // This will throw an error
</code></pre>
But if you already have the variable with the same name as the exported variable, you can use the renaming syntax while importing like this:
<pre><code class="lang-js">import { PI as PIValue } from './constants';
</code></pre>
Here we have renamed <code>PI</code> to <code>PIValue</code> and so we can't use the <code>PI</code> variable name now. Instead, we have to use the <code>PIValue</code> variable to get the exported value of PI.
We can also use the renaming syntax at the time of exporting:
<pre><code class="lang-js">// constants.js
const PI = 3.14159; 

export { PI as PIValue };
</code></pre>
then while importing we have to use <code>PIValue</code> like this:
<pre><code class="lang-js">import { PIValue } from './constants';
</code></pre>
To export something as a named export, we have to declare it first.
<pre><code class="lang-js">export 'hello'; // this will result in error
export const greeting = 'hello'; // this will work
export { name: 'David' }; // This will result in error
export const object = { name: 'David' }; // This will work
</code></pre>
The order in which we import the multiple named exports is not important.
Take a look at the below <code>validations.js</code> file:
<pre><code class="lang-js">// utils/validations.js

const isValidEmail = function(email) {
 if (/^[^@ ]+@[^@ ]+\.[^@ \.]{2,}$/.test(email)) {
 return "email is valid";
 } else {
 return "email is invalid";
 }
};

const isValidPhone = function(phone) {
 if (/^[\$]\d{3}[\$]\s\d{3}-\d{4}$/.test(phone)) {
 return "phone number is valid";
 } else {
 return "phone number is invalid";
 }
};

function isEmpty(value) { 
 if (/^\s*$/.test(value)) {
 return "string is empty or contains only spaces";
 } else {
 return "string is not empty and does not contain spaces";
 } 
}

export { isValidEmail, isValidPhone, isEmpty };
</code></pre>
and in <code>index.js</code> we use these functions as shown below:
<pre><code class="lang-js">// index.js
import { isEmpty, isValidEmail } from "./utils/validations";

console.log("isEmpty:", isEmpty("abcd")); // isEmpty: string is not empty and does not contain spaces

console.log("isValidEmail:", isValidEmail("abc@11gmail.com")); // isValidEmail: email is valid

console.log("isValidEmail:", isValidEmail("ab@c@11gmail.com")); // isValidEmail: email is invalid
</code></pre>
Here's a <a target="_blank" href="https://codesandbox.io/s/youthful-flower-xesus">Code Sandbox demo</a>.
As you can see, we can import only the required exported things and in any order, so we don’t need to check in what order we exported in another file. That’s the beauty of named exports.
<h2 id="default-exports-in-javascript">Default Exports in JavaScript</h2>
As I said earlier, there can be at most one default export in a single file.
You can, however, combine multiple named exports and one default export in a single file.
 To declare a default export we add the default keyword in front of the export keyword like this:
<pre><code class="lang-js">//constants.js
const name = 'David'; 

export default name;
</code></pre>
To import the default export we don’t add the curly brackets as we did in the named export like this:
<pre><code class="lang-js">import name from './constants';
</code></pre>
If we have multiple named exports and one default export like this:
<pre><code class="lang-js">// constants.js
export const PI = 3.14159; 
export const AGE = 30;

const NAME = "David";

export default NAME;
</code></pre>
then to import everything on a single line we need to use the default exported variable before the curly bracket only.
<pre><code class="lang-js">// NAME is default export and PI and AGE are named exports here

import NAME, { PI, AGE } from './constants';
</code></pre>
One specialty of default export is that we can change the name of the exported variable while importing:
<pre><code class="lang-js">// constants.js
const AGE = 30;

export default AGE;
</code></pre>
And in another file, we can use another name while importing
<pre><code>import myAge from ‘./constants’; 

console.log(myAge); // 30
</code></pre>Here, we have changed the name of the default exported variable from <code>AGE</code> to <code>myAge</code>.
This works because there can be only one default export so you can name it whatever you want.
Another thing to note about default export is that the export default keyword cannot come before variable declaration like this:
<pre><code class="lang-js">// constants.js
export default const AGE = 30; // This is an error and will not work
</code></pre>
so we have to use the export default keyword on a separate line like this:
<pre><code class="lang-js">// constants.js 
const AGE = 30; 

export default AGE;
</code></pre>
We can, however, export default without declaring the variable like this:
<pre><code class="lang-js">//constants.js
export default {
 name: "Billy",
 age: 40
};
</code></pre>
and in another file use it like this:
<pre><code class="lang-js">import user from './constants';

console.log(user.name); // Billy 
console.log(user.age); // 40
</code></pre>
There is another way of importing all the variables exported in a file using the following syntax:
<pre><code class="lang-js">import * as constants from './constants';
</code></pre>
Here, we are importing all the named and default exports we have in <code>constants.js</code> and store in the <code>constants</code> variable. So, <code>constants</code> will become an object now.
<pre><code class="lang-js">// constants.js
export const USERNAME = "David";
export default {
 name: "Billy",
 age: 40
};
</code></pre>
And in another file, we use it as below:
<pre><code class="lang-js">// test.js
import * as constants from './constants';

console.log(constants.USERNAME); // David
console.log(constants.default); // { name: "Billy", age: 40 }
console.log(constants.default.age); // 40
</code></pre>
Here's a <a target="_blank" href="https://codesandbox.io/s/green-hill-dj43b">Code Sandbox demo</a>. 
If you don’t want to export on separate lines for default and named exports, you can combine it as shown below:
<pre><code class="lang-js">// constants.js
const PI = 3.14159; 
const AGE = 30;
const USERNAME = "David";
const USER = {
 name: "Billy",
 age: 40 
};

export { PI, AGE, USERNAME, USER as default };
</code></pre>
Here, we are exporting <code>USER</code> as the default export and others as named exports.
In another file, you can use it like this:
<pre><code class="lang-js">import USER, { PI, AGE, USERNAME } from "./constants";
</code></pre>
Here's a <a target="_blank" href="https://codesandbox.io/s/eloquent-northcutt-7btp1">Code Sandbox demo</a>. 
<h3 id="conclusion">Conclusion</h3>
<ul>
<li>In ES6, data declared in one file is not accessible to another file until it is exported from that file and imported into another file.</li>
<li>If we have a single thing in a file to export like class declaration, we use default export otherwise we use named export. We can also combine default and named exports in a single file.</li>
</ul>
<h3 id="thanks-for-reading">Thanks for reading!</h3>
Check out my recently published <a target="_blank" href="https://master-redux.yogeshchavan.dev/">Mastering Redux</a> course.
In this course, you will build 3 apps along with food ordering app and you'll learn:
<ul>
<li>Basic and advanced Redux</li>
<li>How to manage the complex state of array and objects</li>
<li>How to use multiple reducers to manage complex redux state</li>
<li>How to debug Redux application</li>
<li>How to use Redux in React using react-redux library to make your app reactive.</li>
<li>How to use redux-thunk library to handle async API calls and much more</li>
</ul>
and then finally we'll build a complete <a target="_blank" href="https://www.youtube.com/watch?v=2zaPDfCKAvM">food ordering app</a> from scratch with stripe integration for accepting payments and deploy it to the production.
<a target="_blank" href="https://bit.ly/3w0DGum"><img src="https://gist.github.com/myogeshchavan97/98ae4f4ead57fde8d47fcf7641220b72/raw/c3e4265df4396d639a7938a83bffd570130483b1/banner.jpg" /></a>
Want to stay up to date with regular content regarding JavaScript, React, Node.js? <a target="_blank" href="https://www.linkedin.com/in/yogesh-chavan97/">Follow me on LinkedIn</a>.
<a target="_blank" href="https://www.buymeacoffee.com/myogeshchavan97"><img src="https://cdn.buymeacoffee.com/buttons/default-yellow.png" /></a>

Before ES6 came into play, we used multiple script tags in a single HTML file to import different JavaScript files like this:

```html
<script type="text/javascript" src="home.js"></script>
<script type="text/javascript" src="profile.js"></script>
<script type="text/javascript" src="user.js"></script>
```

So, if we had a variable with the same name in different JavaScript files, it would create a naming conflict and the value you were expecting would not be the actual value you got.

ES6 has fixed this issue with the concept of modules.

Every JavaScript file we write in ES6 is known as a module. The variables and functions we declare in each file are not available to other files until we specifically export them from that file and import them into another file.

So the functions and variables defined in the file are private to each file and can’t be accessed outside the file until we export them.

There are two types of exports:

* Named Exports: There can be multiple named exports in a single file
* Default Exports: There can be only one default export in a single file

## Named Exports in JavaScript

To export a single value as a named export, we export it like this:

```js
export const temp = "This is some dummy text";
```

If we have multiple things to export, we can write an export statement on a separate line instead of in front of a variable declaration. We specify the things to export in curly brackets.

```js
const temp1 = "This is some dummy text1";
const temp2 = "This is some dummy text2";

export { temp1, temp2 };
```

Note that the export syntax is not an object literal syntax. So in ES6, to export something we can't use key-value pairs like this:

```js
 // This is invalid syntax of export in ES6

export { key1: value1, key2: value2 }
```

To import the things we exported as a named export, we use the following syntax:

```js
import { temp1, temp2 } from './filename';
```

Note that while importing something from the file, we don't need to add the `.js` extension to the filename as it's considered by default.

```js
// import from functions.js file from current directory 
import { temp1, temp2 } from './functions';

// import from functions.js file from parent of current directory
import { temp1 } from '../functions';
```

Here's a [Code Sandbox demo](https://codesandbox.io/s/hardcore-pond-q4cjx).

**One thing to note is that the name used while exporting has to match the name we use while importing.**

So if you are exporting as:

```js
// constants.js
export const PI = 3.14159;
```

then while importing you have to use the same name used while exporting:

```js
import { PI } from './constants';
```

You can't use any other name like this:

```js
import { PiValue } from './constants'; // This will throw an error
```

But if you already have the variable with the same name as the exported variable, you can use the renaming syntax while importing like this:

```js
import { PI as PIValue } from './constants';
```

Here we have renamed `PI` to `PIValue` and so we can't use the `PI` variable name now. Instead, we have to use the `PIValue` variable to get the exported value of PI.

We can also use the renaming syntax at the time of exporting:

```js
// constants.js
const PI = 3.14159; 

export { PI as PIValue };
```

then while importing we have to use `PIValue` like this:

```js
import { PIValue } from './constants';
```

To export something as a named export, we have to declare it first.

```js
export 'hello'; // this will result in error
export const greeting = 'hello'; // this will work
export { name: 'David' }; // This will result in error
export const object = { name: 'David' }; // This will work
```

**The order in which we import the multiple named exports is not important.**

Take a look at the below `validations.js` file:

```js
// utils/validations.js

const isValidEmail = function(email) {
 if (/^[^@ ]+@[^@ ]+\.[^@ \.]{2,}$/.test(email)) {
 return "email is valid";
 } else {
 return "email is invalid";
 }
};

const isValidPhone = function(phone) {
 if (/^[\$]\d{3}[\$]\s\d{3}-\d{4}$/.test(phone)) {
 return "phone number is valid";
 } else {
 return "phone number is invalid";
 }
};

function isEmpty(value) { 
 if (/^\s*$/.test(value)) {
 return "string is empty or contains only spaces";
 } else {
 return "string is not empty and does not contain spaces";
 } 
}

export { isValidEmail, isValidPhone, isEmpty };
```

and in `index.js` we use these functions as shown below:

```js
// index.js
import { isEmpty, isValidEmail } from "./utils/validations";

console.log("isEmpty:", isEmpty("abcd")); // isEmpty: string is not empty and does not contain spaces

console.log("isValidEmail:", isValidEmail("abc@11gmail.com")); // isValidEmail: email is valid

console.log("isValidEmail:", isValidEmail("ab@c@11gmail.com")); // isValidEmail: email is invalid
```

Here's a [Code Sandbox demo](https://codesandbox.io/s/youthful-flower-xesus).

As you can see, we can import only the required exported things and in any order, so we don’t need to check in what order we exported in another file. That’s the beauty of named exports.

## Default Exports in JavaScript

As I said earlier, there can be at most one default export in a single file.

You can, however, combine multiple named exports and one default export in a single file.

 To declare a default export we add the default keyword in front of the export keyword like this:

```js
//constants.js
const name = 'David'; 

export default name;
```

To import the default export we don’t add the curly brackets as we did in the named export like this:

```js
import name from './constants';
```

If we have multiple named exports and one default export like this:

```js
// constants.js
export const PI = 3.14159; 
export const AGE = 30;

const NAME = "David";

export default NAME;
```

then to import everything on a single line we need to use the default exported variable before the curly bracket only.

```js
// NAME is default export and PI and AGE are named exports here

import NAME, { PI, AGE } from './constants';
```

One specialty of default export is that we can change the name of the exported variable while importing:

```js
// constants.js
const AGE = 30;

export default AGE;
```

And in another file, we can use another name while importing

```
import myAge from ‘./constants’; 

console.log(myAge); // 30
```

Here, we have changed the name of the default exported variable from `AGE` to `myAge`.

This works because there can be only one default export so you can name it whatever you want.

Another thing to note about default export is that the export default keyword cannot come before variable declaration like this:

```js
// constants.js
export default const AGE = 30; // This is an error and will not work
```

so we have to use the export default keyword on a separate line like this:

```js
// constants.js 
const AGE = 30; 

export default AGE;
```

We can, however, export default without declaring the variable like this:

```js
//constants.js
export default {
 name: "Billy",
 age: 40
};
```

and in another file use it like this:

```js
import user from './constants';

console.log(user.name); // Billy 
console.log(user.age); // 40
```

There is another way of importing all the variables exported in a file using the following syntax:

```js
import * as constants from './constants';
```

Here, we are importing all the named and default exports we have in `constants.js` and store in the `constants` variable. So, `constants` will become an object now.

```js
// constants.js
export const USERNAME = "David";
export default {
 name: "Billy",
 age: 40
};
```

And in another file, we use it as below:

```js
// test.js
import * as constants from './constants';

console.log(constants.USERNAME); // David
console.log(constants.default); // { name: "Billy", age: 40 }
console.log(constants.default.age); // 40
```

Here's a [Code Sandbox demo](https://codesandbox.io/s/green-hill-dj43b). 

If you don’t want to export on separate lines for default and named exports, you can combine it as shown below:

```js
// constants.js
const PI = 3.14159; 
const AGE = 30;
const USERNAME = "David";
const USER = {
 name: "Billy",
 age: 40 
};

export { PI, AGE, USERNAME, USER as default };
```

Here, we are exporting `USER` as the default export and others as named exports.

In another file, you can use it like this:

```js
import USER, { PI, AGE, USERNAME } from "./constants";
```

Here's a [Code Sandbox demo](https://codesandbox.io/s/eloquent-northcutt-7btp1). 

### Conclusion

* In ES6, data declared in one file is not accessible to another file until it is exported from that file and imported into another file.
* If we have a single thing in a file to export like class declaration, we use default export otherwise we use named export. We can also combine default and named exports in a single file.

### Thanks for reading!

Check out my recently published [Mastering Redux](https://master-redux.yogeshchavan.dev/) course.

In this course, you will build 3 apps along with food ordering app and you'll learn:

* Basic and advanced Redux
* How to manage the complex state of array and objects
* How to use multiple reducers to manage complex redux state
* How to debug Redux application
* How to use Redux in React using react-redux library to make your app reactive.
* How to use redux-thunk library to handle async API calls and much more

and then finally we'll build a complete [food ordering app](https://www.youtube.com/watch?v=2zaPDfCKAvM) from scratch with stripe integration for accepting payments and deploy it to the production.

[<img src="https://gist.github.com/myogeshchavan97/98ae4f4ead57fde8d47fcf7641220b72/raw/c3e4265df4396d639a7938a83bffd570130483b1/banner.jpg">](https://bit.ly/3w0DGum)

**Want to stay up to date with regular content regarding JavaScript, React, Node.js? [Follow me on LinkedIn](https://www.linkedin.com/in/yogesh-chavan97/).**

[<img src="https://cdn.buymeacoffee.com/buttons/default-yellow.png" >](https://www.buymeacoffee.com/myogeshchavan97)

ES6 Import And Export Cheatsheet

<h2 id="hi-there-im-yogesh">Hi there, I'm Yogesh! 👋</h2>
I'm a freelancer and a full stack developer.
<ul>
<li>🔭 Mostly working on JavaScript, React and Node.js</li>
<li>🌱 I'm currently in love with React</li>
<li>⚡ Loves sharing knowledge through technical articles</li>
<li>👯 Connect with me for any freelancing project</li>
<li>📫 Want to stay up to date with regular content regarding JavaScript, React, Node.js? Follow me on <a target="_blank" href="https://www.linkedin.com/in/yogesh-chavan97/">LinkedIn</a>.</li>
<li>🚀 You can find my articles at <a target="_blank" href="https://blog.yogeshchavan.dev/">hashnode</a>, <a target="_blank" href="https://dev.to/myogeshchavan97">dev.to</a>, <a target="_blank" href="https://medium.com/@yogeshchavan">medium</a> and <a target="_blank" href="https://www.freecodecamp.org/news/author/yogesh/">freecodecamp</a>.</li>
<li>📌 I have written 100+ articles and tutorials which readers loved and appreciated.</li>
<li>🔥 You can check out my <a target="_blank" href="https://master-redux.yogeshchavan.dev/">Mastering Redux</a> course, <a target="_blank" href="https://modernjavascript.yogeshchavan.dev/">Mastering Modern JavaScript</a> book and my free <a target="_blank" href="https://yogeshchavan.podia.com/react-router-introduction">React Router Course</a></li>
</ul>

## Hi there, I'm Yogesh! 👋

I'm a freelancer and a full stack developer.

- 🔭 Mostly working on JavaScript, React and Node.js
- 🌱 I'm currently in love with React
- ⚡ Loves sharing knowledge through technical articles
- 👯 Connect with me for any freelancing project
- 📫  Want to stay up to date with regular content regarding JavaScript, React, Node.js? Follow me on [LinkedIn](https://www.linkedin.com/in/yogesh-chavan97/).
- 🚀  You can find my articles at [hashnode](https://blog.yogeshchavan.dev/), [dev.to](https://dev.to/myogeshchavan97), [medium](https://medium.com/@yogeshchavan) and [freecodecamp](https://www.freecodecamp.org/news/author/yogesh/).
-  📌  I have written 100+ articles and tutorials which readers loved and appreciated.
- 🔥 You can check out my [Mastering Redux](https://master-redux.yogeshchavan.dev/) course, [Mastering Modern JavaScript](https://modernjavascript.yogeshchavan.dev/) book and my free [React Router Course](https://yogeshchavan.podia.com/react-router-introduction)

Yogesh Chavan

Yogesh Chavan