npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@kvinc/vue-component-api-command-tool

v1.0.14

Published

Tool for changing vue-property-decorator to component-function-api

Downloads

3

Readme

诞生用途

用于更改vue-property-decorator到component-function-api的工具

背景介绍

由于Vue3的诞生, Vue的写法开始发生了变化,其中最引人注意的是Vue3推出的CompositionAPI,由于Vue2的以下两个特点:

  • Vue2采用的是options写法,简便但缺乏灵活性,可操作空间太低
  • Vue2由于过于依赖执行上下文,导致TS的支持度极差 Vue3推出的CompositionAPI极大程度上解决了以上的两个问题

在当前接手的项目中使用的是Vue2.x的TS语法,里面采用了vue-property-decorator的写法,在不升级到Vue3的前提下社区提供了@vue/composition-api包模拟了Vue3的写法, 在此条件下针对TS写法的Vue项目搭建了该工具,用于更改vue-property-decorator到component-function-api

Installation

  npm i @kvinc/vue-component-api-command-tool -g

or

  yarn add global @kvinc/vue-component-api-command-tool

Usage

项目根目录下执行以下命令

  vts2cfa

Options

这些是选项对象中的键

  • -v: 查看当前版本
  • -e: 传入入口文件夹, 以当前执行命令的目录为根目录, 默认src
  • -o: 传入转换好的文件夹名称, 以当前执行命令的目录为根目录, 默认src-out
  • -elimit: Error日志获取错误的信息的数量, 默认是1
  • -h: 查看命令行帮助

Environment

  "@typescript-eslint/eslint-plugin": "^4.29.3",
  "@typescript-eslint/parser": "^4.29.3",
  "@vue/cli-plugin-babel": "~4.5.0",
  "@vue/cli-plugin-eslint": "~4.5.0",
  "@vue/cli-plugin-router": "~4.5.0",
  "@vue/cli-plugin-typescript": "~4.5.0",
  "@vue/cli-plugin-vuex": "~4.5.0",
  "@vue/cli-service": "~4.5.0",
  "@vue/compiler-sfc": "^3.2.10",
  "eslint-plugin-prettier": "^3.4.1",
  "@vue/eslint-config-typescript": "^7.0.0",
  "eslint": "^6.7.2",
  "eslint-plugin-vue": "^7.17.0",
  "less": "^4.1.1",
  "less-loader": "7.3.0",
  "typescript": "~4.1.5",
  "vue-router": "~4.0.0",
  "vuex": "^4.0.2"
  "vue-loader": "latest"

TransformOptions

export default

exapm1

 export default class Name extends Vue {}

result

  defineComponent({})

name

example

  @Component({
    name: 'table'
  })
  export default class extends Vue{}
  name: 'table'

example2

  @Component({
    name: 'Table'
  })
  export default MixinTable class extends Vue{}

result

  name: 'Table'

data

example

  @Component({
    data() {
      return {
        name: 'name'
      }
    }
  })

result

  defineComponent({
    data() {
      return {
        name: 'name'
      }
    }
  })

example2

  class .... {
    [public | private | proctected] name: string = 'name'
  }

result

  defineComponent({
    setup() {
      let name: string = 'name'

      return {
        name
      }
    }
  })

example3

  class .... {
    [public | private | proctected] name: Array<unknown> = []
  }

result

  defineComponent({
    setup() {
      let name: Array<unknown> = reactive([])

      return {
        name
      }
    }
  })

props

example

  @Prop({ type: String, default: 'name', required: false })
  name: string

  // OR

  @Components({
    props: {
      name: {
        type: String,
        default: 'name',
        required: false
      }
    }
  })

result

  props: {
    name: {
      type: String,
      default: 'name',
      required: false
    }
  }

i.g. 同时存在两种Props的话会合并, 相同的名称@Prop会覆盖@Components

propSync

  @PropSync('sync', { default: String }) syncProps
  computed: {
    syncProps: {
      get() {
        return this.sync
      },
      set(value) {
        this.$emit('update:sync', value)
      }
    }
  }

computed

example

  get name() {
    return this.age
  }

  set name(value) {
    this.age = value
  }

result

  computed: {
    name: {
      getter() {
        return this.age
      },
      setter(value) {
        this.age = value
      }
    }
  }

example2

  @Component({
    computed: {
      name() {
        return this.age
      }
    }
  })

result

  computed: {
    name() {
      return this.age
    }
  }

watch

example

  @Watch('name')
  getName(value) {}

result

  watch: {
    name: function getName(value) {}
  }

example2

  @Component({
    watch: {
      name: function(value) {

      }
    }
  })

result

  watch: {
    getName(value) {}
  }

example3

  @Component({
    watch: {
      name: function(value) {

      }
    }
  })

  @Watch('name')
  getName(value) {}
  // 两种同时存在

result

  watch: {
    name: [function(value) {}, function getName(value) {}]
  }

example4

  @Component({
    watch: {
      name: 'getName'
    }
  })

result

   watch: {
    name: 'getName'
  }

example5

  @Watch('name', { deep: true })
  getName() {}

result

  methods: {
    getName() {}
  },
  watch: {
    handler: 'getName',
    deep: true
  }

ref

example

  @Ref('ref')
  name: string

result

  computed: {
    name() {
      const ref: string = this.$refs['ref']
      return this.$refs['ref']
    }
  }

mixins

example

  class xxx extends Mixins(TableMixin)

result

  mixins: [TableMixin]

example2

  @Component({
    mixins: [TableMixin2]
  })
  class xxx extends Mixins(TableMixin)

result

  mixins: [TableMixin, TableMixins2]

Hooks

example

  @Component({
    mounted() {}
  })

result

  mounted(){}

example2

  @Component({
    mounted() {
      console.log('mounted1')
    }
  })
  class extends Vue {
    mounted() {
      console.log('mounted2')
    }
  }

result

  mounted: [function() {
      console.log('mounted1')
    }
  }, function() {
      console.log('mounted2')
    }
  }]

example3

  beforeDetroy() {}
  destroyed() {}

result

  beforeUnmount() {}
  unmounted() {}

model

  @Model('change', {
    type: Array,
    default: () => []
  })
  imgUrls!: string[]
  model: {
    prop: 'imgUrls'
    event: 'change'
  },

emit

  @Emit('changeTrackerIds')
  changeTrackerIds(arg) {
    return this.trackIds
  }
  methods: {
    changeTrackerIds(arg) {
      this.$emit('changeTrackerIds', this.trackIds, arg);
    }
  }

filters / directives / components / render

原封不动的放回optionsAPI

TransitionVuex

State

  @State('value') stateValue: string
  computed: {
    stateValue() {
      const stateValue: string = this.$store.state['value']
      
      return stateValue
    }
  }

Mutation

  @Mutation('setRealTimeTestId') setRealTimeTestId
  setRealTimeTestId(...rest) {
    return this.$store.commit.apply(this.$store,['setRealTimeTestId'].concat(rest));
  }