How to mount multiple InMemory backends

[lvcabral]

Doing the configuration like this, we end up with only one mount cachefs:

How can I create separate inMemory mounts?

[james-pre]

@lvcabral, thanks for reaching out. You will need to wait for configure to resolve before mounts are loaded. If you try to use fs before then, you will just have the default InMemory mounted on /.

A suggestion, using multiple different InMemory backends mounted at different places does not include any meaningful benefits. If may be easier to just use the default InMemory.

When attempting to reproduce this locally, everything works correctly:

import { configure, fs, InMemory } from '@zenfs/core';

await configure({
	mounts: {
		'common:': InMemory,
		'pkg:': InMemory,
		'tmp:': InMemory,
		'cachefs:': InMemory,
	},
});

console.log(...fs.mounts.keys());

$ node index.js
/ /common: /pkg: /tmp: /cachefs:

[james-pre]

What you mean by "wait for configure to resolve before mounts are loaded"??

configure is not synchronous you will need to await it (like in my example) or use .then (configure(...).then(() => { fs.something(...) })).

I got your suggestion ...

Yeah, if your use case needs it, there is very little performance overhead to using multiple InMemory mounts.

[lvcabral]

I was already awaiting the configure in my code.
I believe there should be a way to create new instances of InMemory for each volume, so I can access those independently with specific URLs:
pkg:/source/main.brs or tmp:/images/mypic.png using the same fs

[lvcabral]

Of course the contents of each volume/root folder should be different

[james-pre]

In you[r] test you checked the mount keys, I checked the actual file system using readdirSync()

I just got this as well, it was a race condition in configure since mount creates new directories. I'm surprised it didn't get caught until now. e40bf4c should fix it.

I'm adding tests to prevent a regression now.

[lvcabral]

Cool, thanks for the quick feedback