design-reviews#340: Import maps

Opened Feb 5, 2019

今日はTAG！

I'm requesting a TAG review of:

Name: Import maps
Specification URL: no real spec yet; some work in progress at 1, 2, 3
Explainer, Requirements Doc, or Example code: https://github.com/WICG/import-maps/blob/master/README.md
Tests: Tentative tests in progress at https://chromium-review.googlesource.com/c/chromium/src/+/1449072
Primary contacts: @domenic, @hiroshige-g, @nyaxt

Further details (optional):

Relevant time constraints or deadlines: we hope to do an origin trial in Chromium within the month.
I have read and filled out the Self-Review Questionnare on Security and Privacy. The assessment is here.
I have reviewed the TAG's API Design Principles

You should also know that...

Please read the following sections to head off common questions:

We'd prefer the TAG provide feedback as (please select one):

open issues in our Github repo for each point of feedback

(I hope this is done; in the past I've seen this preference disregarded a lot.)

Comment by @cynthia Feb 7, 2019 (See Github)

(I hope this is done; in the past I've seen this preference disregarded a lot.)

Noted. Apologies for the cases where we didn't acknowledge this preference.

Discussed May 8, 2019 (See Github)

[bump

Discussed May 15, 2019 (See Github)

Kenneth is not present.

Comment by @cynthia May 22, 2019 (See Github)

@kenchris and I went through this today. We're happy to see this feature move forward, and apologies that it took so long. We had some minor issues but none that would warrant blocking the feature from moving forward.

I in particular had some questions about the case that involved a long list of imports (and how to mitigate that with dependencies), and whether or not that is a good practice moving forward, which we also brought up in the modulepreload review. That should probably be treated as a separate bug report in some place; we'd appreciate feedback on where that should be filed.

Comment by @domenic May 22, 2019 (See Github)

I in particular had some questions about the case that involved a long list of imports (and how to mitigate that with dependencies), and whether or not that is a good practice moving forward, which we also brought up in the modulepreload review. That should probably be treated as a separate bug report in some place; we'd appreciate feedback on where that should be filed.

I'm not sure exactly what you mean, but it sounds like maybe you're concerned in general about applications that import a lot of files? Is the concern performance related, or syntax, or...? I think that's probably a general concern with the JavaScript module system, and so best filed at https://github.com/tc39/ecma262. But I may be misunderstanding.

Discussed Jun 19, 2019 (See Github)

Sangwhan: Kenneth and I should discuss in a separate call. Long discussion ahead.

Discussed Jul 3, 2019 (See Github)

Dan: Neither of them are here so we should bumpp this one too.

Discussed Jul 10, 2019 (See Github)

Sangwhan: i want to do a breakout with Kenneth about this.

Ken: we have had problem scheduling time...

[scheduling a breakout and deadline pushed

Comment by @kenchris Sep 10, 2019 (See Github)

Thanks for flying TAG!

#340: Import maps

Discussions