Which is Better Data Serialization Formats?
json5 vs yaml vs xml-js vs toml

1 Year
json5yamlxml-jstomlSimilar Packages:
What's Data Serialization Formats?

Data serialization formats are used to convert data structures or object instances into a format that can be easily stored, transmitted, or reconstructed. These formats provide a way to represent complex data in a human-readable and machine-readable form. Each of these packages offers a different format for serializing and deserializing data, catering to specific use cases and preferences.

NPM Package Downloads Trend
Github Stars Ranking
Stat Detail
Package
Downloads
Stars
Size
Issues
Publish
License
json566,408,4656,390235 kB33-MIT
yaml42,639,1141,200675 kB14a month agoISC
xml-js1,743,1511,261-1225 years agoMIT
toml845,603304-205 years agoMIT
Feature Comparison: json5 vs yaml vs xml-js vs toml

Readability

  • json5: JSON5 offers a more relaxed syntax compared to standard JSON, allowing for comments, trailing commas, and single quotes. This makes JSON5 more human-readable and writable, especially for configuration files and data exchange.
  • yaml: YAML is known for its readability and ease of use, with a syntax that is designed to be human-friendly. YAML files are easy to read and write, making them a popular choice for configuration files and data serialization.
  • xml-js: xml-js provides functions to convert XML data to JSON and vice versa, making it easier to work with XML data in a JavaScript environment. This can improve readability and simplify the manipulation of XML documents.
  • toml: TOML is designed to be highly readable for humans, with a simple and minimal syntax that is easy to understand. This makes TOML a popular choice for configuration files and settings that need to be easily readable and editable.

Flexibility

  • json5: JSON5 offers a more flexible syntax compared to standard JSON, allowing for additional features like comments, trailing commas, and single quotes. This flexibility can be useful for customizing data structures and configurations.
  • yaml: YAML is a flexible data serialization format that supports complex data structures and configurations. The flexibility of YAML allows for easy customization and adaptation to different use cases and requirements.
  • xml-js: xml-js allows for easy conversion between XML and JSON data formats, providing flexibility in working with different data structures. This can simplify data manipulation and processing tasks in JavaScript.
  • toml: TOML provides a flexible and minimal syntax for defining configuration settings, making it easy to customize and extend. This flexibility allows for easy integration with different systems and applications.

Ease of Use

  • json5: JSON5 is easy to use and understand, with a syntax that is similar to standard JSON but with added features for improved readability. This makes JSON5 a user-friendly choice for working with JSON data.
  • yaml: YAML's human-readable syntax and straightforward structure make it easy to use for defining data structures and configurations. The simplicity of YAML files makes them accessible to developers and users alike.
  • xml-js: xml-js simplifies working with XML data in JavaScript by providing functions for converting XML to JSON and vice versa. This ease of use can streamline data processing tasks and make working with XML documents more efficient.
  • toml: TOML is designed to be easy to read and write, with a simple syntax that is intuitive for humans. This ease of use makes TOML a popular choice for configuration files and settings that need to be quickly edited or updated.

Interoperability

  • json5: JSON5 is interoperable with standard JSON, allowing for seamless integration with existing JSON data and systems. This interoperability ensures that JSON5 can be used in a wide range of applications and environments.
  • yaml: YAML's human-readable format and support for complex data structures promote interoperability across different systems and programming languages. This makes YAML a versatile choice for data serialization and configuration needs.
  • xml-js: xml-js facilitates interoperability between XML and JSON data formats, enabling seamless conversion and manipulation of data structures. This interoperability can simplify data exchange and processing tasks in JavaScript applications.
  • toml: TOML's simple and minimal syntax promotes interoperability with different systems and applications. This makes TOML a versatile choice for configuration files and settings that need to be shared across multiple platforms.

Extensibility

  • json5: JSON5 allows for extensibility through its relaxed syntax, which supports additional features like comments, trailing commas, and single quotes. This extensibility can be useful for customizing data structures and configurations.
  • yaml: YAML's support for complex data structures and configurations makes it highly extensible for a wide range of use cases. This extensibility allows for easy customization and adaptation of YAML files to meet specific requirements and preferences.
  • xml-js: xml-js provides extensibility by enabling conversion between XML and JSON data formats, allowing for flexible manipulation of data structures. This extensibility can simplify data processing tasks and enhance the functionality of JavaScript applications.
  • toml: TOML supports extensibility through its simple and minimal syntax, which allows for easy customization and extension of configuration settings. This extensibility makes TOML adaptable to different use cases and requirements.
How to Choose: json5 vs yaml vs xml-js vs toml
  • json5: Choose JSON5 if you need a more relaxed JSON syntax that allows comments, trailing commas, and single quotes. JSON5 is a human-readable and writable format that is compatible with standard JSON.
  • yaml: Choose YAML if you value readability and want a format that is easy for humans to write and understand. YAML is a data serialization format that is often used for configuration files and data exchange between different systems.
  • xml-js: Choose xml-js if you need to work with XML data in JavaScript. xml-js provides functions to convert XML data to JSON and vice versa, making it easier to manipulate XML documents in a JavaScript environment.
  • toml: Choose TOML if you prefer a minimal configuration file format that is easy to read and write. TOML is designed to be easy for humans to understand while also being easy to parse for machines.
Similar Npm Packages to json5

json5 is a library that extends the JSON format to include some ES5 features like comments, trailing commas, and more. It provides a more flexible and human-readable way to write JSON data. While json5 offers these additional features, there are other libraries in the JavaScript ecosystem that handle different data formats. Here are a few alternatives:

  • toml is a library for parsing and serializing TOML (Tom's Obvious, Minimal Language) data format. TOML is designed to be a minimal configuration file format that's easy to read and write.
  • xml-js is a library for converting XML data to JavaScript objects and vice versa. It provides a simple way to work with XML data in JavaScript applications.
  • yaml is a library for parsing and serializing YAML (YAML Ain't Markup Language) data format. YAML is a human-readable data serialization format that is often used for configuration files.

Check out this comparison: Comparing json5 vs toml vs xml-js vs yaml.

README for json5

JSON5 – JSON for Humans

Build Status Coverage
Status

JSON5 is an extension to the popular JSON file format that aims to be easier to write and maintain by hand (e.g. for config files). It is not intended to be used for machine-to-machine communication. (Keep using JSON or other file formats for that. 🙂)

JSON5 was started in 2012, and as of 2022, now gets >65M downloads/week, ranks in the top 0.1% of the most depended-upon packages on npm, and has been adopted by major projects like Chromium, Next.js, Babel, Retool, WebStorm, and more. It's also natively supported on Apple platforms like MacOS and iOS.

Formally, the JSON5 Data Interchange Format is a superset of JSON (so valid JSON files will always be valid JSON5 files) that expands its syntax to include some productions from ECMAScript 5.1 (ES5). It's also a strict subset of ES5, so valid JSON5 files will always be valid ES5.

This JavaScript library is a reference implementation for JSON5 parsing and serialization, and is directly used in many of the popular projects mentioned above (where e.g. extreme performance isn't necessary), but others have created many other libraries across many other platforms.

Summary of Features

The following ECMAScript 5.1 features, which are not supported in JSON, have been extended to JSON5.

Objects

  • Object keys may be an ECMAScript 5.1 IdentifierName.
  • Objects may have a single trailing comma.

Arrays

  • Arrays may have a single trailing comma.

Strings

  • Strings may be single quoted.
  • Strings may span multiple lines by escaping new line characters.
  • Strings may include character escapes.

Numbers

  • Numbers may be hexadecimal.
  • Numbers may have a leading or trailing decimal point.
  • Numbers may be IEEE 754 positive infinity, negative infinity, and NaN.
  • Numbers may begin with an explicit plus sign.

Comments

  • Single and multi-line comments are allowed.

White Space

  • Additional white space characters are allowed.

Example

Kitchen-sink example:

{
  // comments
  unquoted: 'and you can quote me on that',
  singleQuotes: 'I can use "double quotes" here',
  lineBreaks: "Look, Mom! \
No \\n's!",
  hexadecimal: 0xdecaf,
  leadingDecimalPoint: .8675309, andTrailing: 8675309.,
  positiveSign: +1,
  trailingComma: 'in objects', andIn: ['arrays',],
  "backwardsCompatible": "with JSON",
}

A more real-world example is this config file from the Chromium/Blink project.

Specification

For a detailed explanation of the JSON5 format, please read the official specification.

Installation and Usage

Node.js

npm install json5

CommonJS

const JSON5 = require('json5')

Modules

import JSON5 from 'json5'

Browsers

UMD

<!-- This will create a global `JSON5` variable. -->
<script src="https://unpkg.com/json5@2/dist/index.min.js"></script>

Modules

<script type="module">
  import JSON5 from 'https://unpkg.com/json5@2/dist/index.min.mjs'
</script>

API

The JSON5 API is compatible with the JSON API.

JSON5.parse()

Parses a JSON5 string, constructing the JavaScript value or object described by the string. An optional reviver function can be provided to perform a transformation on the resulting object before it is returned.

Syntax

JSON5.parse(text[, reviver])

Parameters

  • text: The string to parse as JSON5.
  • reviver: If a function, this prescribes how the value originally produced by parsing is transformed, before being returned.

Return value

The object corresponding to the given JSON5 text.

JSON5.stringify()

Converts a JavaScript value to a JSON5 string, optionally replacing values if a replacer function is specified, or optionally including only the specified properties if a replacer array is specified.

Syntax

JSON5.stringify(value[, replacer[, space]])
JSON5.stringify(value[, options])

Parameters

  • value: The value to convert to a JSON5 string.
  • replacer: A function that alters the behavior of the stringification process, or an array of String and Number objects that serve as a whitelist for selecting/filtering the properties of the value object to be included in the JSON5 string. If this value is null or not provided, all properties of the object are included in the resulting JSON5 string.
  • space: A String or Number object that's used to insert white space into the output JSON5 string for readability purposes. If this is a Number, it indicates the number of space characters to use as white space; this number is capped at 10 (if it is greater, the value is just 10). Values less than 1 indicate that no space should be used. If this is a String, the string (or the first 10 characters of the string, if it's longer than that) is used as white space. If this parameter is not provided (or is null), no white space is used. If white space is used, trailing commas will be used in objects and arrays.
  • options: An object with the following properties:
    • replacer: Same as the replacer parameter.
    • space: Same as the space parameter.
    • quote: A String representing the quote character to use when serializing strings.

Return value

A JSON5 string representing the value.

Node.js require() JSON5 files

When using Node.js, you can require() JSON5 files by adding the following statement.

require('json5/lib/register')

Then you can load a JSON5 file with a Node.js require() statement. For example:

const config = require('./config.json5')

CLI

Since JSON is more widely used than JSON5, this package includes a CLI for converting JSON5 to JSON and for validating the syntax of JSON5 documents.

Installation

npm install --global json5

Usage

json5 [options] <file>

If <file> is not provided, then STDIN is used.

Options:

  • -s, --space: The number of spaces to indent or t for tabs
  • -o, --out-file [file]: Output to the specified file, otherwise STDOUT
  • -v, --validate: Validate JSON5 but do not output JSON
  • -V, --version: Output the version number
  • -h, --help: Output usage information

Contributing

Development

git clone https://github.com/json5/json5
cd json5
npm install

When contributing code, please write relevant tests and run npm test and npm run lint before submitting pull requests. Please use an editor that supports EditorConfig.

Issues

To report bugs or request features regarding the JSON5 data format, please submit an issue to the official specification repository.

Note that we will never add any features that make JSON5 incompatible with ES5; that compatibility is a fundamental premise of JSON5.

To report bugs or request features regarding this JavaScript implementation of JSON5, please submit an issue to this repository.

Security Vulnerabilities and Disclosures

To report a security vulnerability, please follow the follow the guidelines described in our security policy.

License

MIT. See LICENSE.md for details.

Credits

Aseem Kishore founded this project. He wrote a blog post about the journey and lessons learned 10 years in.

Michael Bolin independently arrived at and published some of these same ideas with awesome explanations and detail. Recommended reading: Suggested Improvements to JSON

Douglas Crockford of course designed and built JSON, but his state machine diagrams on the JSON website, as cheesy as it may sound, gave us motivation and confidence that building a new parser to implement these ideas was within reach! The original implementation of JSON5 was also modeled directly off of Doug’s open-source json_parse.js parser. We’re grateful for that clean and well-documented code.

Max Nanasy has been an early and prolific supporter, contributing multiple patches and ideas.

Andrew Eisenberg contributed the original stringify method.

Jordan Tucker has aligned JSON5 more closely with ES5, wrote the official JSON5 specification, completely rewrote the codebase from the ground up, and is actively maintaining this project.