-
-
Notifications
You must be signed in to change notification settings - Fork 37.1k
more ways of getting files #49757
Copy link
Copy link
Closed as not planned
Labels
feature requestIssues requesting new Node.js features.Issues requesting new Node.js features.fsIssues and PRs related to file-system APIs and the fs module.Issues and PRs related to file-system APIs and the fs module.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues and PRs marked stale due to inactivity and scheduled for automatic closure.
Description
Activity
Metadata
Metadata
Assignees
Labels
feature requestIssues requesting new Node.js features.Issues requesting new Node.js features.fsIssues and PRs related to file-system APIs and the fs module.Issues and PRs related to file-system APIs and the fs module.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues and PRs marked stale due to inactivity and scheduled for automatic closure.
What is the problem this feature will solve?
it's kind of a #developer-pain that
fs.openAsBlob(aka: fs.openAsBlobSync)Blobinstead ofFiles and therefore lacks a file name and lastModified. So upgrading them to a File requires figuring out more stuff yourself.What is the feature you are proposing to solve the problem?
That we add:
fs.openAsFilefs.openAsFileSyncfs.openAsBlobSync(fs: fixfs.openAsBlob, addfs.openAsBlobSyncandfsPromises.openAsBlob#49759)What alternatives have you considered?
Only workaround today is to do:
would be a heck a lot easier if i could just do:
and there is no way of getting around it cuz the async openAsBlob is the only thing you can work with. which makes your own code having to be async as well.