Dynamic import parsing throws 'import' and 'export' may only appear at the top level

[xsurge83]

The following change is throwing an error for dynamic module imports.
. Setting topLevel flag to null in parseStatement function which raises the

"'import' and 'export' may only appear at the top level"

Dynamic module import use to work in 5.7.3 with same settings.

I'm using angular-cli to compile my app which updated webpack to 4.29.9 with new acorn changes. Not sure if this is an angular-cli, webpack or acorn issue but after debugging I noticed these differences in acorn.

[michael-ciniawsky]

webpack/webpack#8656

[adrianheine]

Apparently this is again an npm issue. @marijnh Maybe we can come up with a workaround for these issues? When developing plugins it's also pretty difficult to make sure that all plugins are using the same acorn tree. Putting tokTypes, TokenType, version and isIdentifierStart on the class would be enough for my plugins to not directly depend on acorn.

[marijnh]

I think the Parser.acorn hack covers this problem too, no?

[adrianheine]

yep