Fix use of lexically scoped variables in modules

Their use may trigger setting c->requiresExecutionContext on the module
context, which is correct. However, unlike functions, modules at
instantiation time always have their context created ahead of time (to
populate imports). Therefore we must not emit call context creating byte
code instructions where we'd end up storing exports in the wrong place.

Change-Id: Id1264f1cfa6a7f1cd94247ffe71938bc9c5c3ff9
Fixes: QTBUG-70632
Reviewed-by: Lars Knoll <lars.knoll@qt.io>

1 files changed, 9 insertions, 0 deletions

diff --git a/tests/auto/qml/qjsengine/tst_qjsengine.cpp b/tests/auto/qml/qjsengine/tst_qjsengine.cpp
index f08d9a4798..92696c7e76 100644
--- a/tests/auto/qml/qjsengine/tst_qjsengine.cpp
+++ b/tests/auto/qml/qjsengine/tst_qjsengine.cpp
@@ -226,6 +226,7 @@ private slots:
 
     void importModule();
     void importModuleRelative();
+    void importModuleWithLexicallyScopedVars();
 
 public:
     Q_INVOKABLE QJSValue throwingCppMethod();
@@ -4394,6 +4395,14 @@ void tst_QJSEngine::importModuleRelative()
     }
 }
 
+void tst_QJSEngine::importModuleWithLexicallyScopedVars()
+{
+    QJSEngine engine;
+    QJSValue ns = engine.importModule(QStringLiteral(":/modulewithlexicals.mjs"));
+    QVERIFY2(!ns.isError(), qPrintable(ns.toString()));
+    QCOMPARE(ns.property("main").call().toInt(), 10);
+}
+
 QTEST_MAIN(tst_QJSEngine)
 
 #include "tst_qjsengine.moc"