Aurelia 1.x Q&A - Sandbox at https://codesandbox.io/s/aurelia-javascript-sandbox-jnl6q85zq5
and I haven't done any localization yet either, so that's another thing that will force me to revisit the views
Well, I just wrote a long description in an issue about why we couldn't do that...but I'm thinking I might eat my words depending on how this upgrade goes. I'm a little upset about how it was handled. But, I'll try to be patient and we'll see what happens here. (We do use the TS compiler in our build now...we have a hybrid build process that uses Babel and TS together.)
Especially when the angular team is using it as well.
There's many reasons why it's awesome, types and annotations are a good thing
Would you think the same about it if it wasn't made by Microsoft ?
Transpiler
Don't think they do that now but it would be easy for them to
Code shaking?
and if you keep your core logic outside of it (in a separate library) and use typescript to transpile that, then I can deal with not using TS in aurelia code.
Did they get rid of the Babel runtime library ?
Been a while since I messed around with it
Over and out
How did that make it through testing?
Anyways, also means that until it's fixed there won't be
.d.ts files
Cause the
d.ts generator relies on them
And can be tree shaken
@ejsmith @EisenbergEffect Because Typescript is too far behind... I use the ES7 Async/Await support in Babel for everything client and server now, and it won't be supported until maybe Typescript v2, whenever that gets released. I guess that doesn't really impact Aurelia, but its the primary reason I am using Babel vs Typescript, the slow release schedule on full ES6 support.
@Alxandr so the analyzer knows when you do dynamic things and turns them into errors?
So, if you simply disallow doing
export let/var or export { foo } where foo is let/var (as opposed to const), which can easily be checked by a linter/babel/whatever, there is no way to shoot yourself in the foot
@joelcoxokc @rquast I am on MDL at the moment too, but certainly very, very interested in AI, and no issues with a subscription if it delivers what you are hinting at... If you don't need to have direct dependencies on external projects like Ionic or MDL, I think you should keep it in-house so you have full control over it.