Rahul Gupta

Sounds Good. Thanks!

Would it be possible to have a better error message than `401 Unauthorized` on the container (irrespective of how you solve this issue). Clearly, the resource (unslashed) exists, and it...

The required 404 is unfortunately not helpful to the client! At the very least, the error message saying "is a container" would be useful.

I am not literally saying "is a container" message, but something that will let the client know that it can try with `/`. Actually, I dislike the whole trailing slash...

> Redirect is not required for interop. Sure. I am not arguing with that (or with you). I am just trying to see if there is an iota of possibility...

This actually seems identical to #10. (Should have read more carefully)

Some more info... I get the following response from the fetch inside `getNodeSolidServerCookie`... ``` Response {type: "opaqueredirect", url: "https://inrupt.net/login/password", redirected: false, status: 0, ok: false, …} body: null bodyUsed: false...

Yes, as mentioned above this is happening in an nwjs environment. However, I cannot identify anything environment specific that would prevent `fetch` from doing its thing. But #10 seems to...

Strangely @edbaafi's example only works if you use: ```json "main": "something.js" // '.js' extension "node-main": "somethingelse.mjs" // '.mjs' extension ``` That is, only `node-main` can be set as a module...

Also another temporary way to solve this would be to use the [esm](https://github.com/standard-things/esm) module. This will hijack the require to provide es module loading (effectively you will use this and...