Skip to content

Update implementation status to reduce confusion #152

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 30, 2017
Merged

Update implementation status to reduce confusion #152

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 3 additions & 8 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ respect the [WHATWG Code of Conduct](https://wiki.whatwg.org/wiki/Code_of_Conduc

Section 15.2 of the [ES2015 specification](http://www.ecma-international.org/ecma-262/6.0/) describes the syntax for the new `import` and `export` declarations, but does not specify how modules are to be loaded. This repository consolidates work on the ECMAScript module loading semantics with the integration points of Web browsers, as well as Node.js.

The main spec is available at http://whatwg.github.io/loader, generated from the `index.bs` file.
The main spec is available at https://whatwg.github.io/loader, generated from the `index.bs` file.

## Building the spec

Expand Down Expand Up @@ -47,14 +47,9 @@ to start a watcher on `index.bs` that will update `index.html` as you edit.

### Implementation status

This spec will be implemented in several stages/milestones. See the [roadmap](https://github.com/whatwg/loader/blob/master/roadmap.md) for more details.
This spec is currently undergoing potentially-large redesigns (see [#147](https://github.com/whatwg/loader/issues/147) and [#149](https://github.com/whatwg/loader/issues/149)) and is not ready for implementations. You can see one possible way to break down the work in our old [roadmap](https://github.com/whatwg/loader/blob/master/roadmap.md) document, but that does not reflect the latest changes.

As the various milestones of the roadmap are completed, browsers will be able to implement them. See the following trackers for the current status of the main browsers:

* IE/Edge: [Under Consideration](https://status.modern.ie/moduleses6?term=modules)
* Firefox: [In progress](https://bugzilla.mozilla.org/show_bug.cgi?id=568953)
* Chrome: [In progress](https://code.google.com/p/v8/issues/detail?id=1569)
* Webkit: [Meta Bug](https://bugs.webkit.org/show_bug.cgi?id=147340)
Various browsers are implementing module syntax parsing and `<script type="module">` loading ([Firefox](https://bugzilla.mozilla.org/show_bug.cgi?id=568953), [Chrome](https://code.google.com/p/v8/issues/detail?id=1569), [WebKit](https://bugs.webkit.org/show_bug.cgi?id=147340), [Edge](https://blogs.windows.com/msedgedev/2016/05/17/es6-modules-and-beyond/)). However, none of them have begun work on the ideas prototyped here, since they are not ready for implementations yet.

### Feedback

Expand Down