npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

fastify-vite-plugin

v0.0.24

Published

Integrate Vite SPA into a Fastify application

Downloads

34

Readme

release workflow playwright workflow

vite-plugin-ts

A Fastify plugin to integrate a Vite SPA into the current project and serving both frontend and backend from the same host.
It doesn't aim to deal with server side rendering, but you can still do that from your Fastify application.
It could be an interesting use case to render HTML only if the request is made by a bot. A bot can be detected using isbot package. It's configured to not ship Vite in production and to only serve its produced assets.

Usage

import { fastifyVitePlugin } from 'fastify-vite-plugin'
import Fastify from 'fastify'

const app = Fastify()

// place your routes before the plugin registration
// otherwise the "catch all" route that renders index.html
// for the SPA will take precedence

await app.register(fastifyVitePlugin)

await app.listen({
  port: process.env.PORT,
  host: process.env.NODE_ENV === 'development' ? '0.0.0.0' : undefined,
})

Example vite.config.ts

import react from '@vitejs/plugin-react-swc'
import { VitePWA } from 'vite-plugin-pwa'
import { defineConfig } from 'vite'

export default defineConfig({
  plugins: [
    react(),
    VitePWA({
      workbox: {
        globPatterns: ['**/*.{js,css}'],
        navigateFallback: null,
      },
      includeAssets: ['**/*'],
    }),
  ],
})

The above configuration will just work in dev mode.
When you do npx vite build for NODE_ENV=production make sure that the output is located into /dist/assets.

Options

The following options need to be specified if they are changed in vite.config.ts.

  • viteOutDir defaults to dist
  • viteAssetsDir defaults to /assets/ relative path for where Vite stores its production assets

Requirements

  • it assumes index.html is placed in the root of the project
  • its assumes npx vite build is executed before starting the application with NODE_ENV=production
    • if you are using TypeScript, it should be in the same step where you compile your code to JavaScript