Converted the library from CoffeeScript to ES6

Author: abstractvector

.travis.yml

@@ -1,11 +1,7 @@
 language: node_js
 node_js:
-  - "6"
-  - "6.1"
-  - "6.0"
-  - "5"
-  - "5.1"
-  - "4"
-  - "0.12"
-  - "0.11"
   - "node"
+  - "lts/*"
+  - "9"
+  - "8"
+  - "7"

Cakefile

@@ -1,5 +1,5 @@
-node-dbf
-========
+DBF Parser
+==========
 
 This is an event-based dBase file parser for very efficiently reading data from `*.dbf` files.
 
@@ -8,25 +8,29 @@ This is an event-based dBase file parser for very efficiently reading data from
   [![NPM Version][npm-image]][npm-url]
   [![NPM Downloads][downloads-image]][downloads-url]
 
-The codebase is written in CoffeeScript but compiled in the npm module so CoffeeScript is not a dependency in production.
+The codebase is written in ES6 JavaScript but compiled in the npm module to pure JavaScript.
 
 To get started, simply install the module using npm:
 
-    npm install node-dbf
+```bash
+$ npm install node-dbf
+```
 
-and then `require` it:
+and then `import` it:
 
-    var Parser = require('node-dbf');
+```js
+import Parser from 'node-dbf';
+```
 
-#Classes
+# Classes
 
 There are two classes - the `Parser` and the `Header`. The `Parser` is the most interesting class.
 
-##Parser
+## Parser
 
 This class is the main interface for reading data from dBase files. It extends `EventEmitter` and its output is via events.
 
-###new Parser(path, options)
+### new Parser(path, options)
 
 * path `String` The full path to the DBF file to parse
 * options `Object` An object containing options for the parser.
@@ -37,36 +41,36 @@ The support options are:
 
 Creates a new Parser and attaches it to the specified filename.
 
-    var Parser = require('node-dbf');
+    import Parser from 'node-dbf';
 
-    var parser = new Parser('/path/to/my/dbase/file.dbf');
+    let parser = new Parser('/path/to/my/dbase/file.dbf');
 
-###parser.on(event, listener)
+### parser.on(event, listener)
 
 * event `String` The event name to listen for (see below for details)
 * listener `Function` The callback to bind to the event
 
 This method is inherited from the `EventEmitter` class.
 
-###parser.parse()
+### parser.parse()
 
 Call this method once you have bound to the events you are interested in. Although it returns the parser object (for chaining), all the dBase data is outputted via events.
 
     parser.parse();
 
-###Event: 'start'
+### Event: 'start'
 
 * parser `Parser` The parser object
 
 This event is emitted as soon as the `parser.parse()` method has been invoked.
 
-###Event: 'header'
+### Event: 'header'
 
 * header `Header` The header object as parsed from the dBase file
 
 This event is emitted once the header has been parsed from the dBase file
 
-###Event: 'record'
+### Event: 'record'
 
 * record `Object` An object representing the record that has been found
 
@@ -78,65 +82,74 @@ In addition to the fields, the object contains two special keys:
 * @deleted `Boolean` whether this record has been deleted or not
 
 This object may look like:
+```json
+{
+    "@sequenceNumber": 123,
+    "@deleted": false,
+    "firstName": "John",
+    "lastName": "Smith"
+}
+```
 
-    {
-        "@sequenceNumber": 123,
-        "@deleted": false,
-        "firstName": "John",
-        "lastName": "Smith
-    }
-
-###Event: 'end'
+### Event: 'end'
 
 * parser `Parser` The parser object
 
 This event is fired once the dBase parsing is complete and there are no more records remaining.
 
-##Usage
+## Usage
 
 The following code example illustrates a very simple usage for this module:
 
-    var Parser = require('node-dbf');
-    
-    var parser = new Parser('/path/to/my/dbase/file.dbf');
-    
-    parser.on('start', function(p) {
-        console.log('dBase file parsing has started');
-    });
-    
-    parser.on('header', function(h) {
-        console.log('dBase file header has been parsed');
-    });
-    
-    parser.on('record', function(record) {
-        console.log('Name: ' + record.firstName + ' ' + record.lastName); // Name: John Smith
-    });
-    
-    parser.on('end', function(p) {
-        console.log('Finished parsing the dBase file');
-    });
-    
-    parser.parse();
+```js
+import Parser from 'node-dbf';
+
+let parser = new Parser('/path/to/my/dbase/file.dbf');
+
+parser.on('start', (p) => {
+    console.log('dBase file parsing has started');
+});
+
+parser.on('header', (h) => {
+    console.log('dBase file header has been parsed');
+});
+
+parser.on('record', (record) => {
+    console.log('Name: ' + record.firstName + ' ' + record.lastName); // Name: John Smith
+});
+
+parser.on('end', (p) => {
+    console.log('Finished parsing the dBase file');
+});
+
+parser.parse();
+```
 
-#Command-Line Interface (CLI)
+# Command-Line Interface (CLI)
 
 The parser also supports a command-line interface (CLI) for converting DBF files to CSV. You can invoke it as follows:
 
-    $ node-dbf convert /path/to/file.dbf
+```bash
+$ node-dbf convert /path/to/file.dbf
+```
 
 This will write the converted rows to `stdout` and metadata about the process (e.g. number of rows, etc) to `stderr`. This allows you to write stdout directly to an output file, for example:
 
-    $ node-dbf convert file.dbf > file.csv
+```bash
+$ node-dbf convert file.dbf > file.csv
+```
 
 For more help information on using the command line options, use the integrated help:
 
-    $ node-dbf help
+```bash
+$ node-dbf help
+```
 
-#Tests
+# Tests
 
 Tests are written in Mocha using Chai BDD for the expectations. Data on San Francisco zip codes was used as a reference test file - downloaded from [SF OpenData](https://data.sfgov.org/) and included in the `./test/fixtures/bayarea_zipcodes.dbf` file within the repository.
 
-#TODO
+# To Do
 
 * Add more tests
 * Add support for field types other than Character and Numeric

README.md

@@ -23,7 +23,7 @@ var wrap = function(t) {
   return [quote, t, quote].join('');
 };
 
-var Parser = require('../lib/parser.js');
+var Parser = require('../lib/parser').default;
 var fields;
 
 var timeStart = process.hrtime();