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 🙏

© 2025 – Pkg Stats / Ryan Hefner

relog-rsbuild-plugin

v0.0.2

Published

> 🪵 Capture console logs from your LynxJS app and view them directly in your terminal — designed for use with the **LynxJS Native App Framework** and `rsbuild`.

Readme

relog-rsbuild-plugin

🪵 Capture console logs from your LynxJS app and view them directly in your terminal — designed for use with the LynxJS Native App Framework and rsbuild.

This plugin allows you to intercept console.log() and console.info() calls from your LynxJS app running on a device or emulator and send them back to the rsbuild dev server where they're printed in your terminal. It's especially useful for debugging native apps where logs might not show up in your local console.


⚠️ Disclaimer: This README and plugin were generated with the help of AI and may contain errors or outdated assumptions.
💡 I'm not affiliated with LynxJS or its maintainers — this project was built independently for use within the LynxJS ecosystem.

🙏 Pull requests are welcome! If something doesn’t work or could be improved, feel free to open a PR.


🔗 Related Plugin

This plugin is designed to work alongside ngrok-rsbuild-plugin. It uses the ngrok tunnel URL to forward logs from remote devices when testing on real hardware.

Make sure you’re using both together for the best experience.


✨ Features

  • 🔌 Adds a POST /console_log route to the dev server for capturing logs
  • 📄 Automatically generates a console.js file that overrides console.log and console.info
  • 🌐 Uses ngrok (if available) to allow logs from remote devices
  • ⚙️ Filters out noisy logs (like [rspeedy-dev-server] and [HMR]) by default
  • 🧪 Optional rspeedyLogs flag to include all logs if needed

🛠 Installation

npm install relog-rsbuild-plugin --save-dev

🔧 Setup

// rsbuild.config.ts or index.ts
import { pluginRelog } from 'relog-rsbuild-plugin';

export default {
  plugins: [
    pluginRelog({
      rspeedyLogs: false, // set to true if you want to see all logs including [rspeedy] and [HMR]
    }),
  ],
};

📁 Output

This plugin will generate a file called console.js in the same directory as the plugin.
You should load this file into your app's entry point (or however your framework handles native-side injection of JavaScript code).

import './path-to-plugin/console.js';

This script overrides console.log and console.info globally to forward logs to the dev server.


🧩 How it Works

  1. If ngrok-rsbuild-plugin is installed and exposes a tunnel URL, that URL is used for logging.
  2. A console.js file is generated pointing to http(s)://<host>/console_log.
  3. The script redefines console.log and console.info to send logs as JSON to the dev server.
  4. The server receives and prints them in your terminal.

🔍 Notes

  • Logs are filtered by default to hide common development spam ([rspeedy-dev-server], [HMR]) — you can turn them back on with rspeedyLogs: true.
  • The server route is mounted at /console_log.
  • Make sure your app loads the generated console.js file.

🧪 Example Output

[APP]: App launched on device
[APP]: Fetching data from API...
[APP]: { status: "ok", data: [...] }

License

MIT