Usage from node v8.5.0+ with --experimental-modules

[d3]

Usage from node v8.5.0+ with --experimental-modules

[mbostock]

d3-dsv is usable directly from Node, whether or not you choose to enable --experimental-modules. However, --experimental-modules still limits you to CommonJS interoperability with d3-dsv; you must either continue to use require to load d3-dsv, or import the entire d3-dsv module as the default export:

import d3Dsv from "d3-dsv";

This is because --experimental-modules is hamstrung: it will only load ES modules if the imported file has the extension .mjs, and its CommonJS interoperability is limited to loading the entire module as the default export.

Unlike most other ES module loaders, --experimental-modules does not observe the module entry point in the package.json. So with --experimental-modules you are still consuming d3-dsv’s UMD bundle as defined in the main entry point.

This limitation is why I recommend using @std/esm. Unlike --experimental-modules, @std/esm observes the module entry and allows you to consume ES modules using the standard .js file extension. It also provides better CommonJS interoperability, allowing you to import named symbols from CommonJS modules rather than being limited to the default imports.

[mbostock]

Please read my comment on the linked issue.

[dandv]

Pardon me for being dim on this, but shouldn't d3-dsv want to be usable directly from Node, without having to import any other module? I'm new to --experimental-modules, but published one that can be used just like that after asking on SO how to provide both native ES6 modules and backwards CommonJS compatibility.