memfs | In-memory implementation of Go 's ` io/fs.FS ` interface

This should work:

I was able to narrow the source of the problem down to a dependency.

It seems like memfs is not compatible with graceful-fs which is a dependency of fs-extra which in turn is a dependency of a library I'm using in my own code (laravel-mix). So here's a very minimal reproduction of the error now:

As you mentioned, MEMFS is an in-memory "filesystem" and it works in any browser. IndexedDB is a proper database and it's optimal use-case is for storing large amounts of data (more than what can fit in RAM).

Often times when an app or website is loaded for the first time there's a lot of API calls, authentication, and other work that needs to be done. Doing this every time the application opens up is not optimal so IndexedDB can be used as a way to speed up repeated visits. This way, the latest app state could be stored in IndexedDB and the app can then sync in the background (see stale-while-revalidate).

If you think your game could benefit from this, then you could consider using it. If you think you could also do this would MEMFS, however, I would recommend that since IndexedDB has some nuances.

In the specific case of safari on IOS, you can't store blobs in IndexedDB. You can, however, convert the blob into an ArrayBuffer but you'll also have to store the MIME type alongside the buffer in order to do the conversion correctly (since ArrayBuffer doesn't have a MIME type but blob does).

Writing to storage in IndexedDB may also fail. This could happen for a variety of reasons. Maybe the user is using private mode, or maybe they don't have enough disk space.

If the user clears their cache on their phone, the IndexedDB data may be cleared as well. You may need to handle this.

I've run into some of these errors in the past using IndexedDB and it can be a headache. I would recommend Memfs.

As for the implementation details of IDBFS, it may or may not remain constant across browsers and platforms. What I can say for sure, however, is that unless you are saving a lot of data that needs to be computed in your first application, try profiling memfs and if it works well enough, then you can stick with it.

All make systems (as required by POSIX) have a number of built-in rules including rules that know how to compile object files from C files.

For information on GNU make's built-in rules you can review the manual.

Laravel Mix 6 removes a number of options from the CLI. You will need to update the scripts section of your package.json file accordingly.

See Update Your NPM Scripts
https://laravel-mix.com/docs/6.0/upgrade#update-your-npm-scripts

Before:

What I see is that your saving logic is faulty, and I suspect you aren’t able to iterate the map because it is in fact empty.

Here

Here is what I ended up doing–

input_test.html for file input: