zotero - npm Package Compare versions

Comparing version 0.0.2 to 0.0.3

lib/message.js

@@ -76,3 +76,3 @@ // --- Dependencies ---
    * The encoding of the response body, inferred from
-   * the response's `Content-Type` header. 
+   * the response's `Content-Type` header.
    *
@@ -91,3 +91,3 @@ * @property encoding
    * The file type of the response body's content, inferred
-   * from the response's `Content-Type` header. 
+   * from the response's `Content-Type` header.
    *
@@ -232,7 +232,7 @@ * This value is used to select a suitable message parser.
 
-  if (this.encoding) res.setEncoding(this.encoding);
+  //if (this.encoding) res.setEncoding(this.encoding);
 
   res.on('data', receiving);
 
-  res.once('end', function () {
+  res.once('end', function received() {
     debug('receiving response data complete: %d bytes read', size);
@@ -239,0 +239,0 @@

package.json

 {
   "name": "zotero",
-  "version": "0.0.2",
+  "version": "0.0.3",
   "description": "Zotero API client",
@@ -5,0 +5,0 @@ "main": "lib/zotero.js",

README.md

@@ -90,4 +90,4 @@ Zotero-Node
 using the appropriate encoding. Having said that, it is very easy to add your own message
-parsers to Zotero-Node, by addingthe them to `zotero.Messages.parsers`. For instance,
-we could add a parser for Atom resonses like this:
+parsers to Zotero-Node, by adding them to `zotero.Messages.parsers`. For instance,
+we could add a parser for Atom responses like this:
 
@@ -94,0 +94,0 @@

No alert changes

Worsened metrics

Total package byte prevSize

100008

decreased by-0.34%

Number of package files

24

decreased by-4%

No dependency changes