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.

Add mjs to --ext default

See original GitHub issue

Currently, the only default file extension for the --ext CLI option is js.

It would be good to add mjs to the default, since it is the emerging standard for native Node.js modules. Then the increasingly common lint npm script could go from "eslint . --ext js,mjs" back to simply eslint ..

Issue Analytics

State:
Created 6 years ago
Reactions:10
Comments:27 (14 by maintainers)

Top GitHub Comments

7reactions

albertocommented, Mar 15, 2018

Given it’s still marked as experimental by node terms and it could be removed or changed in backwards incompatible ways, I am against adding it at this moment.

Stability: 1 - Experimental This feature is still under active development and subject to non-backwards compatible changes, or even removal, in any future version. Use of the feature is not recommended in production environments. Experimental features are not subject to the Node.js Semantic Versioning model.

6reactions

not-an-aardvarkcommented, Apr 12, 2018

In today’s TSC meeting, the TSC decided to not accept this issue for 5.0 because Node’s support for .mjs is still experimental. We anticipate that we will add support for this eventually when it becomes stable, unless Node’s roadmap changes. (As noted earlier in this issue, you can use the --ext=.js,.mjs flag to lint .mjs files today.)