Question

165

ES6 import duplicates?

rated 0 times [ 171] [ 6] / answers: 1 / hits: 9232 / 8 Years ago, thu, may 26, 2016, 12:00:00

I'm trying to keep my code (server and client side) as modular as possible and this requires a lot of importing and exporting, however I have an unanswered question.

I tried to search from here, I read topical blog posts and even watched few YT videos, but it's still not fully explained. I would love to avoid making this mistake right now and avoid rewriting my logic later.

File1

import React from 'react';



// do something

File2

import React from 'react';



// do something else

File3

import File1 from './file1';

import File2 from './file2';



// do something with both

Is it smart enough? Can I import same
module as much as I want and it imports it only once?

What if I need to import React to File3 too? Is it still smart enough to handle this situation?

I'm using Node, Babel and Webpack.

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

wyattkennyc

Add To Favorites

Follow

Total Points: 650

Total Questions: 102

Total Answers: 90

Location: Monaco

Member since Mon, May 23, 2022

2 Years ago

answered 8 Years ago annalise · Accepted Answer

When you import a module through Node (and by extension, Webpack, as it effectively follows the same rules when it comes to module resolution), the code in the file is executed once, then the resulting exports are cached. This means that in both of your files, React will be a reference to the same object. So effectively your assumption is correct - Webpack is indeed smart enough to not execute React's full source code file every time you import it.

You can test this for yourself pretty easily - add a console.log() to a module that's imported in multiple places within your app (making sure it's not in a function or anything else that would defer its execution). You'll see that the log only happens once, rather than once per import!

Update: It's also worth noting that the spec for ES2015 modules effectively lists this as a requirement for any implementation too:

This operation must be idempotent if it completes normally. Each time it is called with a specific referencingModule, specifier pair as arguments it must return the same Module Record instance.