Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Propagate the AsyncContextFrame for dynamic imports #634

Merged
merged 1 commit into from
May 11, 2023

Conversation

jasnell
Copy link
Member

@jasnell jasnell commented May 10, 2023

No description provided.

@jasnell jasnell merged commit 9bd2f70 into main May 11, 2023
@kentonv kentonv deleted the jsnell/propagate-async-context-for-dynamic-import branch May 12, 2023 19:10
@kentonv
Copy link
Member

kentonv commented May 12, 2023

Hmm, are you sure this is what we want? We already explicitly run the dynamic import's global scope outside of the IoContext, in order to make it behave as it would if we had eagerly evaluated it at startup. By the same argument, shouldn't the async context behave as if the module were eagerly evaluated at startup, i.e. shouldn't it be empty?

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants