We need to document which modules need to be externalized in webpack configuration in order to create web applications using rdflib and solid-auth-client.

Example external section of webpack configuration file:

  externals: {
    'node-fetch': 'fetch',
    'text-encoding': 'TextEncoder',
    'whatwg-url': 'window',
    'isomorphic-fetch': 'fetch',
    '@trust/webcrypto': 'cry

@jaxoncreed

Actually there is now way to see the real running version on solid.community or dev.inrupt.net and inrupt.net displays NSS 5.1.4
When creating a clean new server the NSS version is displayed

Could it be related to the migration process from one version to the next where :
data/solidServerName/index.html is not updated (solidServerName being solid.community or inrupt.n

Dollar signs entered into Builder loop nReps fields are being compiled to JS in the TrialHandler nReps parameter, causing a reference error in browsers, e.g., see Discourse post

Perhaps it was just me, but when I typed yarn Ubuntu suggested:

Command 'yarn' not found, but can be installed with:

sudo apt install cmdtest

which, of course, is not what is needed. This post gives nice simple instructions. Maybe something along these lines could be added to the README?

Thanks for putting th

We should create a hook that listens to NSS Web Sockets (https://github.com/solid/solid-spec/blob/master/api-websockets.md) and returns the last update.

For instance:

const { document, date } = useLastUpdate('http://example.org/foo', 'http://example.org/bar');

and, with a small component wrapper:

<TrackUpdates subscribe="http://example.org/foo,http://example.org/bar">

Currently there seems to be a lack of automatic update of gh-pages when new documentation is added. We also need to generate the API documentation using npm run doc for gh-pages, since I think it's bad practice to commit files that are automatically generated anyway.