ES6 Import/Export Challenges Broken
See original GitHub issueIdentified in issue #16207 and PR #16201
The final 6 challenges in the ES6 section teach the user about using import
and export
.
Challenges 23, 25, 27 produce: require is not defined
Challenges 24, 26 produce: exports is not defined
Not sure where to start with this issue; however, we need to figure this out before launching Beta.
Issue Analytics
- State:
- Created 6 years ago
- Comments:15 (15 by maintainers)
Top Results From Across the Web
ES6 export and import problems - javascript - Stack Overflow
I'm trying to export functions in ES6 to access them from other files. But I can't figure out how. file 1: (import) import...
Read more >Avoid these issues when using new ECMAScript modules in ...
You will get an error: Jest “SyntaxError: Unexpected token export”. Always remember to set the type: "module" if you're publishing a package ...
Read more >ES6 Import & Export > Webpack Encore - SymfonyCasts
Imagine you're using a huge external library - like lodash - which is really just a collection of independent functions. If that library...
Read more >Node Modules at War: Why CommonJS and ES ... - Code Red
Under dynamic modules, the importer would define the export names in the import . The ESM loader would initially just trust that dynamic...
Read more >JavaScript modules - MDN Web Docs
Report problems with this compatibility data on GitHub ... The first thing you do to get access to module features is export them....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@QuincyLarson, Since this is closed and merged, should it be removed from the TODO list?
So, this stuff is a bit flaky. For http://localhost:3000/en/challenges/es6/use-export-to-reuse-a-code-block, it mentions that export {foo, bar} is acceptable, but the regex is set up to only validate:
export const foo = “bar”
Anyway, we can tighten up the regex later.
I think what’s worse is that the error messages are so obfuscated!