Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Enhancement Proposal: dynamic imports

See original GitHub issue

Now that dynamic imports are now stage 3 and are used by Webpack v2 for code splitting, I’d like to propose we add support for this in Espree/ESLint behind an option like experimentalDynamicImport: true.

An Acorn plugin already exists, and it looks like it’s well used: https://www.npmjs.com/package/acorn-dynamic-import

Issue Analytics

State:
Created 6 years ago
Reactions:4
Comments:13 (11 by maintainers)

Top GitHub Comments

1reaction

kaicataldocommented, Jun 20, 2017

@mysticatea In general, I agree. This feels like a special case to me because of Webpack. Personally, I think it doesn’t feel great to have to use another parser to get code splitting in such a ubiquitous tool.

0reactions

kaicataldocommented, Oct 15, 2020

@tschaub It’s been discussed many times in the eslint/eslint repo (and we’ve had proponents both for keeping ecmaVersion as it is currently and setting to latest), but the summary is that we’ve erred on the safer side of things by making new syntax opt-in rather than opt-out. This means that someone running their code in an environment that doesn’t support the latest syntax would never accidentally push code that couldn’t execute to production.