ali
June 7, 2017, 7:03am
1
In Vue.js Template, it works fine. but I found in the package.json, the
"dependencies": {
"vue": "https://github.com/DanielRosenwasser/vue#540a38fb21adb7a7bc394c65e23e6cffb36cd867",
"vue-router": "https://github.com/DanielRosenwasser/vue-router#01b8593cf69c2a5077df45e37e2b24d95bf35ce3"
},
why not use the offical version ? after I changed the version to offical version, it not works, how to solve it ?
mythz
June 7, 2017, 3:15pm
2
It not working with the official version is exactly the reason why we’re referencing a working version from a member of the TypeScript team. We have no control of when the official Vue.js will be updated to support TypeScript properly but as soon as it does we’ll be updating the Vue.js template accordingly.
Here’s the best thread you can follow to track TypeScript support in Vue atm:
opened 04:33PM - 31 May 17 UTC
closed 02:54PM - 17 Oct 17 UTC
Hi Daniel,
This and the starter setup at https://github.com/Microsoft/TypeScrip… t-Vue-Starter are really cool. Thanks for putting the time in to these to make them clear and easy for newbies!
So the question I have is why must we use your branch, at a specific commit of VueJS? Are these features that play nice with typescript coming to the master branch? Having built a production single page app in ember that was dependent on a side branch like this, I know it can be done, but when you need or want a new feature you have to play this weird self-patching game that's kind of a drag. So I just wanted the scoop from you about why this is setup this way before I invest too deeply.