7 Developer Tasks You're Still Installing npm Packages For (Your Browser Already Does Them)

I used to install a new npm package every time I needed to format JSON, convert CSV to JSON, or edit a Markdown file. Then I realized: why am I downloading entire Node modules for tasks my browser can handle natively?

Here are 7 common developer tasks that don't need any installation — they run entirely in your browser.

---

1. JSON Formatting & Validation

Instead of npm install json-formatter or using a random online tool that might log your API payloads:

// Before: messy API response
{"users":[{"name":"Alice","skills":["js","python"]},{"name":"Bob","skills":["go","rust"]}]}

// After: properly formatted
{
  "users": [
    {
      "name": "Alice",
      "skills": ["js", "python"]
    },
    {
      "name": "Bob",
      "skills": ["go", "rust"]
    }
  ]
}

Client-side JSON formatters parse and re-indent your JSON without sending it anywhere. Your API keys, tokens, and user data stay on your machine.

2. CSV ↔ JSON Conversion

Working with spreadsheets? Most developers end up copying CSV data to an online converter. The problem: you're uploading potentially sensitive data (customer lists, financial data) to unknown servers.

Browser-based CSV converters handle everything locally. Paste your CSV, get JSON. Or vice versa. No upload, no server, no risk.

3. Markdown Editing (with Live Preview)

Yes, VS Code has a Markdown preview. But what about when you're on a shared computer, reviewing a PR on GitHub, or just want a quick preview without opening your IDE?

A browser-based Markdown editor with live preview handles this in one tab. Some even support WeChat Markdown formatting — useful if you're writing content for Chinese social platforms.

4. Base64 Encoding/Decoding

# What you used to do:
echo -n "Hello World" | base64
# SGVsbG8gV29ybGQ=

Quick encoding/decoding tasks happen in browser tools faster than you can type the terminal command. Especially useful when you're debugging JWT tokens or inspecting API responses.

5. URL Encoding/Decoding

That %20 in your URL driving you crazy? Browser tools decode URL-encoded strings instantly. No more googling "url decode online" and clicking through ad-heavy sites.

6. Hash Generation (MD5, SHA-256, etc.)

Verifying file integrity or debugging authentication? Generate hashes in your browser without installing hashlib wrappers or running terminal commands.

7. Regex Testing

Building a complex regex pattern? Browser-based regex testers with real-time matching visualization save more time than any npm package.

---

Why Browser-Based?

The key insight: your data never leaves your browser.

Every online tool you use sends your data to their servers. Most of them don't need to — the computation is trivial and modern JavaScript handles it fine.

I've been using tools.pixiaoli.cn which has 33+ of these tools, all running entirely client-side. JSON formatter, CSV converter, Markdown editor, regex tester — all in one place, no signup required, zero data transmission.

The Privacy Argument

When you paste a JWT token into an online formatter, you're trusting that service not to log it. When you upload a CSV with customer data to a converter, you're hoping they delete it after processing.

With client-side tools, there's nothing to trust. The JavaScript runs in your browser, processes your data locally, and never makes a network request.

---

TL;DR: Before installing another npm package for basic formatting tasks, check if a browser-based tool handles it. Your code stays cleaner, your data stays private, and you save disk space.

What developer tasks do you still install packages for that could be browser-based? Drop a comment below.