@Sheap - you are mistaken about solid-node-client and NSS - it does work with both NSS and ESS. (though depending on your version you may need to apply a patch as mentioned below)(
The landscape for Solid login has changed every couple of months for two years. We are finally at a stage where most of the spec related to it is complete and the servers have mostly (though not completely or consistently) implemented the spec.
Solid-Node-Client does work with both NSS and ESS but since they are both changing, there are gaps as the library plays catch up.
There is currently a bug in some versions of solid-node-client (it depends when you used npm to install it). A downstream package that causes solid-node-client to not work on NSS. I have submitted patches to the downstream libraries and solid-node-client should work again with NSS as soon as the patches are accepted by the downstream authors. There is a simple fix in the mean time - see Could i login solid pod automatically without opening the solid login page? - #5 by jeffz for the details.
ESS recently completely changed their login flow which is what causes the dropping of the session after one login. I am investigating a fix for that and should have one soonish.
@Vincent - can solid-client-authn-node login to NSS with a username password? Can it log in to NSS with a token? Can you point me to documentation if either is possible?
If @vincent’s answer to those questions is yes, then the only reason to use solid-node-client over solid-client-authn-node is that solid-node-client leverages solid-rest to provide Solid access to a non-pod local file system via file:/// URIs and provides a plugin architecture for access to other storage systems. If Vincent’s answer is yes and you have no need of the local or plugin features, then solid-client-authn-node may be your best option.