Andreu Botella d3e107768a fix(modules): Immediately resolve follow-up dyn imports to a dyn imported module (#14958) ... When a dynamically imported module gets resolved, any code that comes after an await import() to that module will continue running. However, if that is the last code in the evaluation of another dynamically imported module, that second module will not resolve until the next iteration of the event loop, even though it does not depend on the event loop at all. When the event loop is being blocked by a long-running operation, such as a long-running timer, or by an async op that might never end, such as with workers or BroadcastChannels, that will result in the second dynamically imported module not being resolved for a while, or ever. This change fixes this by running the dynamic module loading steps in a loop until no more dynamic modules can be resolved.		2022-06-30 14:12:31 -04:00
..
integration	fix(modules): Immediately resolve follow-up dyn imports to a dyn imported module (#14958)	2022-06-30 14:12:31 -04:00
testdata	fix(modules): Immediately resolve follow-up dyn imports to a dyn imported module (#14958)	2022-06-30 14:12:31 -04:00
unit	fix(core): don't panic on non-existent cwd (#14957)	2022-06-30 14:12:31 -04:00
integration_tests.rs	chore: update copyright to 2022 (#13306)	2022-01-07 22:09:52 -05:00