Update roadmap (#92)

Author: GeoffreyBooth

README.md

@@ -30,10 +30,6 @@ This team is spun off from the [Modules team](https://github.com/nodejs/modules)
 
 - [x] Implement chaining as described in the [design](doc/design/proposal-chaining-middleware.md), where the `default<hookName>` becomes `next` and references the next registered hook in the chain. https://github.com/nodejs/node/pull/42623
 
-- [ ] Convert `resolve` from async to sync https://github.com/nodejs/node/pull/43363
-
-   - [ ] Add an async `resolve` to [`module`](https://nodejs.org/api/module.html) module
-
 - [ ] Add helper/utility functions (eg `getPackageType()`) to [`module`](https://nodejs.org/api/module.html) module
 
 - [ ] Move loaders off thread
@@ -42,4 +38,12 @@ This team is spun off from the [Modules team](https://github.com/nodejs/modules)
 
 - [ ] First-class support for [import maps](https://github.com/WICG/import-maps) that doesn’t require a custom loader.
 
+We hope that moving loaders off thread will allow us to preserve an async `resolve` hook while supporting the sync `import.meta.resolve` API. If that turns out to be unachievable, however, then:
+
+- [ ] Convert `resolve` from async to sync https://github.com/nodejs/node/pull/43363
+
+   - [ ] Add an async `resolve` to [`module`](https://nodejs.org/api/module.html) module
+   
+   - [ ] Consider an API for async operations before resolution begins, such as `preImport` https://github.com/nodejs/loaders/pull/89
+
 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.