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

@octanejs/rsbuild-plugin

v0.1.33

Published

Rsbuild metaframework plugin for Octane (Rspack compiler, routing, SSR, hydration, and production builds)

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

trueadmtrueadmleonidaz_npmleonidaz_npmwebeferenwebeferen

Keywords

Readme

@octanejs/rsbuild-plugin

Full Octane app integration for Rsbuild 2.x: Rspack source compilation, routing, streaming dev SSR, hydration, module server RPC, production client/server environments, preview, and deployment adapters.

Install

pnpm add octane @octanejs/rsbuild-plugin
pnpm add -D @rsbuild/core
// rsbuild.config.ts
import { defineConfig } from '@rsbuild/core';
import { pluginOctane } from '@octanejs/rsbuild-plugin';

export default defineConfig({
	plugins: [pluginOctane()],
});

Without an octane.config.ts containing routes, the plugin only installs the Octane compiler and preserves your own Rsbuild entries. Use the lower-level @octanejs/rspack-plugin directly when you do not want Rsbuild.

Routing and SSR

// octane.config.ts
import { defineConfig, RenderRoute, ServerRoute } from '@octanejs/rsbuild-plugin';

export default defineConfig({
	router: {
		routes: [
			new RenderRoute({ path: '/', entry: '/src/Home.tsrx' }),
			new ServerRoute({
				path: '/api/health',
				handler: () => Response.json({ ok: true }),
			}),
		],
	},
});

index.html must contain <!--ssr-head--> in <head> and <!--ssr-body--> inside <div id="root">. In app mode the plugin creates a web hydration environment and a node SSR environment. A deployment adapter with serverTarget: 'webworker' changes only the production server target to web-worker; development SSR remains Node-based. Override the environment names with clientEnvironment and serverEnvironment when composing a larger Rsbuild setup.

pnpm rsbuild dev
pnpm rsbuild build
pnpm octane-rsbuild-preview

Production assets are written to dist/client; the self-contained ESM server, SSR template, and route asset map are written to dist/server. Change the shared root with build.outDir in octane.config.ts. The default generated server exports handler and nodeHandler and auto-boots under Node. A webworker adapter instead receives an importable createWebWorkerHandler factory for its platform wrapper. The configured adapter runs after both environments finish.

build.target applies to both application transforms and Rspack's generated runtime. Use one ES level (es2018, es2022, and so on), modules, false, or browser targets such as ['chrome100', 'firefox100', 'samsung24']. Samsung targets use the Samsung Internet version, not its Chromium engine version; for example, samsung24 corresponds to Chromium 117. The modules baseline also includes Samsung Internet 14, which corresponds to Chromium 87. ES levels and browser targets cannot be mixed in the same array. Transpilation changes syntax; applications remain responsible for any additional Web API polyfills they use.

Options are declarative and cache-stable:

  • hmr controls browser component handoff;
  • profile enables component profiling in the browser environment;
  • strong overrides the app's compiler.strong setting;
  • exclude skips path fragments in the plain .ts/.js hook-slot pass; and
  • clientEnvironment / serverEnvironment rename the generated environments.

Enable Strong mode for the whole app in octane.config.ts:

export default defineConfig({
	compiler: { strong: true },
});

You can also pass pluginOctane({ strong: true }). The plugin option takes priority over the app config. Dependencies are unaffected unless they begin a module with "use strong".

App mode currently serves from the root path and uses Rsbuild's default asset prefix. Keep server.base at / and output.assetPrefix at auto or /; for a subpath deployment, rewrite that prefix to the app root in the hosting proxy. When octane.config.ts or one of its imported helpers changes, rsbuild dev restarts the dev server and applies the complete config atomically. This is required for compiler.renderers, because renderer selection is part of each Rspack compiler's cache and loader identity. Source-module edits continue to use the normal HMR or browser-reload path.

The package forwards normalized compiler.renderers registry, filename-rule, and renderer-boundary metadata through the same Rspack compiler path used by Vite and direct compilation. This enables the experimental universal client target; a concrete Lynx runtime and cross-thread transport remain future work.