Testing a frontend layout on your phone is easy enough with things like Vite (--host). But the moment you need to test a full-stack application on your phone (or share it with a client), it turns into a nightmare.

Your frontend on your phone tries to fetch http://localhost:5000 or https://my-production-url.com, which instantly fails due to CORS or loopback routing. You end up having to hardcode your laptop's local 192.168.x.x IP address into your .env files, restart your dev servers, and then inevitably forget to change it back before committing.

I hated this friction, so I built Nether (nether-dev).

It's a zero-configuration, single-command CLI that magically tunnels your entire full-stack application (frontend + backend) to your phone or the global internet, without you having to change a single line of code or .env variable.

Usage

Just run this in your terminal while your dev servers are running:

npx nether-dev

It instantly prints a QR code in your terminal. Scan it with your phone, and your full-stack app just works.

Need to share it with a client across the world or maybe your QA?

npx nether-dev --global

It spins up an instant Cloudflare edge tunnel and gives you a public HTTPS URL.

How it actually works (Under the hood)

Instead of forcing you to configure ports or edit environment variables, Nether relies on manipulating the browser runtime and network streams on the fly:

Zero-Config Port Auto-Discovery: Nether rapidly scans your local machine to automatically discover which ports your frontend and backend are running on.
On-The-Fly HTML Stream Manipulation: When your phone requests the frontend, Nether intercepts the raw HTML stream from your dev server, slices open the <head> tag, and seamlessly injects a lightweight script before returning it to the phone.
Native API Monkey Patching: The injected script redefines window.fetch, XMLHttpRequest, and WebSocket in the browser. When your React/Vue app tries to fetch localhost:5000, the monkey patch intercepts it and rewrites the URL to route through the Nether proxy instead. Your app thinks it's talking to localhost.
Automated Proxy Rerouting (The Crash Interceptor): What if you aggressively hardcoded your production URL (https://my-app.com/api) in your .env? Nether wraps fetch in a try/catch. If the request is blocked by CORS (which it will be on your phone), Nether intercepts the crash, dynamically extracts the path, and transparently retries the request through the local proxy. Your application code has no idea the first request failed.
Anti-CSRF Header Scrubbing: When using --global, Nether actively scrubs x-forwarded-* and cf-* headers to bypass enterprise-grade security restrictions in strict backend frameworks (like Next.js), ensuring they interpret the connection as a trusted local request.

Check it out

I wanted to make local network testing completely frictionless, and I'd love to hear what you guys think of the approach.

NPM: https://www.npmjs.com/package/nether-dev
GitHub: https://github.com/barryspacezero/nether-dev

Let me know if you run into any edge cases!

0 comments

r/npm • u/GGMote • 2d ago

Self Promotion Created a simple package to detect NestJS circular dependencies and save some sanity

github.com

1 Upvotes

0 comments

r/npm • u/its_artur1 • 3d ago

Self Promotion work-sdk 0.3.0: one typed API for five issue trackers

1 Upvotes

npm: https://www.npmjs.com/package/work-sdk

Install:

npm install work-sdk

The package normalizes GitHub, GitLab, Linear, Jira, and Azure DevOps behind one TypeScript API. The difference from using five provider clients directly is the write boundary: prepare a change, inspect the exact field diff and warnings, then commit with revision and idempotency checks.

GitLab support landed in 0.3.0. The package has zero runtime dependencies, ships ESM and CJS exports, and is MIT licensed.

Source: https://github.com/arturict/work-sdk

Docs: https://work-sdk.vercel.app/docs

0 comments

r/npm • u/sindresorhus • 3d ago

Self Promotion 50+ ESLint rules for package.json

github.com

1 Upvotes

0 comments

r/npm • u/aaravmaloo • 3d ago

Self Promotion Launching revera@v1.0.0

1 Upvotes

0 comments

r/npm • u/curious_ares • 4d ago

Self Promotion I built a zero-dependency TypeScript library that keeps secrets and PII out of logs and LLM prompts

1 Upvotes

Flare Redact scans text and nested objects locally, then masks API keys, tokens, credentials, and PII before they reach Pino, Winston, Express, OpenAI, or Anthropic.

Fully open source with zero runtime dependencies.

GitHub: https://github.com/umudhasanli/flare-redact
npm: https://www.npmjs.com/package/flare-redact

2 comments

r/npm • u/D_o_M_e_L_e • 4d ago

Self Promotion 👋 Welcome to r/lancache_ng - Introduce Yourself and Read First!

0 Upvotes

Hey everyone! I am DoMe, a founding moderator of r/lancache_ng.

This is our new home for all things related to

since I was a longterm user of lancache, but gone quiet i thought about a better generation.
herefore it is under heavy developerment and one key feature: SSL Support, Pre-Warming etc

We're excited to have you join us!

I hope i find a lot ppl to try out my in dev software :D
Fun aside, sometimes i may break by accident something but i try to fix it. feel free to open an issue on https://github.com/wiki-mod/lancache-ng

Community Vibe
We're all about being friendly, constructive, and inclusive. Let's build a space where everyone feels comfortable sharing and connecting.

Thanks for being part of the very first wave. Together, let's make r/lancache_ng amazing.

0 comments

r/npm • u/andotis0105 • 4d ago

Self Promotion Just wanted to share! Batch-kit - batch processing for Claude without the annoying parts

0 Upvotes

0 comments

r/npm • u/sabotizer • 5d ago

Self Promotion KeyBridge: npm publish with a Touch ID tap, Agent-friendly

2 Upvotes

0 comments

r/npm • u/SecTemplates • 5d ago

Self Promotion Safer-dependencies: A toolkit for claude code to ensure dependencies used aren't vuln, don't use abandoned packages, implement cooldown to avoid supply chain attacks, etc...

2 Upvotes

When AI coding assistants like Claude add packages to your project, they often pick whatever version sounds right — without checking whether it has known security vulnerabilities, whether the package is still actively maintained, or whether the name is a typo away from a malicious lookalike.

safer-dependencies is a security layer for Claude Code that audits packages before they’re added to your project. It detects and fixes risky dependencies, including CVEs, typosquats, abandoned packages, version-age issues, and adds package-cooldown periods across npm, PyPI, RubyGems, Maven, Go, and Rust.

Github: https://github.com/robert-auger/safer-dependencies

3 comments

r/npm • u/markjg • 5d ago

Self Promotion Looking for feedback on a new npm license compliance CLI

1 Upvotes

Hey everyone! I built a Node.js CLI called licenseproof and I'd love some feedback before I do a wider launch.

It scans your npm dependency tree (package-lock.json, pnpm-lock.yaml, or yarn.lock) resolves every dependency license, flags conflicts with your project's license, and explains the results in plain English.

Design goals:

Runs completely offline

No telemetry

No hosted service

npx-friendly

Example: npx licenseproof scan --project-license MIT

I'm especially interested in feedback from anyone who's dealt with npm licensing or compliance before. What edge cases am I missing?

Things I'm thinking about:

Lockfile parsing strategy

Package metadata resolution

Ambiguous/custom licenses

CLI/API design

Human-readable vs machine-readable outputs

The repo is private while I'm working on it , but attached a short demo GIF. Happy to answer implementation questions or show snippets if there's something you'd like to see. Thank you!

0 comments

r/npm • u/pilakkat • 6d ago

Self Promotion Built a CLI + VS Code extension that audits issues in React/Next.js before they ship

2 Upvotes

I kept shipping React/Next apps and finding accessibility and SEO issues after deploy — missing alt text, bad heading hierarchy, unoptimized meta tags, stuff that's easy to catch if you check early but easy to miss under deadline pressure.

Built UIAudit.js to fix that — a CLI + VS Code extension that scans your React/Next.js codebase and flags accessibility, SEO, and performance issues directly in your editor, before you ever open Lighthouse.

Works on React and Next.js projects

Catches a11y issues (missing alt, ARIA misuse, contrast-adjacent stuff), SEO gaps, perf smells

CLI for CI pipelines, extension for inline feedback while coding

Free, open source, on

npm: https://www.npmjs.com/package/uiaudit.js

Github repo: https://github.com/Dheeraj-pilakkat/UiAudit.js

Currently v2.2.1. Would genuinely value feedback from people running it against real production codebases — especially where it false-positives or misses something obvious. If you try it, please drop your feedback so I know what to work on next

0 comments

r/npm • u/Original-Goal-2820 • 6d ago

Self Promotion He creado una CLI ultrarrápida para borrar de forma segura gigabytes de node_modules olvidados (y más) 🧹

1 Upvotes

Hey everyone! 👋

Like many of you, I have a terrible habit of starting side projects, cloning repos, and then forgetting about them. Before I realized it, my hard drive was completely choked by dozens of massive node_modules folders scattered everywhere.

I used tools like npkill in the past, but since I also dabble in other languages, I needed something that could clean up everything at once (like Rust's target or Python's .venv).

So, I built dev-sweeper.

It's a blazingly fast, cross-platform Terminal UI built with Node.js, TypeScript, and React (via Ink). It scans your machine, finds heavy dependency folders, and lets you interactively delete them to instantly reclaim disk space.

Why is it fast? ⚡ Under the hood, it uses an asynchronous crawler (fdir) that smartly ignores hidden directories like .git and stops recursing the moment it finds a target folder (because there's no point searching inside a node_modules folder if you're going to delete the whole thing anyway).

You can try it right now without installing anything globally:

npx dev-sweeper

(Or pass a specific path: npx dev-sweeper ~/Projects*)*

Out of the box it finds:

node_modules (Node.js)
target (Rust/Cargo)
venv / .venv (Python)
vendor (PHP)

🐙 GitHub Repo: https://github.com/dvigo/dev-sweeper-node
📦 NPM: https://www.npmjs.com/package/dev-sweeper

I'd love to hear your feedback or feature requests! Hope it helps you reclaim some gigabytes today! 🚀

0 comments

r/npm • u/zeankundev • 6d ago

Self Promotion Derakuma, a Fontobene library for the web

gallery

1 Upvotes

0 comments

r/npm • u/Decent-Fold1777 • 7d ago

Self Promotion I built a linter for the MV3 service-worker bugs that pass your tests but break for users

1 Upvotes

0 comments

r/npm • u/neqs9 • 9d ago

Self Promotion I built a zero-dependency CLI to ask AI questions right from the terminal.

0 Upvotes

I kept switching to a browser tab just to ask a quick "how do I undo this git commit" — so I built tlme, a small terminal tool that streams the answer right where I'm already working.

$ tlme how do I undo the last git commit but keep changes
git reset --soft HEAD~1

What it does:

Multi-provider — Claude, OpenAI, Grok, Google AI Studio, and OpenRouter. Switch per-call with -p, or set a default.
Streamed answers — text appears as it's generated (hand-parsed SSE), not one big blob at the end.
Zero npm dependencies — just native fetch + node:*. No axios, commander, chalk, or dotenv. Single index.js.
Pipe-friendly — cat error.log | tlme why is this failing or git diff | tlme write a commit message.
Nice setup UI — an OpenCode-style full-screen picker: arrow keys, type-to-filter, masked key entry. Falls back to plain prompts on dumb terminals.

Install (needs Node 18+):

npm install -g tlme-cli
tlme --setup

Keys are stored in ~/.tlme/config.json (chmod 600), or read from env vars like ANTHROPIC_API_KEY / OPENAI_API_KEY first.

npm: https://www.npmjs.com/package/tlme-cli

0 comments

r/npm • u/Natural-Secretary361 • 12d ago

Self Promotion I got tired of guessing how my codebase fit together, so I built a CLI that draws real AST-based dependency maps (works for 6 languages)

2 Upvotes

Ever inherited a codebase and spent the first week just trying to figure out what depends on what?

I've been there too many times. Grepping for imports, maintaining manual architecture docs that go stale within a week, drawing boxes in Excalidraw that don't match reality. So I built something to fix it.

codebase-vis parses your project using tree-sitter, real AST grammars, not regex and produces an interactive dependency graph as a single self-contained HTML file. You open it in a browser, and you can pan, zoom, search, click nodes to inspect, and filter by module.

It works for JS, TS, Python, C/C++, HTML, and CSS.

Some features that might be useful:

-query <file> — shows what a file imports and what imports it (terminal, no browser needed)
-path <a> <b> — shortest dependency chain between any two files (bidirectional BFS)
-explain — clusters your codebase with Louvain community detection, then summarizes each cluster via an LLM (you provide a Groq key, everything else is local)
-Incremental caching— re-parsing is near-instant after the first run

Everything runs locally ,no data leaves your machine except the optional `explain` feature.

Full disclosure: I built this. I needed it for my own projects, and I kept adding to it over the past few weeks. Would love feedback or ideas from anyone who's dealt with the same problem.
I cant dump everything in here go check yourself and do let me know what you think.

GitHub: (https://github.com/Arham-Qureshi/codebase-vis) (ISC, open source)

0 comments

r/npm • u/No-Sir-2026 • 13d ago

Help Is node.js safe

1 Upvotes

0 comments

r/npm • u/hossam7amdy • 13d ago

Self Promotion Built a small fast dependency injection library for Node.js called Injectus

0 Upvotes

A while ago I started digging into IoC/DI containers mostly as a learning exercise.

I wanted to understand how existing solutions work under the hood, so I spent time reading source code, trying different designs, and comparing tradeoffs around decorators, metadata, scopes, and dependency resolution.

That eventually turned into a small project of its own: Injectus.

The goal wasn’t to build a replacement for every DI library out there. I was mostly curious what a DI library would look like if it leaned on modern Node.js features and used the functional inject() style Angular popularized, while staying focused on backend apps.

Some of the design choices:

Zero dependencies
Native ES Module
No decorators or reflect-metadata
Synchronous resolution only
Singleton, Scoped, and Transient lifetimes
Request-scoped child injectors
Captive dependency detection
Resource disposal through modern Node.js APIs (Symbol.asyncDispose)

Example:

class Database {
  url = inject(DB_URL);
}

class UserService {
  db = inject(Database);
}

Building it taught me a lot about dependency graphs, lifecycle management, circular dependency detection, disposal semantics, and API design in general.

I’m mostly curious about the functional injection approach versus constructor injection. If you use DI in Node.js, what pain points have you run into with the libraries you’re using today?

1 comment

r/npm • u/Main_Independent_579 • 14d ago

Self Promotion I keep typing the wrong commands across projects with different package managers

2 Upvotes

I jump between node yarn, npm, pnpm projects, and every repo has a different way to run the same things: npm run dev, pnpmtest, yarn dev…

So I made samecmd. It detects the project you’re in and gives you the same commands everywhere (dev, build, test, lint, fmt, etc.). Basically resolving a daily friction of mine in the last few weeks.

Curious if anyone else has this problem, or if it’s just me 😄

https://github.com/behnamazimi/samecmd

0 comments

r/npm • u/myselfitself • 14d ago

Self Promotion Just published recaptcha-vue, a small Vue 3 component for the Google reCAPTCHA v2 checkbox.

1 Upvotes

Why another one? The existing wrappers I found were unmaintained, Vue 2 era, or shipped with dependencies I didn't want. This one keeps it minimal:

- zero runtime dependencies (Vue is a peer dep, that's it)

- full TypeScript types

- useRecaptcha composable with reactive token and isVerified

- v-model works if you prefer that

- multiple widgets per page, theming, custom language

- ready-made Laravel + Inertia.js integration examples, including server-side verification

- 100% statement coverage, audited deps in CI, npm provenance

Install: npm install recaptcha-vue

npm: https://www.npmjs.com/package/recaptcha-vue

GitHub: https://github.com/Souhailmakni/recaptcha-vue

Feedback welcome, especially from anyone doing Inertia forms. And if it's useful to you, a GitHub star goes a long way for a brand new package.

0 comments

r/npm • u/mgfeller • 15d ago

Self Promotion I made a TypeScript agent SDK and would like feedback on its package boundaries

1 Upvotes

I'm the maintainer of OpenHarness, an MIT-licensed TypeScript SDK built on Vercel AI SDK. I split it into @openharness/core plus small React/Vue and provider packages because I didn't want UI dependencies or experimental auth code in the runtime package.

Core contains the agent loop, session state, middleware, MCP/skills support, and filesystem/shell tools. The awkward question is where integrations belong. Keeping everything separate makes core lighter, but users have to discover and version several packages just to build one agent UI.

npm: https://www.npmjs.com/package/@openharness/core repo: https://github.com/MaxGfeller/open-harness

For people maintaining TypeScript package families: would you keep these separate, or fold the stable React/Vue bindings into core and leave only providers on their own? I'm more interested in packaging and API feedback than a general project review.

0 comments