Using the browser to explicitly access local files (
file://path/to/file), as opposed to accessing local files served by a local HTTP server (running on http://localhost), comes with restrictions, and I expect many libraries won’t work in the former context, while they would in the latter.
All of the Solid protocol being deeply tied to HTTP, serving pieces of the architecture (Pod, Identity Provider, potentially the app) over HTTP is a requirement you won’t be able to work around I’m afraid. However, there’s no reason why you shouldn’t be able to run everything locally, provided that you configure your local HTTP server to serve your static popup file. I usually default to serve - npm when I want to locally serve files on my filesystem, and I’m sure there is a number of utilities out there providing similar features if this one doesn’t suit you for some reason.
Finally, just to be sure I’m clear on what you want to do, your client runs server-side, and you want to use a popup to authenticate, is that right ? I’m not 100% sure how the code running in the popup is configured, but I assume you’re using
solid-auth-client, is that correct ? If so, I’m not entirely convinced that it can run in Node, it may need to run in a browser application (but don’t take my word for it, I’m not very familiar with this particular library). It also has some known security issues. If I understood your use case correctly, and you do want to run a Node HTTP server that serves a client application, you may be interested in GitHub - inrupt/solid-client-authn-js: A client library for authenticating with Solid, and in particular in
I hope this helps, but do let me know if I missed something of your use case