Codecademy Forums

FAQ: Intermediate JavaScript Modules - Named Imports


This community-built FAQ covers the “Named Imports” exercise from the lesson “Intermediate JavaScript Modules”.

Paths and Courses
This exercise can be found in the following Codecademy content:

Web Development

Introduction To JavaScript

FAQs on the exercise Named Imports

Join the Discussion. Help a fellow learner on their journey.

Ask or answer a question about this exercise by clicking reply (reply) below!

Agree with a comment or answer? Like (like) to up-vote the contribution!

Need broader help or resources? Head here.

Looking for motivation to keep learning? Join our wider discussions.

Learn more about how to use this guide.

Found a bug? Report it!

Have a question about your account or billing? Reach out to our customer support team!

None of the above? Find out where to ask other questions here!

Did anyone try to use string interpolation instead of string concatenation to log ?


Yes, I get the exact same output but the exercises in this section will not accept string interpolation as correct for any of them it seems.


Me too. And I couldn’t pass the check using interpolation… until I modified the log message using concatenation.

Suppose I imported a function/object (named as AAA, for example) into my current .js file.
Can I create a different function/object, also named AAA, in the current .js file?

Does it cause an error? Or is it not considered the best practice even though we can do so?

I guess this may have something to do with how we should do function/object naming when writing code, right?

Can I import from files that are not .js ?

to the question, can I overwrite an imported function? I tried different things. Seems in Javascript changing a function is possible (unless you define it with const) but in this Codecademy exercise it is not. Try it out yourself!

1 Like

improper grading for ES6 syntax. This entire lesson for modules has been riddled with poor compatibility with ES6 syntax.

fails with string interpolation… this lesson is riddled with bugs…

It seems like some of the compatibility issues have been resolved, but not all of them.

One of the earlier exercises let me use template strings, and then I saw some comments that, for others, this had thrown an error.

However, just having completed exercise 8, it wouldn’t let me pass from Task 4 to 5 unless I used function declaration syntax instead of an arrow function i.e.

function displayStaffStatus() {


instead of

const displayStaffStatus = () => {


This is particularly confusing and inconsistent, because in a previous exercise it had let me use arrow function syntax for the displayFuelCapacity() function, which appears earlier in the same piece of code (in the same file)!

You are right that there are lots of bugs in this lesson: have you (or anyone else) reported this issue and some of the specific bugs via the designated Bug Report form?

For anyone who doesn’t know how to do this: from any lesson, click Get Help in the bottom right of screen, then select Bugs from the drop-down).
Here’s a link to instructions about how to do it:
Note: you must include the URL of the relevant exercise in the description field.

As someone who is currently working through this lesson, I do get the feeling that improvements are being made. However, it is definitely still a work-in-progress, so by submitting bug reports we’ll hopefully speed this up and make things less frustrating for those that follow! :+1: :smiley:

A lot of the exercises at this point seem to require the semicolon to pass through the exercise. I haven’t been using it since the beginning of the path began by explaining ES6.

1 Like

Has anybody been able to run the code in exercises 7 and 8 ( airplane.js and missionControl.js using named exports ) using node ? I haven’t been able to even after transpiling it with babel. is named export syntax so new that even babel can’t transpile it ?

You have to insert the semicolon where necessary.
It’s really frustrating though :tired_face:

Why doesn’t this exercise and some previous ones accept ${template literals} or “double quotation marks” in the answer?