From 6400d31a09e4ec28b579c79b43636627186a54aa Mon Sep 17 00:00:00 2001 From: Jacob Smith <3012099+JakobJingleheimer@users.noreply.github.com> Date: Thu, 5 May 2022 08:42:05 +0200 Subject: [PATCH] Move chaining todo item to "completed" --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 7529f02..571d2a7 100644 --- a/README.md +++ b/README.md @@ -30,12 +30,12 @@ This team is spun off from the [Modules team](https://github.com/nodejs/modules) 1. Refactor Node’s internal ESM loader to move its exception on unknown file types from within `resolve` (on detection of unknown extensions) to within `load` (if the resolved extension has no defined translator). +1. Implement chaining as described in the [design](doc/design/proposal-chaining-middleware.md), where the `default` becomes `next` and references the next registered hook in the chain. + ### In Progress ### Upcoming -1. Implement chaining as described in the [design](doc/design/proposal-chaining-middleware.md), where the `default` becomes `next` and references the next registered hook in the chain. - 1. Get a `load` return value of `format: 'commonjs'` to work, or at least error informatively. See https://github.com/nodejs/node/issues/34753#issuecomment-735921348. After this, we should get user feedback regarding the developer experience; for example, is too much boilerplate required? Should we have a separate `transform` hook? And so on. We should also investigate and potentially implement the [technical improvements](doc/use-cases.md#improvements) on our to-do list, such as the loaders-application communication channel and moving loaders into a thread.