I’m running a local instance of the community solid server (with -c @css:config/file.json) and created a new account using the /idp/register flow. After successful client authentication (using @inrupt/solid-client-authn-browser) the associated pods shall be listed (using function getPodUrlAll()). Unfortunately there’s no pod assigned.
As far as I can see, the lib fetches the profile card from the solid server and trys to find a predicate “http://www.w3.org/ns/pim/space#storage”. Unfortunately, there’s no such predicate associated.
The pod exist, as I could verify by accessing it through the URL, but it seems not to be assigned to the profile for some reason.
Also, thank you for the hint to modify the profile template, but I prefer to use the “tree/traversing” discovery described in the SOLID protocol and shown in the code referenced by @jeswr (thanks by the way!). Penny seems to do it the same way. I think this is more robust and I don’t have to take care when it comes to updating the CSS.
When in doubt, follow the specification. The most recent specification says that servers MUST provide a link header with a pim:stroage predicate in the root of the storage but it does not say that there MUST be such a predicate in the profile. In other words, no matter what server you are on, you can not count on there being a storage predicate in the profile. Therefore, the only interoperable way to find the location of the storage if it isn’t in the profile, is to do a HEAD or GET on the container and look for a returned link header with rel=“type” http://www.w3.org/ns/pim/space#Storage. If you haven’t found the storage yet, walk the container tree looking for the header until you find one. I don’t know which servers are spec-compliant in this regard, but if they do not have a link header with a storage triple at the root of the storage, that is a bug in the server.
And regarding “CSS compliant”: ideally “solid compliant” should be enough and not specific to the server. The solid-client-js library is also based on the solid standards, but I guess in some cases the use optional stuff that’s implemented by ESS but not by others. So in general it’s fine to expect that it also works with CSS