ViteDevServer Type — vite Architecture
Architecture documentation for the ViteDevServer type/interface in index.ts from the vite codebase.
Entity Profile
Dependency Diagram
graph TD 31fbe894_2070_4b11_3ffa_96b46ed3dfa9["ViteDevServer"] a423a1ed_f7d8_0eb5_9b8f_ddfa7fa8147e["index.ts"] 31fbe894_2070_4b11_3ffa_96b46ed3dfa9 -->|defined in| a423a1ed_f7d8_0eb5_9b8f_ddfa7fa8147e style 31fbe894_2070_4b11_3ffa_96b46ed3dfa9 fill:#6366f1,stroke:#818cf8,color:#fff
Relationship Graph
Source Code
packages/vite/src/node/server/index.ts lines 260–424
export interface ViteDevServer {
/**
* The resolved vite config object
*/
config: ResolvedConfig
/**
* A connect app instance.
* - Can be used to attach custom middlewares to the dev server.
* - Can also be used as the handler function of a custom http server
* or as a middleware in any connect-style Node.js frameworks
*
* https://github.com/senchalabs/connect#use-middleware
*/
middlewares: Connect.Server
/**
* native Node http server instance
* will be null in middleware mode
*/
httpServer: HttpServer | null
/**
* Chokidar watcher instance. If `config.server.watch` is set to `null`,
* it will not watch any files and calling `add` or `unwatch` will have no effect.
* https://github.com/paulmillr/chokidar/tree/3.6.0#api
*/
watcher: FSWatcher
/**
* WebSocket server with `send(payload)` method
*/
ws: WebSocketServer
/**
* An alias to `server.environments.client.hot`.
* If you want to interact with all environments, loop over `server.environments`.
*/
hot: NormalizedHotChannel
/**
* Rollup plugin container that can run plugin hooks on a given file
*/
pluginContainer: PluginContainer
/**
* Module execution environments attached to the Vite server.
*/
environments: Record<'client' | 'ssr' | (string & {}), DevEnvironment>
/**
* Module graph that tracks the import relationships, url to file mapping
* and hmr state.
*/
moduleGraph: ModuleGraph
/**
* The resolved urls Vite prints on the CLI (URL-encoded). Returns `null`
* in middleware mode or if the server is not listening on any port.
*/
resolvedUrls: ResolvedServerUrls | null
/**
* Programmatically resolve, load and transform a URL and get the result
* without going through the http request pipeline.
*/
transformRequest(
url: string,
options?: TransformOptions,
): Promise<TransformResult | null>
/**
* Same as `transformRequest` but only warm up the URLs so the next request
* will already be cached. The function will never throw as it handles and
* reports errors internally.
*/
warmupRequest(url: string, options?: TransformOptions): Promise<void>
/**
* Apply vite built-in HTML transforms and any plugin HTML transforms.
*/
transformIndexHtml(
url: string,
html: string,
originalUrl?: string,
): Promise<string>
/**
* Transform module code into SSR format.
*/
ssrTransform(
code: string,
inMap: SourceMap | { mappings: '' } | null,
url: string,
Defined In
Source
Frequently Asked Questions
What is the ViteDevServer type?
ViteDevServer is a type/interface in the vite codebase, defined in packages/vite/src/node/server/index.ts.
Where is ViteDevServer defined?
ViteDevServer is defined in packages/vite/src/node/server/index.ts at line 260.
Analyze Your Own Codebase
Get architecture documentation, dependency graphs, and domain analysis for your codebase in minutes.
Try Supermodel Free