Git Product home page Git Product logo

unplugin-vue-cssvars's Introduction

unplugin-vue-cssvars

🌀 A vue plugin that allows you to use vue3's CSSVars feature in css files

English | 中文

Feature

  • 🧩 It is a function extension of vue
  • 🌈 Compatible with multiple bundled platforms(vite、webpack)
  • ⛰ Support css, sass, scss, less, stylus
  • ⚡ light and fast

Core Strategy

1.When using the development server, unplugin-vue-cssvars will analyze the referenced css file from the component, and inject styles in the transformation code of @vitejs/plugin-vue 2.When building, unplugin-vue-cssvars will analyze the referenced css file from the component and inject it into sfc, don't worry about generating redundant code, packaging tools (such as vite) will automatically handle it.

Install

npm i unplugin-vue-cssvars -D

Or

yarn add unplugin-vue-cssvars -D

Or

pnpm add unplugin-vue-cssvars -D

Usage

  1. use plugin and set options
Vite
// vite.config.ts
import { defineConfig } from 'vite'
import { viteVueCSSVars } from 'unplugin-vue-cssvars'
import vue from '@vitejs/plugin-vue'
import type { PluginOption } from 'vite'
export default defineConfig({
  plugins: [
    vue(),
    viteVueCSSVars({
      include: [/.vue/],
      includeCompile: ['**/**.scss'],
      server: false,
    }) as PluginOption,
  ],
})

Rollup
// rollup.config.js
import { rollupVueCSSVars } from 'unplugin-vue-cssvars'
export default {
  plugins: [
    rollupVueCSSVars(/* options */),
  ],
}

Webpack
// webpack.config.js
module.exports = {
  /* ... */
  plugins: [
    require('unplugin-vue-cssvars').webpackVueCSSVars({ /* options */ }),
  ],
}

Vue CLI
// vue.config.js
module.exports = {
  configureWebpack: {
    plugins: [
      require('unplugin-vue-cssvars').webpackVueCSSVars({ /* options */ }),
    ],
  },
}

ESBuild
// esbuild.config.js
import { build } from 'esbuild'
import { esbuildVueCSSVars } from 'unplugin-vue-cssvars'

build({
  plugins: [esbuildVueCSSVars(/* options */)],
})
  1. use v-bind-m
// foo.css
.foo{
   color: v-bind-m(fontColor)
}
  1. use alias
    For example you have the following project structure:

img.png

// App.vue
<template>
 <div class="scss">
   app
 </div>
</template>

<style lang="scss" scoped>
@import '@/assets/scss/mixin';
</style>

Then you can configure like this

// vite.config.ts
import { resolve } from 'path'
import { defineConfig } from 'vite'
import vue from '@vitejs/plugin-vue'
import { viteVueCSSVars } from '../dist'
export default defineConfig({
  resolve: {
    alias: {
      '@': resolve(__dirname, './src'),
    },
  },
  plugins: [
    vue(),
    viteVueCSSVars({
      include: [/.vue/],
      includeCompile: ['**/**.scss'],
      alias: {
        '@': resolve(__dirname, './src'),
      },
    }),
  ],
})

Option

export interface Options {
   /**
    * Provide path which will be transformed
    * @default process.cwd()
    */
   rootDir?: string
   
   /**
    * RegExp or glob to match files to be transformed
    */
   include?: FilterPattern

   /**
    * RegExp or glob to match files to NOT be transformed
    */
   exclude?: FilterPattern

   /**
    * unplugin-vue-cssvars depends on the vue compiler,
    * there may be duplicate css after packaging, here we clear it
    */
   revoke?: boolean

   /**
    * Specify the file to be compiled, for example,
    * if you want to compile scss, then you can pass in ['** /**.sass']
    * @property { ['** /**.css', '** /**.less', '** /**.scss', '** /**.sass', '** /**.styl'] }
    * @default ['** /**.css']
    */
   includeCompile?: Array<string>
   
   /**
    * Flag whether to start with server at development time,
    * because unplugin-vue-cssvars uses different strategies for building and server development
    * If it is not passed in vite, unplugin-vue-cssvars will automatically 
    * recognize the command of config to determine the server value
    * @default true
    */
   server?: boolean

   /**
    * alias
    * @default undefined
    */
   alias?: Record<string, string>
}

Tips

● Rules When Transforming Analysis

  1. In sfc, if @import specifies a suffix, the conversion analysis will be performed according to the suffix file, otherwise the conversion analysis will be performed according to the lang attribute of the current script tag (default css)
  2. Rules in css: css files can only reference css files, and only files with css suffixes will be parsed.
  3. Rules in scss, less, stylus: scss, less, stylus files can refer to cssfiles, and correspondingscssorlessfiles orstylusfiles, Prioritize conversion analysis of files with preprocessor suffixes, if the file does not exist, analyze itscss` file

● Variable extraction rules in SFC

  1. For script setup, unplugin-vue-cssvars will extract all variables to match.
<script setup>
    const color = 'red'
</script>
  1. For composition api, unplugin-vue-cssvars will extract setup function return variables for matching.
<script>
 export default {
   setup(){
       const color = 'red'
       return {
          color
       }
   }
}
</script>
  1. For options api, unplugin-vue-cssvars will extract data function return variables for matching.
<script>
 export default {
   data(){
       const color = 'red'
       return {
          color
       }
   }
}
</script>
  1. For normal script, unplugin-vue-cssvars will extract all variables to match.
<script>
    const color = 'red'
</script>

● Variable conflict rules in SFC

  1. In sfc, there are options API and composition API, and all variables will be merged. If there are conflicts in variables, the syntax that appears later will take precedence (for example, if options API is written first and composition API is written later, composition API takes precedence).
  2. There are script setup, options api and composition api in sfc, all variables will be merged, if there is a variable conflict, script setup will take precedence
  3. Ordinary script in sfc will not exist at the same time as options api and composition api
  4. If the normal script exists in sfc, there must be script setup
  5. Common script and script setup variables in sfc will be merged, if there is a variable conflict, script setup will take precedence

● Priority after style injection

  1. Starting from sfc, analyze the css files referenced in the style tag, and in accordance with the order of references in the css files, they will be promoted in depth-first order and injected into sfc.
  2. After being injected into sfc, its priority is completely determined by the compiler of @vue/compiler-dom.

Thanks

unplugin-vue-cssvars's People

Contributors

baiwusanyu-c avatar dependabot[bot] avatar simon-he95 avatar faga295 avatar

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.