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

fs-json-writer

v1.0.0-beta

Published

write JSON content with persist indent depths from file system

Readme

fs-json-writer

Generate JSON file content readable by a human

The native solution fs.writeFile combined with JSON.stringify generate a minified content because JSON.stringify is designed for data transfer.

This package full rewrite a JavaScript Object Notation with resolve tabulation depth and resolve nested object/array.

installation

in depending your need you can install at dev-dependencies

> npm install --save fs-json-writer

or with yarn

> yarn add fs-json-writer

usage

json file

const jsonWriter = require('fs-json-writer');
const path = require('path');


const myHumanJson = {

  version: "1.0.0",
  details: "this is a stable version with goodly peoples ^.^"
};

jsonWriter({

  path: path.join( __dirname, "./file-name.json" ),

  state: myHumaJson
});

output (filename.json)

{
  "version": "1.0.0",
  "details": "this is a stable version with goodly peoples ^.^"
}

This encoding use is always UTF-8 for write a JSON content and path argument should be a absolute path

js file

const jsonWriter = require('fs-json-writer');
const path = require('path');


const myHumanJson = {

  version: "1.0.0",
  details: "this is a stable version with goodly peoples ^.^"
};

jsonWriter({

  path: path.join( __dirname, "./file-name.js" ),
  state: myHumaJson,

  isEs6: true,
  isNoQuote: true
});

extension of filename determined if content should be JS or JSON file.

output (filename.js)

export default {

  version: "1.0.0",
  details: "this is a stable version with goodly peoples ^.^"
}

async

Can asynchrone generate content with Promise API or inehrit from natively fs module callback system.

Promise

const jsonWriter = require('fs-json-writer');
const path = require('path');


const myHumanJson = {

  version: "1.0.0",
  details: "this is a stable version with goodly peoples ^.^"
};

jsonWriter.async({

  path: path.join( __dirname, "./file-name.js" ),
  state: myHumaJson,

  isEs6: true
})
.then( ({ path, content, state }) => {

  console.log( "success write at:" + path + " the content: " + content + " from javascript object: ", state );

} )
.catch( error => {

  console.log( error );

  throw "Oops, something went wrong.";

} );

Callback

const jsonWriter = require('fs-json-writer');
const path = require('path');


const myHumanJson = {

  version: "1.0.0",
  details: "this is a stable version with goodly peoples ^.^"
};

jsonWriter.legacyAsync({

  path: path.join( __dirname, "./file-name.js" ),
  state: myHumaJson,

  isEs6: true,
  isNoQuote: true,

  onError: error => {

    console.log( error );

    throw "Oops, something went wrong.";
  },

  onSuccess: ({path, content, state}) => {

    console.log( "success write at:" + path + " the content: " + content + " from javascript object: ", state );

  }

});

optionals

From a syn/async call can define optionals attributes: onReplace: () => any | string[] | number[], space: string | number this attributes is passed to arg2 and arg3 of JSON.stringify

Please if you detect any bugs/undetermined comportement open new issue