unplugin/docs/guide/plugin-conventions.md
yuyin 83d6795cee
docs: move docs (#369)
Co-authored-by: wawa0584 <60140118+WestonSeyler@users.noreply.github.com>
Co-authored-by: 三咲智子 Kevin Deng <sxzz@sxzz.moe>
2024-03-09 18:36:05 +01:00

815 B

aside lastUpdated
false false

Plugin Conventions

To have a better community and ecosystem, we encourage plugin authors to follow these conventions when creating unplugins.

  • Plugins powered by Unplugin should have a clear name with unplugin- prefix.
  • Include unplugin keyword in package.json.
  • To provide better DX, packages could export 2 kinds of entry points:
    • Default export: the returned value of createUnplugin function

      import UnpluginFeature from 'unplugin-feature'
      
    • Subpath exports: properties of the returned value of createUnplugin function for each bundler users

      import VitePlugin from 'unplugin-feature/vite'
      
    • Refer to unplugin-starter for more details about this setup.