Skip to content

Commit 06be261

Browse files
authored
Clean up comments in entry.rs
Removed comments explaining async module handling.
1 parent 4b4c2ee commit 06be261

File tree

1 file changed

+0
-9
lines changed

1 file changed

+0
-9
lines changed

crates/next-core/src/next_edge/entry.rs

Lines changed: 0 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -13,15 +13,6 @@ pub async fn wrap_edge_entry(
1313
entry: ResolvedVc<Box<dyn Module>>,
1414
pathname: RcStr,
1515
) -> Result<Vc<Box<dyn Module>>> {
16-
// The wrapped module could be an async module, we handle that with the proxy
17-
// here. The comma expression makes sure we don't call the function with the
18-
// module as the "this" arg.
19-
// Turn exports into functions that are also a thenable. This way you can await the whole object
20-
// or exports (e.g. for Components) or call them directly as though they are async functions
21-
// (e.g. edge functions/middleware, this is what the Edge Runtime does).
22-
// Catch promise to prevent UnhandledPromiseRejectionWarning, this will be propagated through
23-
// the awaited export(s) anyway.
24-
//
2516
// The actual wrapper lives in the Next.js templates directory as `edge-wrapper.js`.
2617
// We use the template expansion helper so this code is kept in sync with other
2718
// Next.js runtime templates. This particular template does not have any imports

0 commit comments

Comments
 (0)