Sven Sauleau

@MattIPv4 that sound right. I sent the header to my Chrome and it didn't fail. That said, I'm not sure how to check that it works

is there anything actionable here? we won't modify existing files because that would be a breaking change.

Copying my comment here: https://github.com/tc39/proposal-pipeline-operator/issues/123#issuecomment-387025644. FYI we are wanting to centralizing the implementation status on the future TC39 website: https://github.com/tc39/tc39-web-draft. Tracking will be easier.

> HNY! Fixed the first notebook... bundle.run is not very reliable. What's the issue you're seeing on bundle.run?

it means that your webserver doesn't set the proper mime type when serving the wasm file. You should consider upgrading to the latest version

The `case` is just a list of statements and isn't providing a real scope (AFAIK). The following code works: ```js switch (myVar.val) { case 0: alert('MyVar.val is 0'); break; case...

@aaronang With ES2015 we need to transpile `let` to `var` and emulate a scoping in some cases. This issue occurs during the transformation.

The issue seems to come from `scope.rename` ([Renamer](https://github.com/babel/babel/blob/7.0/packages/babel-traverse/src/scope/lib/renamer.js)). Which in the following example also rename the switch discriminant: ```js let v = 0; switch (v) { case 0: let v...

Seems like the [try/catch arround the JSON parse](https://github.com/babel/babel/blob/7.0/packages/babel-register/src/cache.js#L49) to avoid such issues doesn't work :thinking:

If the goal is to reduce the size of the final binary I guess you could just replace the func with an empty one (with no code). Otherwise you'll need...