feat: update dependencies - #2028

🏁 Script executed:

#!/bin/bash
# Check vite-plugin-dts version and verify API compatibility
cat unraid-ui/package.json | jq -r '.devDependencies["vite-plugin-dts"]'

# Search for other vite-plugin-dts usage patterns
rg -nC3 'vite-plugin-dts|from.*dts' unraid-ui/

Repository: unraid/api

Length of output: 863

🏁 Script executed:

cat -n unraid-ui/vite.config.ts | head -50

Repository: unraid/api

Length of output: 1921

🌐 Web query:

vite-plugin-dts 5.0.2 API configuration outDirs bundleTypes

💡 Result:

In vite-plugin-dts, there are no specific configuration options named outDirs or bundleTypes [1][2]. It appears these may be confused with other settings or older plugin versions: Regarding bundling types: The functionality to bundle all type declaration files into a single file is controlled by the rollupTypes option, not bundleTypes [1][2]. When set to true, the plugin uses @microsoft/api-extractor to perform the bundling [1][2]. Example usage: import dts from 'vite-plugin-dts'; export default defineConfig({ plugins: [dts({ rollupTypes: true })], }); Regarding output directories: The plugin does not provide an outDirs option. The output directory for declaration files is generally determined by your Vite build configuration (typically build.outDir) and the plugin's default behavior of following your source file structure [3][1]. If you need to restrict output, the plugin provides a strictOutput option (default: true), which ensures that generated declaration files remain within the configured outDir [2].

Citations:

• 1: https://app.unpkg.com/vite-plugin-dts@4.5.3/files/README.md
• 2: https://unpkg.com/vite-plugin-dts@4.2.1/README.md
• 3: https://www.npmjs.com/package/vite-plugin-dts

🌐 Web query:

vite-plugin-dts 5.0.2 changelog release notes

💡 Result:

vite-plugin-dts version 5.0.2 was released on June 1, 2026 [1][2][3]. As of the 5.x major release, the project has evolved into unplugin-dts [4]. While vite-plugin-dts remains available as a package, it is now maintained within the unplugin-dts repository [1][4]. The 5.0.2 update includes the following key changes: Bug Fixes: - Re-emits declarations when non-type files change during watch mode [5][6]. - Fixes a getResolvedModule error that occurred when bundling dts files outside of the src directory [5][6]. - Adds a.js extension to synthetic entry imports to support nodenext module resolution [5][6]. Additional Changes: - Version 5.0.2 also includes an internal update to bump the minimum Node.js requirement to version 20 or higher [3]. For users migrating or seeking the most versatile version of the plugin, the author recommends transitioning to the unplugin-dts package, which supports Vite, Rollup, Rolldown, Webpack, Rspack, and Esbuild [4].

Citations:

• 1: https://github.com/qmhc/unplugin-dts/blob/main/packages/vite-plugin-dts/CHANGELOG.md
• 2: https://www.npmjs.com/package/vite-plugin-dts
• 3: chore(deps): Bump vite-plugin-dts from 5.0.1 to 5.0.2 herokwon/framix#252
• 4: https://github.com/qmhc/unplugin-dts
• 5: https://npmx.dev/package-changelog/vite-plugin-dts/v/5.0.2
• 6: https://github.com/qmhc/unplugin-dts/releases/tag/unplugin-dts%401.0.2

🌐 Web query:

site:github.com vite-plugin-dts v5.0.2 API options

💡 Result:

In vite-plugin-dts version 5.x, the plugin core was migrated to unplugin-dts [1][2]. A primary breaking change in this version is the renaming of the rollupTypes option to bundleTypes [1]. Key API options for vite-plugin-dts v5.0.2 include: bundleTypes: A boolean (default: false) that enables type bundling. When set to true, it utilizes @microsoft/api-extractor to merge all declaration files into a single file [3]. tsconfigPath: A string used to specify the path to your tsconfig.json file. The plugin uses this to resolve include and exclude patterns [3][4]. outDir: Specifies the output directory for generated declaration files. This can be a string, an array of strings, or an object/array of objects to control module formats (e.g., { dir: 'dist', moduleFormat: 'esm' }) [4][5]. entryRoot: Overrides the root path of entry files, which is particularly useful in monorepo structures [4][5]. strictOutput: A boolean (default: true) that, when enabled, ignores generated declaration files that fall outside the specified outDir [4][5]. processor: Specifies the processing mode, accepting either 'ts' or 'vue' [4][5]. compilerOptions: Allows overriding TypeScript compilerOptions [4][5]. resolvers: An array for specifying custom resolvers [4][5]. For migration from version 4.x, note that the rollupTypes option has been removed in favor of bundleTypes [1]. Additionally, ensure that your project dependencies align with the updated requirements, as v5+ often requires peer dependencies like @microsoft/api-extractor and rollup [1].

Citations:

• 1: complexdatacollective/network-canvas-monorepo@73441ea
• 2: qmhc/unplugin-dts@2996858
• 3: https://github.com/qmhc/unplugin-dts/blob/main/docs/en/usage.md
• 4: https://github.com/qmhc/vite-plugin-dts
• 5: https://github.com/qmhc/unplugin-dts/tree/vite-plugin-dts%405.0.0

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.