Chunpeng Huo

There is no problem for TypeScript to understand that import without extname `.ts`, same as babel has no problem to understand any import without extname `.js`. If you saw some...

Oh, sorry, I miss read your issue. Send over a PR if you want to :)

npm has command to remove all existing versions. But you need to wait 24 hrs (some npmjs policy) before republish it under different npm user name. For safety, you'd better...

From my understanding, I don't think your `css.bind` is a correct Aurelia usage. We use ``` css="width: ${width}px; height: ${height}px;" ``` to do string interpolation, use ``` ``` to do...

Instead of using `{color: undefined}`, use a proper css value like `{color: 'inherit'}` or `{color: 'unset'}` can clean up the old value. That can normalise your problem on browsers.

I understand your point. My argument is that `undefined` is not a proper css value, all css values should be string. I think it's fragile to rely on Aurelia to...

I added that in codesandbox, but the tutorial has to be updated. @EisenbergEffect planed to rewrite the tutorial using codesandbox setup.

Your two aliases should be just one alias with two keys. I am surprised nodejs didn't complain about the duplicated object key (alias) in your webpack config.

aurelia-dialog v1 uses aurelia-loader (the abstration layer normalized module loaders) to load dynamic resources. v2 switched to native dynamic `import()` statement to simplify the code. This is indeed a breaking...

Please review the above cli PR (will be released in couple of days). This one can be closed.