[error] bad ES6 import paths in "modular" example code in README?

[warren-bank]

Disclaimer: I could be wrong about this, because personally.. I only use CommonJS module imports.

But.. I was looking at the README and noticed that the ES6 module import paths don't jive with the directory structure published to npm.

Specifically, every instance of:
from '@textile/ipfs-lite/

...should be replaced by:
from '@textile/ipfs-lite/dist/

..unless ES6 module imports are somehow smart enough to search paths relative to main in package.json when the verbatim path isn't found, which I highly doubt.. but can't say for sure.

[warren-bank]

from the Node.js documentation regarding its implementation of ES6 module imports

• package.json can include an exports field containing a basepath
  • no example given for its usage

thoughts:

• I wasn't aware that Node.js added support for ES6 modules
• dunno if Webpack supports this exports field
• package.json in v0.1.5 doesn't include this exports field.. so moot point (at the moment)

update:

• evidently ES6 modules went from an experimental feature to release in Node.js v12
• in the Webpack documentation regarding its implementation of ES6 module imports
  • I don't see anything about an exports field