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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@fluixi/start

v0.1.0-alpha.85

Published

The Fluixi meta-framework — dev server, build, and production SSR server over @fluixi/server + Vite.

Readme

@fluixi/start

The Fluixi meta-framework — zero-config dev/build/start with SSR, file routing, and hydration.

License: MIT TypeScript npm Vite


✨ Overview

@fluixi/start is dev, build, and production start over @fluixi/server

  • Vite, so apps stop hand-rolling a server.mjs. This package is the runtime (programmatic commands + config); the fluixi CLI lives in @fluixi/cli, and you scaffold a new app with create-fluixi (npm create fluixi).
fluixi dev      # SSR dev server (Vite middleware + HMR)
fluixi build    # client + server bundles → dist/client, dist/server
fluixi start    # production SSR server (after build)

📦 Installation

pnpm add @fluixi/start @fluixi/cli

🗂️ Conventions

| Default | Config key | | --- | --- | | src/entry-server.ts exporting render(url) (and optionally renderStream(url)) | serverEntry | | src/entry-client.ts (hydration) | clientEntry | | src/routes/ (file-based routes → virtual:fluixi-routes) | routesDir | | src/middleware.ts (optional request middleware) | middleware | | index.html with <div id="root"></div> | template / mountId | | port 3000 | port |

⚙️ Config

fluixi.config.{ts,mts,mjs,js} — TypeScript configs are bundled on the fly:

import { defineConfig } from '@fluixi/start/config';

export default defineConfig({
  port: 3010,
  ssrNoExternal: ['@medusajs/js-sdk'], // SSR deps Vite must bundle
  adapter: nodeAdapter,                // where this deploys
  prerender: true,                     // SSG: build static HTML, crawling internal links
  resolve: [                           // where an unimported tag comes from
    { match: /^([A-Z]\w+)$/, module: '/src/components/$1.tsx' },
  ],
});

ssr: false gives an SPA — the server still runs (file routing, middleware, env, server functions), the first paint just happens on the client. i18n and apiDir default to src/i18n and src/api, and stay a no-op until those folders have files.

🚀 Features

  • Streaming SSR — export renderStream(url) (via @fluixi/server's renderToBodyStream) and the index.html head is flushed first, then the app body is streamed into the mount point.
  • Middleware / guards — src/middleware.ts default-exports defineMiddleware([...]), a (request, next) => Response chain run before SSR (auth redirects, headers, …).
  • Server functions — a "use server" function runs only on the server and is callable from the client over RPC (/_server, same-origin CSRF); getRequestEvent() works inside it.
  • Routing — @fluixi/start/router re-exports @fluixi/core/router: Router, Outlet, Link, Form, the hooks, createMemoryHistory.
  • Static generation — prerender: true builds routes to static HTML in dist/client, crawling internal <a href> links; an object sets explicit routes for paths nothing links to. The pages still hydrate.
  • API routes — files under src/api export GET/POST/… and are served at /api/*.
  • i18n — src/i18n/<locale>.json is discovered and exposed as virtual:fluixi-i18n for createI18n, with typed keys.
  • Deploy adapters — createProdHandler builds a runtime-neutral fetch handler, and an adapter decides how the server is bundled and served: nodeAdapter (Node http + static files), webAdapter (export { fetch } for edge/worker), plus cloudflareAdapter, netlifyAdapter and vercelAdapter, which emit the layout each platform expects. The same handler runs on Node, Bun, Deno and edge runtimes.
  • Component resolution — resolve says where a capitalised tag with no import comes from; one pattern rule can cover a whole folder. See @fluixi/compiler for the rule shapes and for load: deferral.

🧰 Programmatic

import { dev, build, start, createProdHandler } from '@fluixi/start';

await dev({ port: 3010 });                 // or build() / start()
const handler = await createProdHandler();  // a (Request) => Promise<Response>

🔌 Subpaths

| Import | What | | --- | --- | | @fluixi/start | dev/build/start, the fetch-handler layer, adapters, middleware helpers | | @fluixi/start/config | defineConfig, loadConfig, resolveConfig | | @fluixi/start/router | the routing surface (re-export of @fluixi/core/router) | | @fluixi/start/server-fn | server-function runtime (isServerFnRequest, handleServerFn) |

📄 License

MIT © Fluixi