• Contribution Guide
• 中文 README

Another style of writing Vue components.

• NPM version:  
• VSCode extension:  
• Check more details in docs:  

Category	Package	Version	Description
	@vue-vine/compiler		Compiler
	@vue-vine/language-server		Language Server
	@vue-vine/language-service		Language Service
	@vue-vine/vite-plugin		Vite Plugin
	@vue-vine/eslint-parser		ESLint Parser
	@vue-vine/eslint-plugin		ESLint Plugin
	@vue-vine/eslint-config		ESLint Config
	@vue-vine/nuxt		Nuxt Module
	vue-vine-tsc		TypeScript CLI checker
	create-vue-vine		Project starter CLI

# If you didn't install `@antfu/ni` yet, I highly recommend you to install it.
ni -D vue-vine

Use the plugin in vite.config.ts:

import { VineVitePlugin } from 'vue-vine/vite'

export default defineConfig({
  plugins: [
    // ...Other plugins
    VineVitePlugin()
  ],
})

Then add macro's type definition in tsconfig.json:

{
  "compilerOptions": {
    "types": ["vue-vine/macros"]
  }
}

For ESLint, install our custom ESLint config:

ni -D @vue-vine/eslint-config

You need to load the config into your flat configs.

import antfu from '@antfu/eslint-config'

// `VueVine()` returns a ESLint flat config
import VueVine from '@vue-vine/eslint-config'

export default antfu(
  {
    // First option is not Linter.FlatConfig,
    // it's a setting for antfu's config itself
  },
  ...VueVine(),
)

Finally, install the VSCode extension, search Vue Vine in the marketplace.

You can try the demo by following steps:

For development environment setup, first you need to get the VSCode extension bundle ouput.

git clone https://github.com/vue-vine/vue-vine.git
cd vue-vine
pnpm install

# Build all packages
pnpm run build

After building the VSCode extension, you can open the 'Debug' tab in VSCode, and start the 'Run Vine Extension' debug session.

Then start the Playground's dev server in another terminal session.

pnpm run play

1. You can see the demo in http://localhost:3333/.
2. You can inspect the transforming process in http://localhost:3333/__inspect/