FAQ: Intermediate JavaScript Modules - Import Named Imports

Interesting speculation!
I would like to think this is done on purpose, for this reason… However, it does seem a harsh way to get us to use a variety of syntax - a much better approach would be to state at the outset that this is what they are trying to do, and then make it clear in the task instructions which type of syntax they would like us to practise, rather than it being left to frustrating and time-consuming trial-and-error guess work :expressionless::confused:

What I’m concerned about more than anything, is the sense some people have that their Bug Reports aren’t being responded to. As there is a specific Bug Reporting facility for this purpose, I can understand rant and raves in this forum (instead of an actual Bug Report) to fall on deaf ears, but if actual Bug Reports aren’t being acted upon, then that’s worrying!
@byteslayer77703, @jeltehomminga, is that actually the case? Did you submit Bug Reports following the prescribed procedure?..as explained here:


I submitted quite a few bugs and issues via this procedure during my first couple of months with Codecademy. However, as I never had any acknowledgement of receipt, I did start wondering whether they were acted upon. As they take a fair amount of time to describe and submit properly, I actually started sending less and less…

…does anyone else have any thoughts on this? :thinking:

If anyone is interested, here’s a link to another of my posts on this subject:


@nondera, @supertonic00, @magicmark


I agree that if the SCT behavior is on purpose that it would be much better if the lesson specified which methods to use. The trial and error is frustrating especially when you’re still learning, and aren’t sure if you may have done something else wrong. I can’t say with any certainty that the bug reports do or don’t fall on deaf ears so to speak. I do know that Codecademy has recently employed a team tasked specifically with fixing bugs in the lessons. I don’t know if they are actively investigating the learner submitted bug reports. Perhaps @alexcraig or @mtf could shed more light on this topic.


Thanks for the reply! That sounds like positive news!

I’m more than happy to spend time on submitting the bugs/errors I spot, if I know they are being at least read. The process of spotting, mulling, resolving, describing and submitting is actually a really good learning/consolidation/reenforcement process. Obviously there may be very good reasons why they are not actioned (after all I am still a beginner). As a learner, though (and also as a teacher in another field), what I feel I can say is that I think it would be much more motivational and constructive educationally for any reports to at least be acknowledged. It would be super-motivational and super-constructive if a well-submitted and well-reasoned Bug Report (one that someone has obviously taken the trouble and time to think about and set out clearly) received a reply explaining either 1) why it won’t actually be actioned; or 2) why it will be actioned - as this would provide the learner with very useful feedback (all part of the learning process).


Add to the tagged names @factoradic and @zystvan.


I’ve submitted several bug reports myself. I’ve never had one replied to directly. I have seen bugs discussed on the forum, that have either gained the attention of or were specifically brought to the attention of a Codecademy team member, and then seen the bugs fixed with an accompanying reply to the forum announcing the fix.

I’m not sure that the ‘bug fixing team’ would consider the SCT for a particular lesson only accepting one of several possible solutions a bug per se’. They may consider it more of a user preference, and not get in any hurry to address it.


I agree with you that this isn’t a bug per se. I, personally, haven’t submitted such issues in bug reports - just battled with the SCT until I’ve done what it wants, and treated it as an additional “consolidation” exercise. :wink: :rofl: However, I have definitely noticed from the comments a high number of frustrated learners with this particular lesson on modules, and when so many people are obviously being tortured rather than supported, I think that definitely comes under the scope of “bug”… until there is an additional option of submitting an “issues” report.

I have always understood that the forums were more for discussion, rather than rants about the design of particular exercises. When the rants start to outweigh healthy discussion, then I would say there is definitely a need for some “adjustments” :wink: :smiley:


The moderators and super users have a sort of inside track that has produced results in a few cases recently. I’ll see if we can’t get the issues in this thread some attention.


Thanks, really appreciate the reponses! :smiley:

1 Like

Hey all, I’ll get this flagged up, sounds very confusing indeed! Should be sorted within a week or two. If you have any future bug reports (anyone but particularly @jon_morris) send them to me in the format:

  • Summary Heading
  • URL
  • Error
  • Steps to recreate
  • Any known workaround

And I will get them sorted ASAP


If it was done on purpose, wouldn’t you think a little disclaimer at the beginning of the modules lesson would be logical? Like if we were told to use old-school function declarations in the prompt we would at least have some idea what was expected of us.

I agree with you. I’m tending to believe that rather than an intentional attempt to keep us on our toes, or familiarize us with the different ways functions can be written, it’s more likely an oversight that hasn’t been corrected. I believe that it has already been brought to the attention of the Codecademy Engineering team, but I’ll double check, and report it myself if it hasn’t. It is a bit confusing.

1 Like

That would be lovely. I’ve tried reporting it myself but it seems like it hasn’t done much. It’s strange because sometimes I get away with arrow functions and it isn’t an issue, like in Modules #9 “Export Named Exports”, but other times, particularly with the .forEach() method, I fail the step and have to use “function” instead (Modules 8 & 10 come to mind).

1 Like

What is up with these exercises? Every convention taught in previous exercises (arrow syntax, interpolation) is suddenly not accepted anymore? I’ve just spend 5 minutes pondering over an exercise because I forgot a semi-colon.

If this is what Codecademy has to offer for €35/month then yeah, this is gonna be my final month on this platform.

Guess you get what you pay for

Is anybody else getting an error due to all the exports we did in the previous lesson on airplane.js?

SyntaxError: /home/ccuser/workspace/intermediate-javascript_modules-airplanes/airplane.js: ‘import’ and ‘export’ may only appear at the top level (31:2)
29 |
30 | export function meetsSpeedRangeRequirements(maxSpeed, minSpeed,requiredSpeedRange) {

31 | export let range=maxSpeed-minSpeed;

I’ve been reading the forums for javascript module and I also threw a bug report to report that these lessons don’t support use of a lot of ES6 functionality and interpolation. There are no replies and I’m actually shocked because I started learning ES6 and testing ways for it to work because of the first few lessons teaching ES6. It should state in the instructions if the lesson does not support ES6 functionality instead of having the user doing test cases to figure out that the lesson only supports ES5

1 Like

Hi alex I’m currently working through the Intermediate Javascripts Modules and have hit the infamous arrow function blocks. looked through the comments and found yours dated August 6. Just to say that the lessons still haven’t been amended to accept arrow functions or at the very least warn the students that they can’t use them.

If you need me to send any more information just say so.

Yours, Damian

1 Like

Great thanks, will chase this up again.

1 Like

@factoradic and @zystvan

@alexcraig @mtf

over one year now and this is still broken. What gives?