---
title: "@pitlane/assets/vite-plugin"
description: ""
url: "https://pitlane.tools/package/assets/vite-plugin"
---

# @pitlane/assets/vite-plugin

## Interfaces

- [AssetEntryRegistration](https://pitlane.tools/package/assets/vite-plugin/interface/AssetEntryRegistration.md). Browser entries declared by one server module's development transform.
- [AssetsPluginApi](https://pitlane.tools/package/assets/vite-plugin/interface/AssetsPluginApi.md). Available on the resolved plugin named `pitlane-assets`.
- [AssetsPluginOptions](https://pitlane.tools/package/assets/vite-plugin/interface/AssetsPluginOptions.md). Options for [assets](https://pitlane.tools/package/assets/vite-plugin/function/assets.md). `remix()` from `@pitlane/vite-plugin-remix` accepts them as `remix({ assets })`.

## Variables

- [ASSETS\_MANIFEST\_FILE](https://pitlane.tools/package/assets/vite-plugin/variable/ASSETS_MANIFEST_FILE.md). The manifest module a build writes at the root of each server environment's output directory. The server chunks that read the manifest import this file by a relative path, so a host that deploys a single module must bundle it in.

## Functions

- [assets](https://pitlane.tools/package/assets/vite-plugin/function/assets.md). The Vite plugins that give `@pitlane/assets` its manifest: they serve browser entries during `vite dev`, emit them in a build, and replace `@pitlane/assets/manifest` with the manifest of the current dev server or build. Setting `allowFiles` also enforces the browser boundary.