\n\n## Install\n\n```sh\npnpm i -D vite-plugin-dts\n```\n\n## Usage\n\nIn `vite.config.ts`:\n\n```ts\nimport { resolve } from 'path'\nimport { defineConfig } from 'vite'\nimport dts from 'vite-plugin-dts'\n\nexport default defineConfig({\n build: {\n lib: {\n entry: resolve(__dirname, 'src/index.ts'),\n name: 'MyLib',\n formats: ['es'],\n fileName: 'my-lib',\n },\n },\n plugins: [dts()],\n})\n```\n\nBy default, the generated declaration files are following the source structure.\n\nFortunately, with the help of [API Extractor](https://api-extractor.com/), the plugin can bundle all types into a single file. You just need to install `@microsoft/api-extractor` and set `bundleTypes: true`:\n\n```ts\nexport default defineConfig({\n plugins: [dts({ bundleTypes: true })],\n})\n```\n\nWhen publishing both ESM and CommonJS, explicitly add `outDirs` entries with\n`moduleFormat: 'esm'` and `moduleFormat: 'cjs'`; Vite's JavaScript formats are not inferred.\nEach entry is bundled once and reused for both declaration formats. Configure conditional\n`exports.types` entries separately in `package.json`.\n\nIf you start with official Vite template, you should specify the `tsconfigPath`:\n\n```ts\nexport default defineConfig({\n plugins: [dts({ tsconfigPath: './tsconfig.app.json' })],\n})\n```\n\n## Documentation\n\nFor full documentation, please refer to [unplugin-dts](../../docs/en/usage.md).\n\n## Example\n\nA real project using this plugin: [Vexip UI](https://github.com/vexip-ui/vexip-ui).\n\n## License\n\nMIT License.\n","readmeFilename":"README.md"}
![\"version\"](\"https://img.shields.io/npm/v/vite-plugin-dts?color=orange&label=\")
\n \n \n ![\"license\"](\"https://img.shields.io/npm/l/vite-plugin-dts\")
\n \n