[WIP] Make the new module system in rdflib work

[megoth]

This should only be merged after linkeddata/rdflib.js#335 is merged and pushed into a new version.

Not 100% sure why this works, but seems to do the trick on my local setup.

Right, @RubenVerborgh already explained this in his comment linkeddata/rdflib.js#335 (comment)

The only breaking change is that external code that was incorrectly using import rdf from 'rdflib' should use import * as rdf from 'rdflib'. Preferably, such code imports the exposed subcomponents of rdflib, such that tree shaking becomes possible.

[RubenVerborgh]

You might be able to import * as $rdf, { NamedNode }, or might want to const { NamedNode } = $rdf.

Question is whether you really want to import * as $rdf instead of importing only the parts you need. And you probably do not want to import NamedNode, but rather import DataFactory and use its .namedNode method.

[RubenVerborgh]

This breaking change is why I strongly suggest to remove rdflib 1.0.{1,2}.

[megoth]

Question is whether you really want to import * as $rdf instead of importing only the parts you need. And you probably do not want to import NamedNode, but rather import DataFactory and use its .namedNode method.

Right now it seems that there are code in solid-ui that are dependent on $rdf being in the global object window, so think we should leave it as is for now, and have as goal to remove solid-ui dependency on $rdf in the global object.

[RubenVerborgh]

Needs an "rdflib": "^1.0.3" in package.json.

[megoth]

Updated to rdflib@1.0.3 in latest commit

[Vinnl]

It would indeed be clearer if this would be import * as $rdf, { NamedNode } from 'rdflib' I think.

[timbl]

This seems to work when I build it and run it.
The new 1.0.3. + rdflib is supposed to be basically compatible, so long as you don't use default imports.