csvtojson 2.0.10

csvtojson is a comprehensive Node.js module primarily used for converting CSV data to JSON or column arrays. It follows the strict CSV definition RF4180 and is built to work with substantial lines of CSV data. The module provides a plethora of parsing parameters as well as support for async and streaming parsing. Additionally, it encompasses a built-in CSV parsing tool for command-line usage and provides a CSV parser for both Node.js and web browsers. It presents options for developers such as 'pre-defined' helpers and flexibility in usage. Furthermore, it emphasizes high-speed performance, making it an optimal choice for large datasets.

The usage of the csvtojson module is quite straightforward. After installing the module using npm (npm i --save csvtojson), it can be imported for use within your JavaScript code. The basic usage involves calling a function provided from the csvtojson package and invoking fromFile() or fromStream() to read from a CSV file or a stream, and then() to handle the parsed JSON objects.

Here's an example of reading from a CSV file:

const csv=require('csvtojson')
const csvFilePath='<path to csv file>'

csv()
.fromFile(csvFilePath)
.then((jsonObj) => {
	console.log(jsonObj);
})

You can also read from a CSV string or a stream, or process each line from a CSV URL asynchronously:

const request=require('request')
const csv=require('csvtojson')

csv()
.fromStream(request.get('http://mywebsite.com/mycsvfile.csv'))
.subscribe((json)=>{
	return new Promise((resolve,reject)=>{
		// long operation for each json e.g. transform / write into database.
	})
},onError,onComplete);

For more detailed usage, please refer to the package's API documentation.

The csvtojson module's documentation can be found on the GitHub page of the project, under the URL: https://github.com/Keyang/node-csvtojson. The documentation is very detailed and covers a wide variety of usage examples, including installation, quick start, API, browser usage, and other parameters. There are also guides for upgrading to version 2 as well as specific documentation for version 1, should developers be using that version.