aba-generator - npm Package Compare versions

Comparing version 1.0.3 to 1.0.4

package.json

 {
   "name": "aba-generator",
-  "version": "1.0.3",
+  "version": "1.0.4",
   "description": "ABA file generator",
@@ -21,3 +21,3 @@ "main": "index.js",
   "dependencies": {
-    "printf": "^0.5.3"
+    "printf": "^0.6.0"
   },
@@ -24,0 +24,0 @@ "devDependencies": {

README.md

 # ABA generator
 
-Generate ABA Files from Node.js
+Generate ABA Files from Node.js and browser.
 
@@ -66,3 +66,3 @@ Notable:
 
-which is a fully valid ABA file. (There should be spaces in the end of the first and last rows, but are not rendered in Markdown).
+which is a fully valid ABA file. Note spaces in the end of the first and last lines.
 
@@ -73,3 +73,3 @@ Every line in the ABA file must be 120 chars. So data like `user`, `description`, `accountTitle`, etc are truncated if too long.
 
-Even though the format is standardised, bank typically mandate some of the fields to be hardcoded.
+Even though the format is standardised, banks typically mandate some fields to be hardcoded.
 
@@ -102,3 +102,3 @@ ## ABA file specification
 
-Transactions schema. Most of the params are required as yo ucan see.
+Transactions schema. Most of the params are required as you can see.
 
@@ -114,3 +114,3 @@ ```
  * @param transactions[].accountTitle {String} The third party (recipient) account name. Up to 32 chars.
- * @param transactions[].reference {String} Payment reference, e.g. "Invoice # 123". Up to 18 chars.
+ * @param [transactions[].reference] {String} Payment reference, e.g. "Invoice # 123". Up to 18 chars.
  * @param transactions[].traceBsb {String} The transacting account BSB
@@ -117,0 +117,0 @@ * @param transactions[].traceAccount {String} The transacting account number

No alert changes

Worsened metrics

Total package byte prevSize

23428

decreased by-0.16%

Dependency changes

• + Addedprintf@0.6.1(transitive)

• - Removedprintf@0.5.3(transitive)

• Updatedprintf@^0.6.0