[WIP] move to esm

[elf-pavlik]

I open it to mostly to discuss distributing this library as an ES Module around concrete working PR

This PR makes this module available as ES Module, it relies on esm package explained here: https://medium.com/web-on-the-edge/tomorrows-es-modules-today-c53d29ac448c

TODO

• bin/test.js

[tpluscode]

Default export should be avoided with ES modules. At least for non-internal modules

It would be better to have these exported as export BlankNode from './blank-node'

[tpluscode]

Hi @elf-pavlik. I missed this PR, thanks for your effort. I have proposed similar yesterday for sink-map: rdfjs-base/sink-map#10

Would like to hear your opinion

[elf-pavlik]

Hi @tpluscode

I think that a recent esm issue may complicate things. It made me lock my node version to v12.15

standard-things/esm#868

It also gave me impression that no one actively maintains esm module 😢

[tpluscode]

Interesting. I have not seen that error myself. Have you?

[elf-pavlik]

Yes, I've stumbled on similar error when using latest node LTS and found that github issue through that.

[retog]

I'm really looking forward to having some improvements here. With version 1.1.2 this is a pain, with different import styles working in different tools

There's one invocation of require left here:

https://github.com/elf-pavlik/data-model/blob/esm/lib/quad.js#L1

So I'm still getting "ReferenceError: require is not defined"

I've created elf-pavlik#1 to fix this.

[tpluscode]

Can we actually discuss removing default exports?

With default export commonjs imports will need the additional default

const rdf = require('@rdfjs/data-model')

-rdf.default.blankNode()
+rdf.blankNode()

[elf-pavlik]

I've just added commit removing all default exports in favor of using only named exports. Commonjs should be able to do

const { DataFactory } = require('@rdfjs/data-model')

[bergos]

fixed in #37