README
¶
Vite Integration For Go
A Go module that lets you serve your Vue 3, React, or Svelte project from a Go-based web server. You build your project, tell Go where to find the dist/ directory, and the module figures out how to load the generated Vue application into a web page.
Installation
go get github.com/torenware/vite-go
To upgrade to the current version:
go get -u github.com/torenware/vite-go@latest
Getting It Into Your Go Project
The first requirement is to use ViteJS's tooling for your JavaScript code. The easiest thing to do is either to start out this way, or to create a new project and move your files into the directory that Vite creates. Using NPM:
npm create vite@latest
Using Yarn:
yarn create vite
Just answer the questions asked, and away you go.
You will need to position your source files and the generated dist/ directory so Go can find your project, the manifest.json file that describes it, and the assets that Vite generates for you. You may need to change your vite.config.js file (vite.config.ts if you prefer using Typescript) to make sure the manifest file is generated as well. Here's what I'm using:
/**
* @type {import('vite').UserConfig}
*/
import { defineConfig } from 'vite';
import vue from '@vitejs/plugin-vue';
export default defineConfig({
plugins: [vue()],
build: {
manifest: 'manifest.json',
rollupOptions: {
input: {
main: 'src/main.ts',
},
},
},
});
This, however, is more than you need. A minimal config file would be:
import { defineConfig } from 'vite'
import vue from '@vitejs/plugin-vue'
// https://vitejs.dev/config/
export default defineConfig({
plugins: [vue()],
build: {
manifest: "manifest.json",
},
})
The essential piece here is the vue plugin (or whatever plugin you need instead for React, Preact or Svelte) and the build.manifest line, since vite-go needs the manifest file to be present in order to work correctly.
Here's some sample pseudo code that uses the go 1.16+ embedding feature for the production build, and a regular disk directory (frontend in our case) as a development directory:
package main
import (
"embed"
"html/template"
"net/http"
vueglue "github.com/torenware/vite-go"
)
//go:embed "dist"
var dist embed.FS
var vueGlue *vueglue.VueGlue
func main() {
// This:
// Production configuration.
config := &vueglue.ViteConfig{
Environment: "production",
AssetsPath: "dist",
EntryPoint: "src/main.js",
Platform: "vue",
FS: frontend,
}
// OR this:
// Development configuration
config := &vueglue.ViteConfig{
Environment: "development",
AssetsPath: "frontend",
EntryPoint: "src/main.js",
Platform: "vue",
FS: os.DirFS("frontend"),
}
// Parse the manifest and get a struct that describes
// where the assets are.
glue, err := vueglue.NewVueGlue(config)
if err != nil {
//bail!
}
vueGlue = glue
// and set up your routes and start your server....
}
func MyHandler(w http.ResponseWriter, r *http.Request) {
// Now you can pass the glue object to an HTML template
ts, err := template.ParseFiles("path/to/your-template.tmpl")
if err != nil {
// better handle this...
}
ts.Execute(respWriter, vueGlue)
}
You will also need to serve your javascript, css and images used by your javascript code to the web. You can use a solution like http.FileServer, or the wrapper the library implements that configures this for you:
// using the standard library's multiplexer:
mux := http.NewServeMux()
// Set up a file server for our assets.
fsHandler, err := glue.FileServer()
if err != nil {
log.Println("could not set up static file server", err)
return
}
mux.Handle("/src/", fsHandler)
Some router implementations may alternatively require you to do something more like:
// chi router
mux := chi.NewMux()
...
mux.Handle("/src/*", fsHandler)
YMMV :-)
Templates
Your template gets the needed tags and links by declaring the glue object in your template and calling RenderTags on, as so:
<!doctype html>
<html lang='en'>
{{ $vue := . }}
<head>
<meta charset='utf-8'>
<title>Home - Vue Loader Test</title>
{{ if $vue }}
{{ $vue.RenderTags }}
{{ end }}
</head>
<body>
<div id="app"></div>
</body>
</html>
You should check that the glue ($vue in our example) is actually defined as I do here, since it will be nil unless you inject it into your template.
The sample program in examples/sample-program has much more detail, and actually runs.
Configuration
Vite-Go is fairly smart about your Vite Javascript project, and will examine your package.json file on start up. If you do not override the standard settings in your vite.config.js file, vite-go will probably choose to do the appropriate thing.
As mentioned above, a ViteConfig object must be passed to the NewVueGlue() routine, with anything you want to override. Here are the major fields and how to use them:
| Field | Purpose | Default Setting |
|---|---|---|
| Environment | What mode you want vite to run in. | development |
| FS | A fs.Embed or fs.DirFS | none; required. |
| JSProjectPath | Path to your Javascript files | frontend |
| AssetPath | Location of the built distribution directory | Production: dist |
| Platform | Any platform supported by Vite. vue and react are known to work; other platforms may work if you adjust the other configurations correctly. | Based upon your package.json settings. |
| EntryPoint | Entry point script for your Javascript | Best guess based on package.json |
| ViteVersion | Vite major version ("2" or "3") | Best guess based on your package.json file in your project. If you want to make sure, specify the version you want. |
| DevServerPort | Port the dev server will listen on; typically 3000 in version 2, 5173 in version 3 | Best guess based on version |
| DevServerDomain | Domain serving assets. | localhost |
| HTTPS | Whether the dev server serves HTTPS | false |
Caveats
This code is relatively new; in particular, there may be some configurations you can use in vite.config.js that won't work as I expect. If so: please open an issue on Github. I've posted the code so people can see it, and try things out. I think you'll find it useful.
Copyright © 2022 Rob Thorne
Documentation
¶
Index ¶
Constants ¶
const ( DEFAULT_VITE_VERSION = "3" DEFAULT_PORT_V2 = "3000" DEFAULT_PORT_V3 = "5173" )
constants
Variables ¶
Functions ¶
This section is empty.
Types ¶
type JSAppParams ¶ added in v0.4.0
type JSAppParams struct {
JSHash string `json:"hash"`
ViteVersion string `json:"vite_version"`
ViteMajorVer string `json:"vite_major_version"`
PackageType string `json:"package_type"`
MajorVer string `json:"major_version,omitempty"`
EntryPoint string `json:"entry_point"`
HasTypeScript bool `json:"has_ts"`
IsVanilla bool `json:"is_vanilla,omitempty"`
VueVersion string `json:"vue_version,omitempty"`
ReactVersion string `json:"react_version,omitempty"`
PreactVersion string `json:"preact_version,omitempty"`
SvelteVersion string `json:"svelte_version,omitempty"`
LitVersion string `json:"lit_version,omitempty"`
}
type PackageJSON ¶ added in v0.3.2
type ViteConfig ¶ added in v0.1.0
type ViteConfig struct {
// FS is the filesystem where assets can be loaded.
FS fs.FS
// DevDefaults is best guess for defaults
DevDefaults *JSAppParams `json:"-"`
// Environment (development|production). In development mode,
// the package sets up hot reloading. In production, the
// package builds the Vue/Vuex production files and embeds them
// in the Go app.
Environment string
// JSProjectPath is where your JS project is relative to the
// root of your project. Default: frontend
JSProjectPath string
//AssetsPath relative to the JSProjectPath. Empty for dev, dist for prod
AssetsPath string
// "2" or "3". If not set, we try to guess by looking
// at package.json
ViteVersion string
// DevServerDomain is what domain the dev server appears on.
// Default is localhost.
DevServerDomain string
// DevServerPort is what port the dev server will appear on.
// Default depends upon the ViteVersion.
DevServerPort string
// HTTPS is whether the dev server is encrypted or not.
// Default is false.
HTTPS bool
// URLPrefix (/assets/ for prod, /src/ for dev)
URLPrefix string
// Platform (vue|react|svelte) is the target platform.
// Default is "vue"
Platform string
// Entry point: as configured in vite.config.js. Typically
// src/main.js or src/main.ts.
EntryPoint string
}
type ViteConfig passes info needed to generate the library's output.
func (*ViteConfig) SetDevelopmentDefaults ¶ added in v0.4.0
func (vc *ViteConfig) SetDevelopmentDefaults() error
func (*ViteConfig) SetProductionDefaults ¶ added in v0.4.1
func (vc *ViteConfig) SetProductionDefaults() error
type VueGlue ¶
type VueGlue struct {
// Environment. This controls whether the library will
// configure the host for hot updating, or whether it
// needs to configure loading of a dist/ directory.
Environment string
// Entry point for JS
MainModule string
// BaseURL is the base URL for the dev server.
// Default is http://localhost:5173
BaseURL string
// JS Dependencies / Vendor libs
Imports []string
// Bundled CSS
CSSModule []string
// Target JS Platform
Platform string
// A file system or embed that points to the Vue/Vite dist
// directory (production) or the javascript src directory
// (development)
DistFS fs.FS
// DevServer is the URI of the Vite development server
DevServer string
// JSProjectPath is the location of the JS project.
JSProjectPath string
// AssetPath is the relative path from the JSDirectory.
AssetPath string
// Debug mode
Debug bool
}
type VueGlue summarizes a manifest file, and points to the assets.
func NewVueGlue ¶
func NewVueGlue(config *ViteConfig) (*VueGlue, error)
NewVueGlue finds the manifest in the supplied file system and returns a glue object.
func ParseManifest ¶
ParseManifest imports and parses a manifest returning a glue object.
func (*VueGlue) DevServerRedirector ¶ added in v0.3.0
func (*VueGlue) FileServer ¶ added in v0.1.4
FileServer is a customized version of http.FileServer that can handle either an embed.FS or a os.DirFS fs.FS. Since development directories used for hot updates can contain dot files (potentially with sensitive information) the code checks to make sure that dot files are not served.
type WriterWrapper ¶ added in v0.5.0
type WriterWrapper struct {
Writer http.ResponseWriter
RetCode int
}
func NewRespWriter ¶ added in v0.5.5
func NewRespWriter(w http.ResponseWriter) *WriterWrapper
func (*WriterWrapper) Header ¶ added in v0.5.0
func (w *WriterWrapper) Header() http.Header
func (*WriterWrapper) Write ¶ added in v0.5.0
func (w *WriterWrapper) Write(buf []byte) (int, error)
func (*WriterWrapper) WriteHeader ¶ added in v0.5.0
func (w *WriterWrapper) WriteHeader(status int)
Source Files
Directories