This Vite build plugin allows you to inline all JavaScript and CSS resources directly into the final dist/index.html
file. By doing this, your enter web app can be embedded and distributed as a single HTML file.
Bundling your entire site into one file certainly isn't recommended for most situations.
However, this can be very handy for offline web applications--apps you can simply opeen the HTML file in your default web browser. This might include utilities, expert system tools, documentation, demos, and other situations where you want the full power of a web browser, without the need for a Cordova or Electron wrapper or the pain of normal application installation.
Web applications running from a local file have some browser security limitations:
- No ability to access external domains -- no images, no API calls, etc.
- Limited state management options -- no cookies, no
localStorage
. However, you can use the new FileSystem API, with user permission. - Some web features that require a secure context may not be available.
Here's an example vite.config.ts
file. The cssCodeSplit
option results in all CSS being emitted as a single file, which vite-plugin-singlefile
can then inline. The assetsInlineLimit
ensures that even very large assets are inlined in your JavaScript. The inlineDynamicImports
also ensures that as many resources as possible are inlined.
import { defineConfig } from "vite"
import vue from "@vitejs/plugin-vue"
import { viteSingleFile } from "vite-plugin-singlefile"
export default defineConfig({
plugins: [vue(), viteSingleFile()],
build: {
cssCodeSplit: false,
assetsInlineLimit: 100000000,
rollupOptions: {
inlineDynamicImports: true,
},
},
})
favicon
resources are not inlined by Vite, and this plugin doesn't do that either.- There may be other situations where referenced files aren't inlined by Vite and aren't caught by this plugin either. I've done little testing so far, I just wanted to get this out there first.
- This is my first Vite and first Rollup plugin. I have no idea what I'm doing. PRs welcome.
- This doesn't remove the build artifacts from the
dist
folder, it just embeds them in theindex.html
. You can ignore the extra files. I'd be open to a PR to remove the recognized files so thedist
folder is cleaner, especially if there's a way to just prevent them from being written in the first place (i.e., not having to delete the files).
yarn add vite-plugin-singlefile -D
or npm i vite-plugin-singlefile -D
MIT