一个 Dart 库,公开了 Web 平台的文件系统访问 API,使网络应用程序能够安全地读取和写入用户的本地文件系统。它提供了一种现代化的、基于权限的文件处理方式,与浏览器功能保持一致。该包通过直观的 Dart 接口简化了与文件和目录的交互,提升了需要文件操作的网络应用的用户体验。它专为网络平台设计,并在可用时利用原生浏览器 API。
适合场景
直接从用户的本地存储读取和写入文件
使用高级文件管理功能构建网页应用
在Web应用程序中启用拖放文件操作
使用持久文件访问创建离线优先的Web应用程序
允许用户保存文件而无需依赖下载提示
主要特点
与浏览器文件系统访问 API 的直接集成
基于权限的文件系统访问
支持读取和写入文件及目录
常见文件操作的最小样板代码
仅限 Web 的平台支持
适合对象
Web 开发人员构建以文件为中心的应用程序
需要安全的用户控制文件访问的应用程序
针对具有文件系统功能的现代浏览器的开发者
需要无缝文件交互且无需服务器往返的项目
寻求原生文件系统行为的 Flutter Web 用户
使用建议
仅适用于网页平台
需要支持文件系统访问 API 的现代浏览器
用户权限必须授予文件操作
对旧版浏览器的回退选项有限
不兼容移动或桌面 Flutter 目标
原始 README
以下为关联源码仓库的 README 原文快照,最新内容请访问源码仓库。
File System Access API
A Dart library to expose the File System Access API from web platform.
You can pick files and directories from user's file system to read, write, create, move and delete files/directories
from Dart web apps.
The web API (and this library) is experimental and is only supported on Chrome, Edge and Opera browsers for now.
It is not recommended to use this library in a production environment.
Features
This library reflects the web File System Access API using Dart types.
See a more detailed description on MDN Web Docs or keep reading to Usage section below.
Getting started
Install library in your Dart project:
$ dart pub add file_system_access_api
You're all set to play around with the API.
Note that in a cross-platform Flutter project, you can use this library only in a Web environment.
Use kIsWeb to prevent building/runtime errors and optimize build size.
Usage
You can reproduce example from the web API as much of the interfaces are transparent between this Dart library and the
JavaScript API.
Is browser supported
You can check if current browser supports the File System Access API with:
voidmain() {
if (!FileSystemAccess.supported) {
print("Browser does not support API.");
return;
}
print("Browser support API.");
}
Note that you must execute code samples below within main() as a result of a user gesture (e.g. click event) for
security reason. This part is omitted for brevity.
Open file(s)
You can ask a user to open file(s) with the method window.showOpenFilePicker() and access selected files like this:
voidmain() async {
try {
List<FileSystemFileHandle> handles = awaitwindow.showOpenFilePicker(
multiple: true,
excludeAcceptAllOption: true,
types: [FilePickerAcceptType(description: "Pictures", accept: {"image/png+jpg": [".png", ".jpg"]})],
startIn: WellKnownDirectory.pictures
);
for (final handle in handles) {
File file = await handle.getFile();
print("<file name='${handle.name}' size='${file.size} bytes' />");
// You can read content of a File using a FileReader, like any other File coming from 'dart:html'
}
} onAbortError {
print("User dismissed dialog or picked a file deemed too sensitive or dangerous.");
}
}
Save a file
You can ask a user where to save a file with the method window.showSaveFilePicker() and write in the selected file
like this:
voidmain() async {
try {
FileSystemFileHandle handle = awaitwindow.showSaveFilePicker(
suggestedName: "awesome.dart",
excludeAcceptAllOption: true,
types: [FilePickerAcceptType(description: "Dart files", accept: {"application/dart": [".dart"]})],
startIn: WellKnownDirectory.documents
);
FileSystemWritableFileStream stream = await handle.createWritable();
await stream.writeAsText(
"void main() {"" print('This is the way.');""}"
);
await stream.close();
// Note that data will be written on disk only after call to close() completed.
} onAbortError {
print("User dismissed dialog or picked a file deemed too sensitive or dangerous.");
} onNotAllowedError {
print("User did not granted permission to readwrite in this file.");
}
}
Open a directory
You can ask a user to pick a directory window.showDirectoryPicker() and recursively access files and directories like
this:
voidmain() async {
try {
FileSystemDirectoryHandle directory = awaitwindow.showDirectoryPicker(
// Use readwrite to ask permission and grant write access on files instead.
mode: PermissionMode.read
);
// List of handles in a directory emitted with a [Stream].// Listen periodically on [Stream] to reproduce a file system watch-like feature.awaitfor (FileSystemHandle handle in directory.values) {
if (handle.kind == FileSystemKind.file) {
print("<file name='${handle.name}' />");
} elseif (handle.kind == FileSystemKind.directory) {
print("<directory name='${handle.name}/' />");
// You can create, move and delete files/directories. See example/ for more on this.
}
}
} onAbortError {
print("User dismissed dialog or picked a directory deemed too sensitive or dangerous.");
}
}
Permissions
You can query / request permission on files and directories from the user. It allows you to write in files, modify a
directory structure, etc. Those methods are available per file/directory handle:
voidmain() async {
try {
final handles = awaitwindow.showOpenFilePicker(multiple: false);
final handle = handles.single;
var permission = await handle.queryPermission(mode: PermissionMode.readwrite);
if (permission != PermissionState.granted) {
print("Asking permission to read and write");
permission = await handle.requestPermission(mode: PermissionMode.readwrite);
if (permission != PermissionState.granted) {
print("read/write access refused, either prompt was dismissed or denied.");
return;
}
print("read/write access granted. 😀");
}
print("Write beautiful bytes. ✨");
} onAbortError {
print("User dismissed dialog or picked a file deemed too sensitive or dangerous.");
}
}
Note that current implementation of the File System Access API does not remember permissions across browser's sessions
when used with IndexedDB.
Star crbug.com/1011533 to be notified of work on persisting granted permissions.
Drag and Drop
You can get files/directories from a drag-n-drop event:
voidmain() {
final $area = document.querySelector("#area") asDivElement;
$area.addEventListener("dragover", (event) => event.preventDefault());
$area.addEventListener("drop", (event) async {
event.preventDefault();
final handles = awaitFileSystemAccess.fromDropEvent(event);
for (final handle in handles) {
print("<${handle.kind.name} name='${handle.name}' />");
}
});
}
Remove handle
Experimental and non-standard.
You can remove a file/directory directly from its handle, instead of using the handle of the parent directory:
FileSystemHandle handle;
if (handle.kind == FileSystemKind.file) {
final file = handle asFileSystemFileHandle;
print("handle is a file");
} elseif (handle.kind == FileSystemKind.directory) {
final directory = handle asFileSystemDirectoryHandle;
print("handle is a directory.");
}
How to compare FileSystemHandle(s)
DON'T compare using == operator or hashCode property:
FileSystemFileHandle a;
FileSystemFileHandle b;
if (a == b) {
print("will return false even when a and b represents the same file entry.");
}
DO compare using FileSystemHandle.isSameEntry:
voidmain() async {
FileSystemFileHandle a;
FileSystemFileHandle b;
if (await a.isSameEntry(b)) {
print("return true when a and b represents the same file entry.");
}
}
More
See examples in example/ folder to play with fun tools.
Origin Private File System
This is a storage endpoint private to the origin of the page. It contains files/directories within a "virtual disk"
chosen by the browser implementing this API. Files and directories may be written in a database or any other data
structure. You should not expect to find those files/directories as-this on the hard disk.
Get root directory
You can get a root directory of the origin private file system with:
Applies only within a Web Worker and Origin Private File System for now.
You can get an interface to synchronously read from and write to a file. This will create an exclusive lock on the file
associated with the file handle, until it is closed:
// Code executed within a Web Workervoidmain() async {
FileSystemDirectoryHandle root;
FileSystemFileHandle source = await root.getFileHandle("linux.iso");
FileSystemSyncAccessHandle src = await source.createSyncAccessHandle();
Uint8List buffer = Uint8List(src.getSize());
src.read(buffer);
src.close();
print(buffer);
}
Missing features
It's all good for now.
Known issues
You cannot store a FileSystemHandle into IndexedDB as-this. See issue #50621 for more. A workaround is implemented
in LightStorage within example/ folder.