Add explicit-javascript-compile-hints-file-based

[browser-specs-bot]

URL

https://wicg.github.io/explicit-javascript-compile-hints-file-based/

Rationale

• See repository: WICG/explicit-javascript-compile-hints-file-based
• Would-be shortname: explicit-javascript-compile-hints-file-based

Additional properties

{}

[browser-specs-bot]

Changes to index.json

This update would trigger the following changes in index.json:

Add spec (1)

{
  "url": "https://wicg.github.io/explicit-javascript-compile-hints-file-based/",
  "seriesComposition": "full",
  "shortname": "explicit-javascript-compile-hints-file-based",
  "series": {
    "shortname": "explicit-javascript-compile-hints-file-based",
    "currentSpecification": "explicit-javascript-compile-hints-file-based",
    "title": "Explicit JavaScript Compile Hints (File-based)",
    "shortTitle": "File-based",
    "nightlyUrl": "https://wicg.github.io/explicit-javascript-compile-hints-file-based/"
  },
  "nightly": {
    "url": "https://wicg.github.io/explicit-javascript-compile-hints-file-based/",
    "status": "Editor's Draft",
    "alternateUrls": [],
    "repository": "https://github.com/WICG/explicit-javascript-compile-hints-file-based",
    "sourcePath": "index.bs",
    "filename": "index.html"
  },
  "organization": "W3C",
  "groups": [
    {
      "name": "Web Platform Incubator Community Group",
      "url": "https://www.w3.org/community/wicg/"
    }
  ],
  "title": "Explicit JavaScript Compile Hints (File-based)",
  "source": "spec",
  "shortTitle": "File-based",
  "categories": [
    "browser"
  ],
  "standing": "good"
}

Tests

These changes look good! 😎

[dontcallmedom]

pending clarity from https://github.com/WICG/explicit-javascript-compile-hints-file-based/issues/10

[tidoust]

The specification was updated on 2025-02-26 (last reviewed on 2024-10-14).

[dontcallmedom]

Also the clarity on scope now has a documented answer https://github.com/WICG/explicit-javascript-compile-hints-file-based?tab=readme-ov-file#faq

[tidoust]

I note some worries expressed on the API design in standard positions (WebKit, Mozilla, but no strong pushback and some interest expressed. Overall, that seems now ok to add.

(FWIW, previous update comment was me testing the code in #1755)

[tidoust]

@browser-specs-bot pr