typescript 2.0

[davidmoshal]

Hi, have been using vue-typescript with:

• Typescipt 1.8.10 and
• vue 1.26
  works great!!

So, am wondering if I can expect any issues upgrading to Typescript 2.0?

Thanks again for the awesome work on this project.

[davidmoshal]

How about Typescript 2.0 and Vue 2.0?
Any issues?

[davidmoshal]

So far it seems that vue-typescript:

• does work with Typescript 2.0 but
• does NOT work with Vue 2.0.

Seems like others have migrated to this project:
https://github.com/vuejs/vue-class-component

however, that project seems to have less functionality, for example:

• no @watch
• no @prop({require:true})

So, for the moment I'm staying with vue-typescript, hopefully @itsfrank will weigh in on this.
Note: Vue 2.0 removes 2-way sync.

Generally I'm not a fan of two-way sync, however, consise idioms for replacing sync with emit seem lacking at this time.

[HerringtonDarkholme]

Hi, av-ts is also an option to try here. So sorry to mention my own library here. But I hope more libraries competition may keep projects going better.

[davidmoshal]

@herrington would be great if you could describe a migration path, based on vue-typescripts readme.

[davidmoshal]

@HerringtonDarkholme - just came across this, was wondering what you think of it:

https://libraries.io/npm/vue-typescript-component

[HerringtonDarkholme]

@davidmoshal It might be more suitable for you because of its API resemblance to vue-typescript.

I don't want to brag here. So please refer to av-ts readme. I believe it has better extensibility and broader coverage.

[davidmoshal]

thanks, I moved the discussion to your repo, not fair to have it on @itsfrank 's site.

[davidmoshal]

Really wish you update this library, vue-class-component, and vue-property-decorator are such a mess. Actually I'm wondering if Vue 2.0 is worth the upgrade!

[itsfrank]

I will, I've been overwhelmed with grad school applications for the pas few months, I will find time to get this library feature complete for vue 1 at least and look into the work needed for vue 2 compatibility

[itsfrank]

Hopefully it should be updated by mid February

[davidmoshal]

Thanks!!
Then I'll stick with vue-typescript and Vue 1 for now.
Upgrading to Vue 2 isn't worth it if I have to drop typescript, and current typescript libraries aren't giving me the same functionality of vue-typescript.

Dave

[itsfrank]

Vue 2 removing broadcast was a huge mistake in my opinion, I personally much prefer vue 1

[davidmoshal]

Not the only huge mistake, vue-class-component (official typescript library) requires property definition twice!.

And this example (using vue-class-component, and vue-property decorator):

import { Component, prop } from 'vue-property-decorator';
import * as Vue from 'vue';

@Component({
  template: `
      <div>
        <div>{{propA}}</div>
        <button @click="propA +=1 ">click</button>
      </div>
  `
}) export class One extends Vue{
    @prop({
      default: 0
    })
    propA: number   
}

results in a huge error message:

[Vue warn]: Avoid mutating a prop directly since the value will be overwritten 
whenever the parent component re-renders. Instead, use a data or computed 
property based on the prop's value. Prop being mutated: "propA" 

WTF - you can't mutate local variables, why?

I'm wondering if a typescript-specific fork of Vue1 (called Vuet) would be a good idea?

[davidmoshal]

@itsfrank I publishing a project showing how to test vue-typescript components with WallabyJS.

https://github.com/davidmoshal/reactive-vue-typescript-testing

I've decided to stick with Vue 1.x for the forseable future, several of the Vue 2.0 design decisions are questionable.

More interested to me would have been to evolve Vue to support TSX templates.

[galprz]

Hey any news about the vue2 support?