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

@craft-ts/log-server

v0.8.7

Published

Local JSONL log ingestion server for CraftTS development

Readme

Local log server

Receives logs from the demo application over HTTP and appends them to a local JSONL file. It does nothing else — reading the logs back is the job of @craft-ts/log-mcp.

npm run logs:server

Endpoints

| Method | Path | Description | | -------- | --------- | -------------------------------------------------- | | POST | /logs | Ingest a batch. Answers 202 {"accepted": n}. | | DELETE | /logs | Delete the active and rotated files. | | GET | /health | Target file and its current size. |

POST /logs accepts three body shapes: a { clientId, entries: [...] } envelope (what the demo sends), a bare array of entries, or a single entry. Entries missing a known level are dropped individually — one bad entry never rejects the whole batch. CORS is wide open: this is a loopback dev tool.

Storage

One JSON object per line in .logs/app.jsonl, oldest first. Each stored entry keeps the browser timestamp and adds a server-side receivedAt plus an incrementing seq. Once the active file exceeds LOG_SERVER_MAX_FILE_SIZE it is rotated to app.jsonl.1, existing rotated files shift down one slot, and anything past LOG_SERVER_MAX_FILES is dropped.

Environment

| Variable | Default | Description | | -------------------------- | ----------- | --------------------------------- | | LOG_SERVER_HOST | 127.0.0.1 | Listen address | | LOG_SERVER_PORT | 4319 | Listen port | | LOG_SERVER_DIR | ./.logs | Storage directory | | LOG_SERVER_MAX_FILE_SIZE | 5242880 | Rotation threshold, in bytes | | LOG_SERVER_MAX_FILES | 5 | Rotated files kept | | LOG_SERVER_QUIET | unset | Set to 1 to silence ingest echo |

LOG_SERVER_DIR and LOG_SERVER_MAX_FILES must match what the MCP server uses, otherwise it reads a different set of files.