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

@juncha9/rr7-build-fix

v0.0.1

Published

Fix Windows backslash path separators (assetsBuildDirectory) in React Router 7 SSR build output

Readme

@juncha9/rr7-build-fix

Fix Windows backslash path separators in React Router 7 SSR build output.

When you run react-router build on Windows, the server bundle declares:

var assetsBuildDirectory = "build\\client";

The backslash separator breaks path handling on POSIX servers (e.g. Linux deploys). This CLI rewrites only that assignment to use a forward slash:

var assetsBuildDirectory = "build/client";

It is surgical — it touches only the assetsBuildDirectory = "..." assignment, so unrelated regex/pattern escapes elsewhere in the bundle (e.g. "\\d{6}") are left intact. Running it twice is safe (idempotent).

Installation

npm install --save-dev @juncha9/rr7-build-fix

Usage

Run with no arguments to fix server/index.js in the known build directories (build/ and build_test/) — whichever exist:

npx rr7-build-fix

Wire it into your build scripts:

"scripts": {
  "build:prod": "react-router build --mode production && rr7-build-fix",
  "build:test": "react-router build --mode testprod  && rr7-build-fix"
}

Target a specific build directory or file:

rr7-build-fix build_test                 # fixes build_test/server/index.js
rr7-build-fix build/server/index.js      # fixes the file directly
rr7-build-fix build build_test           # multiple targets

A directory argument is resolved to <dir>/server/index.js; a file argument is used as-is.

Programmatic API

import { fixAssetsBuildPath } from "@juncha9/rr7-build-fix";

const result = fixAssetsBuildPath("build/server/index.js");
// { filePath, changed, before?, after? }

License

MIT