Error: 'import' and 'export' may only appear at the top level · Issue #2558 · getsentry/sentry-javascript · GitHub
![Module parse failed: 'import' and 'export' may only appear at the top level (36:3) · Issue #1266 · styleguidist/react-styleguidist · GitHub Module parse failed: 'import' and 'export' may only appear at the top level (36:3) · Issue #1266 · styleguidist/react-styleguidist · GitHub](https://user-images.githubusercontent.com/18602363/52358015-713b9500-29f4-11e9-9c28-3a8bc8878add.png)
Module parse failed: 'import' and 'export' may only appear at the top level (36:3) · Issue #1266 · styleguidist/react-styleguidist · GitHub
![Terser plugin: "Export" statement may only appear at the top level, plus other compilation issues - bud - Roots Discourse Terser plugin: "Export" statement may only appear at the top level, plus other compilation issues - bud - Roots Discourse](https://discourse.roots.io/uploads/default/original/2X/b/b48ee0131a5d0c1b01dfd51d2d0e6758b4e22f2e.png)
Terser plugin: "Export" statement may only appear at the top level, plus other compilation issues - bud - Roots Discourse
![angular - Module parse failed: 'import' and 'export' may only appear at the top level - Stack Overflow angular - Module parse failed: 'import' and 'export' may only appear at the top level - Stack Overflow](https://i.stack.imgur.com/yf2yF.png)
angular - Module parse failed: 'import' and 'export' may only appear at the top level - Stack Overflow
![Dynamic import parsing throws 'import' and 'export' may only appear at the top level · Issue #809 · acornjs/acorn · GitHub Dynamic import parsing throws 'import' and 'export' may only appear at the top level · Issue #809 · acornjs/acorn · GitHub](https://user-images.githubusercontent.com/863208/53190398-5ce3c480-35be-11e9-889d-99d84cc78f5d.png)
Dynamic import parsing throws 'import' and 'export' may only appear at the top level · Issue #809 · acornjs/acorn · GitHub
![Error in release 3.1.1 (Module parse failed: 'import' and 'export' may only appear at the top level (138:339)) · Issue #178 · sveltejs/svelte-loader · GitHub Error in release 3.1.1 (Module parse failed: 'import' and 'export' may only appear at the top level (138:339)) · Issue #178 · sveltejs/svelte-loader · GitHub](https://user-images.githubusercontent.com/24325642/116014129-18bf3500-a60a-11eb-9b3f-babfffb58c45.png)
Error in release 3.1.1 (Module parse failed: 'import' and 'export' may only appear at the top level (138:339)) · Issue #178 · sveltejs/svelte-loader · GitHub
ParseError: 'import' and 'export' may only appear at the top level · Issue #228 · vuejs/vueify · GitHub
![Sebastian on Twitter: "Following up from my earlier tweets about JS parsing. I've made the Rome JS parser tolerant. Parsing will not be stopped on syntax errors. Uses the same diagnostic format Sebastian on Twitter: "Following up from my earlier tweets about JS parsing. I've made the Rome JS parser tolerant. Parsing will not be stopped on syntax errors. Uses the same diagnostic format](https://pbs.twimg.com/media/D4kn47wUEAA60dN.png)
Sebastian on Twitter: "Following up from my earlier tweets about JS parsing. I've made the Rome JS parser tolerant. Parsing will not be stopped on syntax errors. Uses the same diagnostic format
![reactjs - React App won't run- after accidentaly run npm add -syntax error: 'import' and 'export' - Stack Overflow reactjs - React App won't run- after accidentaly run npm add -syntax error: 'import' and 'export' - Stack Overflow](https://i.stack.imgur.com/peV0G.png)