vite-plugin-dts 2.2.0 → 3.0.0-beta.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -1,326 +1,302 @@
1
- <h1 align="center">vite-plugin-dts</h1>
2
-
3
- <p align="center">
4
- A vite plugin that generates declaration files (<code>*.d.ts</code>) from <code>.ts(x)</code> or <code>.vue</code> source files when using vite in <a href="https://vitejs.dev/guide/build.html#library-mode">library mode</a>.
5
- </p>
6
-
7
- <p align="center">
8
- <a href="https://www.npmjs.com/package/vite-plugin-dts">
9
- <img src="https://img.shields.io/npm/v/vite-plugin-dts?color=orange&label=" alt="version" />
10
- </a>
11
- </p>
12
-
13
- <p align="center">
14
- <strong>English</strong> | <a href="./README.zh-CN.md">中文</a>
15
- </p>
16
-
17
- <p align="center"><strong>Notice: </strong><code>skipDiagnostics</code> option default to <code>false</code> since 1.7.0.</p>
18
-
19
- <br />
20
-
21
- ## Install
22
-
23
- ```sh
24
- pnpm add vite-plugin-dts -D
25
- ```
26
-
27
- ## Usage
28
-
29
- In `vite.config.ts`:
30
-
31
- ```ts
32
- import { resolve } from 'path'
33
- import { defineConfig } from 'vite'
34
- import dts from 'vite-plugin-dts'
35
-
36
- export default defineConfig({
37
- build: {
38
- lib: {
39
- entry: resolve(__dirname, 'src/index.ts'),
40
- name: 'MyLib',
41
- formats: ['es'],
42
- fileName: 'my-lib'
43
- }
44
- },
45
- plugins: [dts()]
46
- })
47
- ```
48
-
49
- In your component:
50
-
51
- ```vue
52
- <template>
53
- <div></div>
54
- </template>
55
-
56
- <script lang="ts">
57
- // using defineComponent for inferring types
58
- import { defineComponent } from 'vue'
59
-
60
- export default defineComponent({
61
- name: 'Component'
62
- })
63
- </script>
64
- ```
65
-
66
- ```vue
67
- <script setup lang="ts">
68
- // Need to access the defineProps returned value to
69
- // infer types although you never use the props directly
70
- const props = defineProps<{
71
- color: 'blue' | 'red'
72
- }>()
73
- </script>
74
-
75
- <template>
76
- <div>{{ color }}</div>
77
- </template>
78
- ```
79
-
80
- ## FAQ
81
-
82
- Here are some FAQ's and solutions.
83
-
84
- ### Missing some declaration files after build (before `1.7.0`)
85
-
86
- By default, the `skipDiagnostics` option is set to `true` which means type diagnostic will be skipped during the build process (some projects may have diagnostic tools such as `vue-tsc`). If there are some files with type errors which interrupt the build process, these files will not be emitted (declaration files won't be generated).
87
-
88
- If your project doesn't use type diagnostic tools, you can set `skipDiagnostics: false` and `logDiagnostics: true` to turn on diagnostic and logging features of this plugin. It will help you check the type errors during build and log error information to the terminal.
89
-
90
- ### Type error when using both `script` and `setup-script` in Vue component
91
-
92
- This is usually caused by using the `defineComponent` function in both `script` and `setup-script`. When `vue/compiler-sfc` compiles these files, the default export result from `script` gets merged with the parameter object of `defineComponent` from `setup-script`. This is incompatible with parameters and types returned from `defineComponent`, which results in a type error.
93
-
94
- Here is a simple [example](https://github.com/qmhc/vite-plugin-dts/blob/main/example/components/BothScripts.vue). You should remove the `defineComponent` which in `script` and export a native object directly.
95
-
96
- ### Type errors that are unable to infer types from packages in `node_modules`
97
-
98
- This is an existing issue when TypeScript infers types from packages located in `node_modules` through soft links (pnpm). Please refer to [this TypeScript issue](https://github.com/microsoft/TypeScript/issues/42873). The current workaround is to add `baseUrl` to your `tsconfig.json` and specify the `paths` for these packages:
99
-
100
- ```json
101
- {
102
- "compilerOptions": {
103
- "baseUrl": ".",
104
- "paths": {
105
- "third-lib": ["node_modules/third-lib"]
106
- }
107
- }
108
- }
109
- ```
110
-
111
- ## Options
112
-
113
- ```ts
114
- import type { ts, Diagnostic } from 'ts-morph'
115
- import type { LogLevel } from 'vite'
116
-
117
- interface TransformWriteFile {
118
- filePath?: string
119
- content?: string
120
- }
121
-
122
- export interface PluginOptions {
123
- /**
124
- * Depends on the root directory
125
- *
126
- * Defaults to 'root' property in your vite config
127
- */
128
- root?: string
129
-
130
- /**
131
- * Declaration files output directory
132
- *
133
- * Supports arrays to output to multiple directories
134
- *
135
- * Defaults to 'build.outDir' property in your vite config
136
- */
137
- outputDir?: string | string[]
138
-
139
- /**
140
- * Manually sets the root path of entry files
141
- *
142
- * The output path of each file will be calculated based on it
143
- *
144
- * Defaults to the shortest public path for all files
145
- */
146
- entryRoot?: string
147
-
148
- /**
149
- * Project init compilerOptions using by ts-morph
150
- *
151
- * @default null
152
- */
153
- compilerOptions?: ts.CompilerOptions | null
154
-
155
- /**
156
- * Project init tsconfig.json file path by ts-morph
157
- *
158
- * Plugin also resolves include and exclude files from tsconfig.json
159
- *
160
- * @default 'tsconfig.json'
161
- */
162
- tsConfigFilePath?: string
163
-
164
- /**
165
- * Set which paths should exclude when transform aliases
166
- *
167
- * If a regular expression, it will test the original import path directly
168
- *
169
- * @default []
170
- */
171
- aliasesExclude?: (string | RegExp)[]
172
-
173
- /**
174
- * Whether tp transform file name '.vue.d.ts' to '.d.ts'
175
- *
176
- * @default false
177
- */
178
- cleanVueFileName?: boolean
179
-
180
- /**
181
- * Whether to transform dynamic imports to static
182
- *
183
- * Force true when `rollupTypes` is effective
184
- *
185
- * eg. 'import('vue').DefineComponent' to 'import { DefineComponent } from "vue"'
186
- *
187
- * @default false
188
- */
189
- staticImport?: boolean
190
-
191
- /**
192
- * Specify a glob of files to include
193
- *
194
- * Defaults to 'include' property of the tsconfig.json
195
- */
196
- include?: string | string[]
197
-
198
- /**
199
- * Specify a glob of files to exclude
200
- *
201
- * Defaults to 'exclude' property of tsconfig.json and 'node_module/**' when empty
202
- */
203
- exclude?: string | string[]
204
-
205
- /**
206
- * Do not emit if content of file only includes 'export {}'
207
- *
208
- * @default true
209
- */
210
- clearPureImport?: boolean
211
-
212
- /**
213
- * Whether to generate types entry file
214
- *
215
- * When set to true, will add package.json `types` property to `${outputDir}/index.d.ts`
216
- *
217
- * Force true when `rollupTypes` is set
218
- *
219
- * @default false
220
- */
221
- insertTypesEntry?: boolean
222
-
223
- /**
224
- * Set to rollup declaration files after emit
225
- *
226
- * Power by `@microsoft/api-extractor`, it will start a new program which takes some time
227
- *
228
- * @default false
229
- */
230
- rollupTypes?: boolean
231
-
232
- /**
233
- * Whether to copy .d.ts source files to outputDir
234
- *
235
- * @default false
236
- * @remarks Prior to 2.0, the default was true
237
- */
238
- copyDtsFiles?: boolean
239
-
240
- /**
241
- * Whether to emit nothing when there is a diagnostic
242
- *
243
- * @default false
244
- */
245
- noEmitOnError?: boolean
246
-
247
- /**
248
- * Whether to skip Typescript diagnostics
249
- *
250
- * Skip type diagnostics means type errors will not interrupt the build process
251
- *
252
- * But source files with type errors will not be emitted
253
- *
254
- * @default false
255
- * @remarks Before 1.7, default was true
256
- */
257
- skipDiagnostics?: boolean
258
-
259
- /**
260
- * Customize Typescript lib folder path
261
- *
262
- * Relative path to root or an absolute path
263
- *
264
- * @default undefined
265
- */
266
- libFolderPath?: string
267
-
268
- /**
269
- * Specify the log level of plugin
270
- *
271
- * Defaults to base 'logLevel' property of your vite config
272
- */
273
- logLevel?: LogLevel
274
-
275
- /**
276
- * After emit diagnostic hook
277
- *
278
- * According to the length to judge whether there is any type error
279
- *
280
- * @default () => {}
281
- */
282
- afterDiagnostic?: (diagnostics: Diagnostic[]) => void | Promise<void>
283
-
284
- /**
285
- * Before declaration file be writed hook
286
- *
287
- * You can transform declaration file-path and content through it
288
- *
289
- * The file will be skipped when return exact false
290
- *
291
- * @default () => {}
292
- */
293
- beforeWriteFile?: (filePath: string, content: string) => void | false | TransformWriteFile
294
-
295
- /**
296
- * After build hook
297
- *
298
- * It wil be called after all declaration files are written
299
- *
300
- * @default () => {}
301
- */
302
- afterBuild?: () => void | Promise<void>
303
- }
304
- ```
305
-
306
- ## Contributors
307
-
308
- Thanks for all the contributions!
309
-
310
- <a href="https://github.com/qmhc/vite-plugin-dts/graphs/contributors">
311
- <img src="https://contrib.rocks/image?repo=qmhc/vite-plugin-dts" />
312
- </a>
313
-
314
- ## Example
315
-
316
- Clone and run the following script:
317
-
318
- ```sh
319
- pnpm run test:ts
320
- ```
321
-
322
- Then check `examples/ts/types`.
323
-
324
- ## License
325
-
326
- MIT License.
1
+ <h1 align="center">vite-plugin-dts</h1>
2
+
3
+ <p align="center">
4
+ A Vite plugin that generates declaration files (<code>*.d.ts</code>) from <code>.ts(x)</code> or <code>.vue</code> source files when using Vite in <a href="https://vitejs.dev/guide/build.html#library-mode">library mode</a>.
5
+ </p>
6
+
7
+ <p align="center">
8
+ <a href="https://www.npmjs.com/package/vite-plugin-dts">
9
+ <img src="https://img.shields.io/npm/v/vite-plugin-dts?color=orange&label=" alt="version" />
10
+ </a>
11
+ </p>
12
+
13
+ **English** | [中文](./README.zh-CN.md)
14
+
15
+ ## Install
16
+
17
+ ```sh
18
+ pnpm add vite-plugin-dts -D
19
+ ```
20
+
21
+ ## Usage
22
+
23
+ In `vite.config.ts`:
24
+
25
+ ```ts
26
+ import { resolve } from 'path'
27
+ import { defineConfig } from 'vite'
28
+ import dts from 'vite-plugin-dts'
29
+
30
+ export default defineConfig({
31
+ build: {
32
+ lib: {
33
+ entry: resolve(__dirname, 'src/index.ts'),
34
+ name: 'MyLib',
35
+ formats: ['es'],
36
+ fileName: 'my-lib'
37
+ }
38
+ },
39
+ plugins: [dts()]
40
+ })
41
+ ```
42
+
43
+ In your component:
44
+
45
+ ```vue
46
+ <template>
47
+ <div></div>
48
+ </template>
49
+
50
+ <script lang="ts">
51
+ // using defineComponent for inferring types
52
+ import { defineComponent } from 'vue'
53
+
54
+ export default defineComponent({
55
+ name: 'Component'
56
+ })
57
+ </script>
58
+ ```
59
+
60
+ ```vue
61
+ <script setup lang="ts">
62
+ // Need to access the defineProps returned value to
63
+ // infer types although you never use the props directly
64
+ const props = defineProps<{
65
+ color: 'blue' | 'red'
66
+ }>()
67
+ </script>
68
+
69
+ <template>
70
+ <div>{{ color }}</div>
71
+ </template>
72
+ ```
73
+
74
+ ## FAQ
75
+
76
+ Here are some FAQ's and solutions.
77
+
78
+ ### Missing some declaration files after build (before `1.7.0`)
79
+
80
+ By default, the `skipDiagnostics` option is set to `true` which means type diagnostic will be skipped during the build process (some projects may have diagnostic tools such as `vue-tsc`). If there are some files with type errors which interrupt the build process, these files will not be emitted (declaration files won't be generated).
81
+
82
+ If your project doesn't use type diagnostic tools, you can set `skipDiagnostics: false` and `logDiagnostics: true` to turn on diagnostic and logging features of this plugin. It will help you check the type errors during build and log error information to the terminal.
83
+
84
+ ### Type error when using both `script` and `setup-script` in Vue component (before `3.0.0`)
85
+
86
+ This is usually caused by using the `defineComponent` function in both `script` and `setup-script`. When `vue/compiler-sfc` compiles these files, the default export result from `script` gets merged with the parameter object of `defineComponent` from `setup-script`. This is incompatible with parameters and types returned from `defineComponent`, which results in a type error.
87
+
88
+ Here is a simple [example](https://github.com/qmhc/vite-plugin-dts/blob/main/examples/vue/components/BothScripts.vue). You should remove the `defineComponent` which in `script` and export a native object directly.
89
+
90
+ ### Type errors that are unable to infer types from packages in `node_modules`
91
+
92
+ This is an existing issue when TypeScript infers types from packages located in `node_modules` through soft links (pnpm). Please refer to [this TypeScript issue](https://github.com/microsoft/TypeScript/issues/42873). The current workaround is to add `baseUrl` to your `tsconfig.json` and specify the `paths` for these packages:
93
+
94
+ ```json
95
+ {
96
+ "compilerOptions": {
97
+ "baseUrl": ".",
98
+ "paths": {
99
+ "third-lib": ["node_modules/third-lib"]
100
+ }
101
+ }
102
+ }
103
+ ```
104
+
105
+ ## Options
106
+
107
+ ```ts
108
+ import type ts from 'typescript'
109
+ import type { LogLevel } from 'vite'
110
+
111
+ interface TransformWriteFile {
112
+ filePath?: string
113
+ content?: string
114
+ }
115
+
116
+ export interface PluginOptions {
117
+ /**
118
+ * Specify root directory
119
+ *
120
+ * By Default it base on 'root' of your Vite config, or `process.cwd()` if using Rollup
121
+ */
122
+ root?: string
123
+
124
+ /**
125
+ * Specify declaration files output directory
126
+ *
127
+ * Can be specified a array to output to multiple directories
128
+ *
129
+ * By Default it base on 'build.outDir' of your Vite config, or `outDir` of tsconfig.json if using Rollup
130
+ */
131
+ outDir?: string | string[]
132
+
133
+ /**
134
+ * Manually set the root path of the entry files, useful in monorepo
135
+ *
136
+ * The output path of each file will be calculated base on it
137
+ *
138
+ * By Default it is the smallest public path for all files
139
+ */
140
+ entryRoot?: string
141
+
142
+ /**
143
+ * Specify a CompilerOptions to override
144
+ *
145
+ * @default null
146
+ */
147
+ compilerOptions?: ts.CompilerOptions | null
148
+
149
+ /**
150
+ * Specify tsconfig.json path
151
+ *
152
+ * Plugin also resolve include and exclude files from tsconfig.json
153
+ *
154
+ * By default plugin will find config form root if not specify
155
+ */
156
+ tsconfigPath?: string
157
+
158
+ /**
159
+ * Set which paths should exclude when transform aliases
160
+ *
161
+ * @default []
162
+ */
163
+ aliasesExclude?: (string | RegExp)[]
164
+
165
+ /**
166
+ * Whether transform file name '.vue.d.ts' to '.d.ts'
167
+ *
168
+ * @default false
169
+ */
170
+ cleanVueFileName?: boolean
171
+
172
+ /**
173
+ * Whether transform dynamic import to static
174
+ *
175
+ * Force `true` when `rollupTypes` is effective
176
+ *
177
+ * eg. `import('vue').DefineComponent` to `import { DefineComponent } from 'vue'`
178
+ *
179
+ * @default false
180
+ */
181
+ staticImport?: boolean
182
+
183
+ /**
184
+ * Manual set include glob
185
+ *
186
+ * By Default it base on 'include' option of the tsconfig.json
187
+ */
188
+ include?: string | string[]
189
+
190
+ /**
191
+ * Manual set exclude glob
192
+ *
193
+ * By Default it base on 'exclude' option of the tsconfig.json, be 'node_module/**' when empty
194
+ */
195
+ exclude?: string | string[]
196
+
197
+ /**
198
+ * Whether remove those `import 'xxx'`
199
+ *
200
+ * @default true
201
+ */
202
+ clearPureImport?: boolean
203
+
204
+ /**
205
+ * Whether generate types entry file
206
+ *
207
+ * When `true` will from package.json types field if exists or `${outDir}/index.d.ts`
208
+ *
209
+ * Force `true` when `rollupTypes` is effective
210
+ *
211
+ * @default false
212
+ */
213
+ insertTypesEntry?: boolean
214
+
215
+ /**
216
+ * Set whether rollup declaration files after emit
217
+ *
218
+ * Power by `@microsoft/api-extractor`, it will start a new program which takes some time
219
+ *
220
+ * @default false
221
+ */
222
+ rollupTypes?: boolean
223
+
224
+ /**
225
+ * Bundled packages for `@microsoft/api-extractor`
226
+ *
227
+ * @default []
228
+ * @see https://api-extractor.com/pages/configs/api-extractor_json/#bundledpackages
229
+ */
230
+ bundledPackages?: string[]
231
+
232
+ /**
233
+ * Whether copy .d.ts source files into `outDir`
234
+ *
235
+ * @default false
236
+ * @remarks Before 2.0 it defaults to true
237
+ */
238
+ copyDtsFiles?: boolean
239
+
240
+ /**
241
+ * Specify the log level of plugin
242
+ *
243
+ * By Default it base on 'logLevel' option of your Vite config
244
+ */
245
+ logLevel?: LogLevel
246
+
247
+ /**
248
+ * Hook after diagnostic emitted
249
+ *
250
+ * According to the length to judge whether there is any type error
251
+ *
252
+ * @default () => {}
253
+ */
254
+ afterDiagnostic?: (diagnostics: readonly ts.Diagnostic[]) => void | Promise<void>
255
+
256
+ /**
257
+ * Hook before each declaration file is written
258
+ *
259
+ * You can transform declaration file's path and content through it
260
+ *
261
+ * The file will be skipped when return exact `false`
262
+ *
263
+ * @default () => {}
264
+ */
265
+ beforeWriteFile?: (filePath: string, content: string) => void | false | TransformWriteFile
266
+
267
+ /**
268
+ * Hook after built
269
+ *
270
+ * It wil be called after all declaration files are written
271
+ *
272
+ * @default () => {}
273
+ */
274
+ afterBuild?: () => void | Promise<void>
275
+ }
276
+ ```
277
+
278
+ ## Contributors
279
+
280
+ Thanks for all the contributions!
281
+
282
+ <a href="https://github.com/qmhc/vite-plugin-dts/graphs/contributors">
283
+ <img src="https://contrib.rocks/image?repo=qmhc/vite-plugin-dts" />
284
+ </a>
285
+
286
+ ## Example
287
+
288
+ Clone and run the following script:
289
+
290
+ ```sh
291
+ pnpm run test:ts
292
+ ```
293
+
294
+ Then check `examples/ts/types`.
295
+
296
+ Also Vue and React cases under `examples`.
297
+
298
+ A real project using this plugin: [Vexip UI](https://github.com/vexip-ui/vexip-ui).
299
+
300
+ ## License
301
+
302
+ MIT License.