Chunpeng Huo

Might be true. But you should not say that in public :D In that case, how ~/my-app/ is worse than ~/app/? :-)

I don't mind the project name change much. (`au2-app` might be a good candidate too) For the root component name, let's do ``, it's very clear. The `${projectname}-app` is not...

Current scaffolding is updated to use ES2017 by default, which has native async/await support.

There is nothing we can do in this repo, because currently Aurelia 2 npm packages dist files are not compiled to support IE11. @fkleuver has plan to provide IE11 compatible...

It's not only transpiling to es5, but also many polyfills for IE11. Especially Aurelia 2 uses reflect metadata APIs which is very new in JS standard.

> conditionally target one set of dist files That's bundler's responsibility. Yes, all bundlers have some kind of custom config to support that.

Replaced by #108

@bigopon is working on it https://github.com/aurelia/aurelia/tree/master/packages-tooling/vite-plugin

Solved by #108

Not right now, we want to keep this repo as small as possible before Aurelia 2 Beta (no timeline). Because of possible breaking change, we don't want to bring so...