You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This way, a fetchfs WASMFS backend can have a mapping from paths to
URLs used to satisfy those paths. I think this makes more sense than
creating a separate fetchfs backend for each individual file.
In the absence of a manifest, the old behavior of using the file path
as a relative path against the baseURL will still be used.
NOTE, it's important that the fetchfs have a dedicated directory
created/"mounted" or else the "create file with path" code path will
never be used. In other words, paths at `/whatever.txt` can never
work given the way WASMFS is implemented; the accessed files don't get
paths unless the parent directory and child path have the same
backend. So, creating the directory at `/dat` and having a manifest
entry like `/whatever.txt` is the way to go for a file at
`/dat/whatever.txt`.
0 commit comments