Ben Newman

@linegel As @crapthings mentioned above, the [SWC](https://swc.rs/) project aims to be a drop-in replacement for [Babel](https://babeljs.io/) (or at least as much of a drop-in replacement as possible when using a...

We're definitely open to exploring opportunities for using HTTP/2, though I suspect response multiplexing will be more impactful than server push, given that server push needs to know what resources...

This should be pretty straightforward, I think.

If you run `meteor update --release 1.6.2-beta.20`, you should get a lot more insight into what's happening during `_buildLocalPackages`.

The basic trick to tree-shaking is to prune unused exports (by removing some identifiers from `export` declarations) and then run a generic dead code elimination tool (such as UglifyJS) to...

This would be super awesome! I think the main complexities will be dealing with multi-container deployments, and maintaining security.

Given that browser bugs are generally not intentional, the `force` attribute seems reasonable, since the browser may believe it supports a module, according to some previous specification of what the...

It seems preferable to perform at most one HTTP request, if possible. Including the requested version and the browser's current version of the module in that request should be adequate,...

I think the decision to forbid `export default from` is a bug in the spec text, and in general I am opposed to introducing syntax gotchas like this one. Both...

@robertsmit Can you share the code for your field policy (including `read`, `merge`, and `keyArgs`) and `fetchMore` call?