A JSON to CSV and CSV to JSON converter that natively supports sub-documents and auto-generates the CSV heading.
npm install json-2-csv
This node module will convert an array of JSON documents to a CSV string.
Column headings will be automatically generated based on the keys of the JSON documents. Nested documents will have a '.' appended between the keys.
It is also capable of converting CSV of the same form back into the original array of JSON documents.
The columns headings will be used as the JSON document keys. All lines must have the same exact number of CSV values.
``bash`
$ npm install json-2-csv
CLI:
`bash`
$ npm install @mrodrig/json-2-csv-cli
Upgrading to v5 from v4? Check out the upgrade guide.
`javascript`
let converter = require('json-2-csv');
const csv = await converter.json2csv(data, options);
orjavascript`
import { json2csv } from 'json-2-csv';
#### json2csv(array, options) => string
Returns the CSV string or rejects with an Error if there was an issue.
* array - An array of JSON documents to be converted to CSV.options
* - (Optional) A JSON document specifying any of the following key value pairs:arrayIndexesAsKeys
* - Boolean - Should array indexes be included in the generated keys?false
* Default:
* Note: This provides a more accurate representation of the JSON in the returned CSV, but may be less human readable. See #207 for more details.
* - Boolean - Should all documents have the same schema?false
* Default:
* Note: An error will be thrown if some documents have differing schemas when this is set to .delimiter
* - Document - Specifies the different types of delimitersfield
* - String - Field Delimiter. ,
* Default:
* - String - Wrap values in the delimiter of choice (e.g. wrap values in quotes). "
* Default:
* - String - End of Line Delimiter. \n
* Default:
* - Any - Value that, if specified, will be substituted in for field values that are undefined, null, or an empty string.escapeHeaderNestedDots
* Default: none
* - Boolean - Should nested dots in header keys be escaped?true
* Default:
* Example:
json`
[
{
"a.a": "1"
}
]
* will generate the following CSV:`
csv`
a\.a
1
* will generate the following CSV:`
csv`
a.a
1
* Note: This may result in CSV output that does not map back exactly to the original JSON.
* - Boolean - Should a unicode character be prepended to allow Excel to open a UTF-8 encoded file with non-ASCII characters present.excludeKeys
* - Array - Specify the string keys or RegExp patterns that should be excluded from the output. Provided string keys will also be used as a RegExp to help exclude keys under a specified prefix, such as all keys of Objects in an Array when expandArrayObjects is true (e.g., providing 'baz' will exclude 'baz.a' too).[]
* Default:
* Note: When used with , arrays present at excluded key paths will not be unwound.expandNestedObjects
* - Boolean - Should nested objects be deep-converted to CSV?true
* Default:
* Example:
json`
[
{
"make": "Nissan",
"model": "Murano",
"year": 2013,
"specifications": {
"mileage": 7106,
"trim": "S AWD"
}
}
]
* uses the following keys:['make', 'model', 'year', 'specifications.mileage', 'specifications.trim']
*
* uses the following keys:['make', 'model', 'year', 'specifications']
*
* Note: This may result in CSV output that does not map back exactly to the original JSON.
* - Boolean - Should objects in array values be deep-converted to CSV?false
* Default:
* Example:
json`
[
{
"specifications": [
{ "features": [...] },
{ "mileage": "5000" }
]
}
]
* uses the following keys:['specifications.features', 'specifications.mileage']
*
* uses the following keys:['specifications']
*
* Note: This may result in CSV output that does not map back exactly to the original JSON. See #102 for more information.
* - Object - Specify field titles that should be renamed.{}
* Default:
* Example:
* - Array - Specify the keys that should be converted.`
* Default: These will be auto-detected from your data by default.
* Keys can either be specified as a String representing the key path that should be converted, or as an Object of the following format:
javascript`
{
"field": "string", // required
"title": "string", // optional
"wildcardMatch": false, // optional - default: false
}
* When specifying keys as an Object, the property specifies the key path, while title specifies a more human readable field heading. Additionally, the wildcardMatch option allows you to optionally specify that all auto-detected fields with the specified field prefix should be included in the CSV. The list specified can contain a combination of Objects and Strings.[ 'key1', 'key2', ... ]
* Examples:
*
*
*
* Key Paths - If you are converting a nested object (ie. {info : {name: 'Mike'}}), then set this to ['info.name']
* - Function - Specify how values should be converted into CSV format. This function is provided a single field value at a time and must return a String. The built-in parsing method is provided as the second argument for cases where default parsing is preferred.useDateIso8601Format
* Default: A built-in method is used to parse out a variety of different value types to well-known formats.
* Note: Using this option may override other options, including and useLocaleFormat.prependHeader
* - Boolean - Should the auto-generated header be prepended as the first line in the CSV?true
* Default:
* - Boolean or Function - Should the header keys be sorted in alphabetical order? or pass a function to use a custom sorting functionfalse
* Default:
* - Boolean - Should the field values be trimmed?false
* Default:
* - Boolean - Should the header fields be trimmed? false
* Default:
* - Boolean - Should array values be "unwound" such that there is one line per value in the array?false
* Default:
* Example:
json`
[
{
"_id": {"$oid": "5cf7ca3616c91100018844af"},
"data": {"category": "Computers", "options": [{"name": "MacBook Pro 15"}, {"name": "MacBook Air 13"}]}
},
{
"_id": {"$oid": "5cf7ca3616c91100018844bf"},
"data": {"category": "Cars", "options": [{"name": "Supercharger"}, {"name": "Turbocharger"}]}
}
]
* will unwind the JSON to four objects, and therefore four lines of CSV values:`
csv`
_id.$oid,data.category,data.options.name
5cf7ca3616c91100018844af,Computers,MacBook Pro 15
5cf7ca3616c91100018844af,Computers,MacBook Air 13
5cf7ca3616c91100018844bf,Cars,Supercharger
5cf7ca3616c91100018844bf,Cars,Turbocharger
* will leave the values unwound and will convert the array as-is (when this option is used without expandArrayObjects):`
csv`
_id.$oid,data.category,data.options
5cf7ca3616c91100018844af,Computers,"[{""name"":""MacBook Pro 15""},{""name"":""MacBook Air 13""}]"
5cf7ca3616c91100018844bf,Cars,"[{""name"":""Supercharger""},{""name"":""Turbocharger""}]"
* Note: This may result in CSV output that does not map back exactly to the original JSON.
* - Boolean - Should date values be converted to an ISO8601 date string?false
* Default:
* Note: If selected, values will be converted using rather than toString() or toLocaleString() depending on the other options provided.useLocaleFormat
* - Boolean - Should values be converted to a locale specific string?false
* Default:
* Note: If selected, values will be converted using rather than toString()
* - Boolean - Should boolean values be wrapped in wrap delimiters to prevent Excel from converting them to Excel's TRUE/FALSE Boolean values.false
* Default:
* - Boolean - Should CSV injection be prevented by left trimming these characters: Equals (=), Plus (+), Minus (-), At (@), Tab (0x09), Carriage return (0x0D).false
* Default:
#### csv2json(csv, options) => object[]
Returns the JSON object array (object[]) or rejects with an Error if there was an issue.
* csv - A string of CSVoptions
* - (Optional) A JSON document specifying any of the following key value pairs:delimiter
* - Document - Specifies the different types of delimitersfield
* - String - Field Delimiter. ,
* Default:
* - String - The character that field values are wrapped in. "
* Default:
* - String - End of Line Delimiter. \n
* Default:
* - Boolean - Does the CSV contain a unicode character prepended in order to allow Excel to open a UTF-8 encoded file with non-ASCII characters present?false
* Default:
* - Array - Specify the field names (as strings) in place of a header line in the CSV itself.{info : {name: 'Mike'}}
* Default: Parses the header fields directly from the CSV string
* If you want to generate a nested object (ie. ), then use . characters in the string to denote a nested field, like ['info.name']keys
* If your CSV has a header line included, then don't specify the option to utilize the default values that will be parsed from the CSV.
* - Array - Specify the keys (as strings) that should be converted. null
* Default:
* If you have a nested object (ie. ), then set this to ['info.name']
* If you want all keys to be converted, then specify or don't specify the option to utilize the default.parseValue
* - Function - Specify how String representations of field values should be parsed when converting back to JSON. This function is provided a single String and can return any value.JSON.parse
* Default: - An attempt is made to convert the String back to its original value using JSON.parse.trimHeaderFields
* - Boolean - Should the header fields be trimmed? false
* Default:
* - Boolean - Should the field values be trimmed? false
* Default:
, the command line interface functionality has been pulled out to a separate package. Please be sure to
install the @mrodrig/json-2-csv-cli NPM package if you wish to use the CLI functionality shown below:`bash
$ npm install @mrodrig/json-2-csv-cli
` #### json2csv
`
Usage: json2csv [options]Arguments:
jsonFile JSON file to convert
Options:
-V, --version output the version number
-o, --output [output] Path of output file. If not provided, then stdout will be used
-a, --array-indexes-as-keys Includes array indexes in the generated keys
-S, --check-schema Check for schema differences
-f, --field Field delimiter
-w, --wrap Wrap delimiter
-e, --eol End of Line delimiter
-E, --empty-field-value Empty field value
-n, --expand-nested-objects Expand nested objects to be deep converted to CSV
-k, --keys [keys] Keys of documents to convert to CSV
-d, --escape-header-nested-dots Escape header nested dots
-b, --excel-bom Excel Byte Order Mark character prepended to CSV
-x, --exclude-keys [keys] Comma separated list of keys to exclude
-A, --expand-array-objects Expand array objects
-W, --without-header Withhold the prepended header
-p, --prevent-csv-injection Prevent CSV Injection
-s, --sort-header Sort the header fields
-F, --trim-fields Trim field values
-H, --trim-header Trim header fields
-U, --unwind-arrays Unwind array values to their own CSV line
-I, --iso-date-format Use ISO 8601 date format
-L, --locale-format Use locale format for values
-B, --wrap-booleans Wrap booleans
-h, --help display help for command
#### csv2json
Usage: csv2json [options]Arguments:
csvFile CSV file to convert
Options:
-V, --version output the version number
-o, --output [output] Path of output file. If not provided, then stdout will be used
-f, --field Field delimiter
-w, --wrap Wrap delimiter
-e, --eol End of Line delimiter
-b, --excel-bom Excel Byte Order Mark character prepended to CSV
-p, --prevent-csv-injection Prevent CSV Injection
-F, --trim-fields Trim field values
-H, --trim-header Trim header fields
-h, --header-fields Specify the fields names in place a header line in the CSV itself
-k, --keys [keys] Keys of documents to convert to CSV
--help display help for command
Tests
bash
$ npm test
`To see test coverage, please run:
bash
$ npm run coverage
`Features
* Header Generation (per document keys)
* Allows for conversion of specific keys in both json2csv and csv2json via the options.keys parameter (as of 1.1.2)
* Document schema verification functionality (field order is irrelevant) (as of 1.1.0)
* Supports sub-documents natively
* Supports arrays as document values for both json2csv and csv2json
* Custom ordering of columns (see F.A.Q. for more information)
* Ability to re-generate the JSON documents that were used to generate the CSV (including nested documents)
* Allows for custom field delimiters, end of line delimiters, etc.
* Wrapped value support for json2csv and csv2json (as of 1.3.0)
* Support for multiple different schemas (as of 1.4.0)
* RFC 4180 Compliance (as of 3.0.0)
* CLI functionality (as of 3.0.0)
*
and*
*