Closed bourgeoa closed 3 years ago
It must be a difference in our development environments, because if I clone the current master, then run npm install, it successfully builds and I can access it from the created bundle.js. I checked this before I npm'd it and also just now.
I found that webpack npm null-loader
could replace an unused module by an empty module.
After a lot of trial and error, I found a working solution :
. as rdflib treated solid-file-cli as external and only succeed any compile keeping it external
. I added a rule to use webpack null loader
but it only compiled if
. in external I used "solid-file-client" : "solid-file-client"
in replacement of "solid-file-client" : "null"
.
With that I have a solid-ide and solidTiddlywiki both using a solid-file-client compatible with rdflib@0.20.1
I have never seen the error you describe. If it is indeed a problem with how rdflib external works, then I need to fix it there, we should not be doing things to solve an error that occurs elsewhere. But, as I said, I do not get the same error as you - I have never seen that error.
Here are the 2 webpack files I modified
The developpement environnement for solidTiddliwiki is browserify babelify
For solid-ide there is no dev environnement as you only use Githubissues.
I got the following error since V0.5.0 where was introduced rdflib@0.20.1 (with solid-file-cli as webpack : externals refered as "null" module for browser usage (same being applied to solid-file-client))
At the same time I tried to upgrade
solid-ide
to use latest version ofsolid-file-client
. The solid-file-client never loaded.