-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Option to not use sync cache with Async(FileSystem)
#64
Comments
The idea behind having all async file systems use await configure({
disableAsyncCache: true,
mounts: {
...
}
}) What do you think? |
Like zen-fs/dom#12, this could be done using |
@atty303 Does v0.12.1 resolve the issue? You should be able to set await configure({
disableAsyncCache: true,
mounts: {
// this mount will have the sync cache
'/mnt/net/example': {
backend: Fetch,
index: 'https://example.com/index.json',
disableAsyncCache: false,
},
// this mount will not have the sync cache
'/mnt/emscripten': { backend: Emscripten, /* Should be published soon */ },
// this mount will not have the sync cache
'/mnt/worker/0': { backend: Port, port: worker0 },
// this mount will not have the sync cache
'/mnt/worker/1': { backend: Port, port: worker1 },
}
}); |
Async(FileSystem)
Async(FileSystem)
Unit tests confirm that this is working correctly, so I am closing the issue. |
Sorry for the delay. |
@atty303 My apologies, I had not released the Zip updates yet. @zenfs/zip v0.4.0 should be up to date. |
I've decided to use only the Async API in my integration with Emscripten, so I no longer need crossCopy when using
Async(FileSystem)
.I thought it would be nice to have an option to not use crossCopy or the memory mirror itself in such cases.
The text was updated successfully, but these errors were encountered: