Now, with Node.js 12, there is native support for ECMAScript modules. But it has to be manually enabled, by using the '--experimental-modules' flag.
The current version - Node.js 13 - doesn't need a flag to enable ECMAScript modules. Great! It is on by default. But the runtime will log a message on startup, a warning that the feature is not ready for production yet. Maybe we can expect it to be a default setting, without experimental warnings, in the next LTS later this year?
I have tried out ECMAScript modules in Node.js, using the experimental flag and the type: module in package.json.
|Import tooling support, not perfect, but good enough.|
Cool, but not perfect yet
I ran into issues when writing & running unit tests. My favorite unit testing library is tape, but it doesn't support ECMAScript modules natively:
Must use import to load ES Module
What about the AVA test runner ? No native support yet. Mocha? I couldn't find any info about it, but tests won't run.
Don't try this at ... work?
Besides that using a default unit testing runner usually is a good thing, there's also a huge drawback with the experimental & non-standard approach that I describe in this post. The node command will run a single file only. 👀
But, hey, we're in Experimental Mode right! A workaround would be to execute a custom runner containing all our unit tests. Just don't forget to add every new file to it.
"test": "node --experimental-modules test/run.js | tap-spec"
(from the script section of package.json)
The test/run.js file:
Try this at home, folks. Don't try it at work (yet). 🏡