j-nguyen/vue-template-generator

A small CLI Tool, designed to help create vue js templates.

VueJS Component Template Generator

A simple CLI tool, used to generate VueJS components. (Compatiable with VueJS 2+)

Major credits to these guys!: Forked from this repo

Installation

Global

npm install -g vue-template-generator

Local Package

npm install --save-dev vue-template-generator

Call either by going through the directory, ./node_modules/vue-template-generator/dist/vgc.js, or you can create a shortcut script through your own package.json.

Usage

Help

vgc help

Will give you the help commands.

Scaffolding

vgc scaffold example

Will generate a vue file: index, create, update, and edit.

index/edit/update/create.vue

<template>
</template>

<script>
export default {
  name: 'ExampleIndex',
  data() {
    return {
      
      }
  },
  created() {

  },
};
</script>

<style lang="scss" scoped>
</style>

Generating a single component

vgc component example src/component

Will generate a file named example.vue, in src/component.

example.vue

<template>
</template>

<script>
export default {
  name: 'ExampleIndex',
  data() {
    return {
      
      }
  },
  created() {

  },
};
</script>

<style lang="scss" scoped>
</style>

Credits

• Inspired by these guys

vue-template-generator's Issues

Add extra command arguments for scaffold and component

So right now the scaffold is as basic as it can be. Sometimes you may only want to create an index file only, but you still want to keep the folder structure.

I was thinking of adding a --except=index,show or --only=index type of deal. Not sure if I want to add in a package, just because. I would like to keep this short.

Setup Travis CI

Why

I would like to set-up CI for continual testing. This will ensure that our git repo is cleaned and ensured.

Fix typo on help

So I realized that the description for scaffold is wrong. It says it would create a delete.vue file, but it does not. It should say edit.

Separate master and develop branch

This would also be nice. Hopefully would make it easier for contributors to come in and help out. master is the stable release, and then we can work on develop together.

Add a CONTRIBUTOR and GUIDELINE file

This is for a good starting point when others want to help in. We should have a strict guideline, based on community thoughts to see what they're like (including myself).

Add Test Templating Engine

Would be nice to have a spec test engine, especially for jest.