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 🙏

© 2024 – Pkg Stats / Ryan Hefner

jsonc.min

v1.1.0

Published

✨ Faster and safer JSON and JSONC minify, parse and stringify for JavaScript (Browser compatible) — 2.3KB.

Downloads

334

Readme

NPM Version GitHub Workflow Status (Node.js) GitHub Workflow Status (Bun) GitHub Workflow Status (Deno)

✨ Faster and safer JSON and JSONC minify, parse and stringify for JavaScript (Browser compatible) — 2.3KB.

Why

🔐 Safety

Many JSON minification packages rely on vulnerable regex, making them unsuitable for production.

     jsonc.min prioritizes security by avoiding these pitfalls and offering a robust solution.

🤝 Compatibility

     jsonc.min ensures full compatibility with both Node.js, Bun, Deno and, browser environments.      All features work for both JSON and JSONC.

🪶 Lightweight

     Zero dependencies and optimized for production environments.


Install

# Node.js
npm i jsonc.min
# Bun
bun add jsonc.min
# Deno
deno add npm:jsonc.min

Usage

Import

ES Modules

import { JSONC } from 'jsonc.min';

CommonJS

const { JSONC } = require('jsonc.min');

Browser

<script src="https://cdn.jsdelivr.net/npm/jsonc.min/browser/jsonc.min.js"></script>

toJSON

Convert from JSONC to JSON.

JSONC.toJSON('/* JSONC content */ { "test": true }');
// "{ test: true }"

If the content is already JSON, it will just be preserved:

JSONC.toJSON('{ "test": true }');
// "{ test: true }"

minify

Minify both JSON and JSONC.

const content = `
  /**
   * JSONC content
   */
  {
    "test": true // 🔬
  }
`;

JSONC.minify(content);
// "{test:true}"
const content = `
  {
    "test": true
  }
`;

JSONC.minify(content);
// "{test:true}"

parse

Parse both JSON and JSONC.

const content = `
  /**
   * JSONC content
   */
  {
    "test": true // 🔬
  }
`;

JSONC.parse(content);
// { test: true }
const content = `
  {
    "test": true
  }
`;

JSONC.parse(content);
// { test: true }
  • If your content is guaranteed to be a JSON, there is no advantage to using JSONC.parse(content) instead of JSON.parse(content).

stringify

Prettify both JSON and JSONC.

Use JSON.stringify behind the scenes.

const content = '/** JSONC content */ { "test": true }';

JSONC.stringify(content, null, 2);
// "{
//    "test": true
//  }"
const content = '{ "test": true }';

JSONC.stringify(content, null, 2);
// "{
//    "test": true
//  }"

Examples

Reading a JSON or JSONC file

import { readFile } from 'node:fs/promises';
import { JSONC } from 'jsonc.min';

const content = await readFile('./file.jsonc', 'utf-8');

JSONC.parse(content);

Parsing a dynamic config file

For this example, let's assume a .configrc that can be both a JSON or a JSONC, as well as looking for both config.json and config.jsonc files:

import { JSONC } from 'jsonc.min';
import { cwd } from 'node:process';
import { join } from 'node:path';
import { readFile } from 'node:fs/promises';

export const getConfigs = async (customPath?: string) => {
  const targetRoot = cwd();

  const expectedFiles = customPath
    ? [customPath]
    : ['.configrc', 'config.json', 'config.jsonc'];

  for (const file of expectedFiles) {
    const filePath = join(targetRoot, file);

    try {
      const configsFile = await readFile(filePath, 'utf-8');

      // jsonc.min will parse both JSON and JSONC extensions, even if there is no extension.
      return JSONC.parse(configsFile);
    } catch {}

    return {};
  }
};

Acknowledgements

Contributors