Skip to content

meta: planning for promisified fs and crypto #15413

Closed
@jasnell

Description

@jasnell

This is largely a heads up.

Yesterday I posted a poll to Twitter asking how users felt about core providing a promisified API for fs... with two hours remaining in the poll, this is the result:

image

It's clear that there is strong demand. I have heard from many who like the fact that util.promisify() is now a thing but feel that being forced to use it in order to get promisified core APIs is not a very ergonomic experience, and while many are using Promise-wrapper libraries to achieve this, there is obviously a strong sentiment towards having these provided by core itself.

Therefore, I will be actively working towards the goal of providing Promise-enabled versions of all of the fs and crypto APIs in core. This will not be done all at once as there are a number of changes that may be required. For the crypto APIs, I will likely wait until async-iterators have landed with V8 6.2.

I understand that not everyone is in love with Promises and not everyone wants to use them. The changes I have in mind will not touch the existing APIs, so anyone who wants to ignore the Promisified versions will be able to.

Metadata

Metadata

Assignees

No one assigned

    Labels

    cryptoIssues and PRs related to the crypto subsystem.fsIssues and PRs related to the fs subsystem / file system.promisesIssues and PRs related to ECMAScript promises.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions