New issue
Advanced search Search tips

Issue 5563 link

Starred by 6 users

Issue metadata

Status: Fixed
Owner:
Closed: Dec 2017
Cc:
Components:
HW: ----
NextAction: ----
OS: ----
Priority: 3
Type: Bug

Blocking:
issue 1569



Sign in to add a comment

Write a test for "late" module linking with export * + import *

Project Member Reported by adamk@chromium.org, Oct 25 2016

Issue description

We currently don't have a test where:

1. On the first import of a module containing an "export *", the export * need not be fully-expanded because there is no "import *"
2. Another "top-level" module is later loaded into the same native context, and does request access to the module namespace object of the "export *"-exporting module.
 

Comment 1 by adamk@chromium.org, Oct 25 2016

Here is such a test case, which currently works with d8, but which we don't currently have good test-running infrastructure for:

foo.js:
import {y as x} from "bar.js";
export let y = 43;
export let z = 44;
print(x);

baz.js:
import * as bar from "bar.js";
print(Object.keys(bar));
print(bar.y);
print(bar.z);

bar.js:
export * from "foo.js";
print("bar");

When run under d8:

$ d8 --module foo.js --module baz.js
bar
43
y,z
43
44

The remaining work is to fit this into our test framework.
Labels: Priority-2

Comment 3 by neis@chromium.org, Apr 18 2017

Labels: -Priority-2 Priority-3
I can write a web-platform-test for this (maybe I already did, lost track).

Comment 4 by adamk@chromium.org, Dec 19 2017

Cc: -neis@chromium.org adamk@chromium.org
Owner: neis@chromium.org
neis, do you think we can close this as covered by WPT?

Comment 5 by neis@chromium.org, Dec 20 2017

Status: Fixed (was: Assigned)
Yeah.

Sign in to add a comment