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.

Use .mjs for JavaScript modules

See original GitHub issue

Squoosh is mostly using TypeScript (.ts), but it also uses .js for https://github.com/GoogleChromeLabs/squoosh/blob/master/src/lib/fix-pmc.js despite it being a module.

Let’s follow our own advice and use .mjs to denote JS modules as opposed to classic scripts.

If this is a problem for our current toolchain, it would be good to identify the problem and raise it upstream.

Issue Analytics

State:
Created 5 years ago
Comments:5 (2 by maintainers)

Top GitHub Comments

1reaction

developitcommented, Jul 4, 2018

Grabbing this since it’s a quick change.

@mathiasbynens - we need to get Webpack to include .mjs in its list of default extensions for module resolution.

0reactions

frank-dspeedcommented, Mar 17, 2020

and maybe you should consider my suggestion to turn all files into .js then marking the package in package.json as type: module and use typescript with checkJs: true flag and use JSDOC annotations you can then still type check while working with nativ modules till they accept .mjs