It is common for IDEs and game-engine editors to specify resources using URIs or file paths.

To access a deeply nested file, we need to call getFileHandle and getDirectoryHandle recursively. Each level is an asynchronous operation that needs to be run sequentially.

I propose that the getFileHandle, getDirectoryHandle, and removeEntry methods be overloaded to accept an array/iterable argument.

directory.getFileHandle(["path", "to", "file.txt"]);

Alternatively, file names should accept slashes as delimiters.

directory.getFileHandle("path/to/file.txt");

The options parameter should include a createRecursive flag to complement the create flag.

directory.getFileHandle(["path", "to", "file.txt"], { createRecursive: true });
// Creates:
// path/
// path/to/
// path/to/file.txt