Skip to content

Commit 706ea20

Browse files
Update doc/design/proposal-ambient-loaders.md
Co-authored-by: Geoffrey Booth <456802+GeoffreyBooth@users.noreply.github.com>
1 parent 96ecc5e commit 706ea20

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

doc/design/proposal-ambient-loaders.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ The reason for that is an attempt to keep loaders as isolated as possible, to al
1616

1717
If loaders cannot generally influence each other, we could have a subset of them do. Indeed, not all loaders affect the resolution so much that they are a requirement to followup loaders. We could have two levels of loaders:
1818

19-
- Ambient loaders would be defined via the `--ambient-loader <module>` flag. They would be loaded sequentially, and would affect the resolution of all followup loaders.
19+
- Ambient loaders would be defined via the `--ambient-loader <module>` flag. They would be loaded sequentially and would affect the resolution of all subsequent ambient and regular loaders.
2020

2121
- Regular loaders would be defined via the `--loader <module>` flag. They would be loaded in parallel (at least conceptually). Because they’d only be loaded after the ambient loaders have finished evaluating, their resolution would be affected by ambient loaders.
2222

0 commit comments

Comments
 (0)