Await Asynchronous Module Imports #82
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For context, this issue was discovered using:
[email protected][email protected]This proposal fixes an issue when using
next-wswith App Router, wherein route handlers are compiled in a way such that the default export can be aPromisethat resolves to an object containing the actual handlers (re: named exports likeSOCKET). Whennext-wsimports a route module and tries to access properties like:module?.default?.routeModule?.userland?.SOCKETIt fails because
module.defaultcan be aPromise, not an object, resulting in the following error:This patch addressed that issue and
next-wsis now working brilliantly in my application. If the maintainers would prefer to address this in a different way, please just consider this a bug report. 😄And finally, thank you @apteryxxyz and the rest of the team for this project! ❤️