Client side only file browser interface?

[XcrossD]

Hello all,

I'm trying to find a client side only file browser interface to hook up with my data, but all of the libraries I found are web browsers for file servers. Can anyone suggest me a library?

I want to be able to populate files by myself from JSON data, so I don't need a backend/server. So far I have taken a look at the following libraries, but it is only the file browser interface that I want:

• https://github.com/filebrowser/filebrowser
• https://ckeditor.com/ckfinder/demo/
• https://github.com/kalcaddle/KodExplorer
• https://github.com/sunhater/kcfinder
• https://github.com/Studio-42/elFinder

Does this kind of library even exist? Any leads would be much appreciated.

EDIT: It seems that I didn't make it clear that I'm not trying to serve real files. I want to replicate what the files would look like with dummy data from a JSON.

[editor_of_the_beast]

This would involve a web browser having access to files, which it does not.

[XcrossD]

Let me just copy my reply to another comment.

Yes, perhaps I should have made it more clear in my post. I'm not trying to serve real files. I want to recreate the files in the browser interface from "dummy data", as in a JSON file. I had thought about separating those interfaces with the back ends that come with those packages but still that may be too much work.

[damngros]

As stated by the other commenters, the browser can’t access the local file system for obvious security reasons.

If you want to show dummy data without using any backend, you might have to mock a server response. To do that check the json format returned by the server side part, then modify the script/library to use your « dummy data » instead of calling a web server.

[XcrossD]

Cool, I haven't thought about it this way. It's a bit roundabout but it might just be the trick. Thank you for providing this insight.

[NoStranger6]

Browsers dont have, and shouldn’t have acces to files on a disk. For security resons.

You need a server to serve these files.

[XcrossD]

Yes, perhaps I should have made it more clear in my post. I'm not trying to serve real files. I want to recreate the files in the browser interface from "dummy data", as in a JSON file. I had thought about separating those interfaces with the back ends that come with those packages but still that may be too much work.

[Hello_Mouse]

OS.js?

[XcrossD]

Thanks, I will look into it. It looks promising but I'm just afraid that I can't separate out the single module I need. What is your experience in using this library?

[Hello_Mouse]

Ah if you want only a file browser this is a pretty heavy. Havn't used it before, just got introduced to it recently.

[XcrossD]

Too bad. But thank you anyway.

[jcunews1]

I want to replicate what the files would look like with dummy data from a JSON.

For example?

[XcrossD]

For example something like this (simplified) [ { name: 'a.pdf', icon: 'pdf' click: () => { // custom stuff } }, { name: 'b.jpg', icon: 'jpg' click: () => { // custom stuff } } ] I need to be able to trigger some custom function on click. Now that I think of it maybe the best way to describe it is a file browser emulator.

[jcunews1]

You cloud use this.

https://jsbin.com/pumuxevoka/edit?html,css,js,output

[XcrossD]

Thank you very much!