@area17/parse-numeric-date - npm Package Compare versions

Comparing version 0.0.4 to 0.0.5

package.json

 {
   "name": "@area17/parse-numeric-date",
-  "version": "0.0.4",
+  "version": "0.0.5",
   "description": "Parse numeric based date inputs",
@@ -8,4 +8,4 @@ "type": "module",
   "exports": {
-      "require": "./dist/parse-numeric-date.cjs",
-      "default": "./dist/parse-numeric-date.modern.js"
+    "require": "./dist/parse-numeric-date.cjs",
+    "default": "./dist/parse-numeric-date.modern.js"
   },
@@ -16,7 +16,5 @@ "main": "./dist/parse-numeric-date.cjs",
   "scripts": {
-      "build": "microbundle",
-      "dev": "microbundle watch",
-      "devdebug": "microbundle watch --compress false",
-      "test": "jest",
-      "format": "prettier --write . '!dist/**/*'"
+    "build": "microbundle",
+    "dev": "microbundle watch",
+    "devdebug": "microbundle watch --compress false"
   },
@@ -23,0 +21,0 @@ "repository": {

README.md

 # parse-numeric-date
 
-Parse numeric based date inputs.
+Micro library to parse numeric based date inputs - ~4kb minified/~1kb gzip
 
@@ -81,7 +81,8 @@ ## Mission Statement
 
-`parse-numeric-date` can't take natural input such as "December 12, 2022" - it is purely for parsing numeric inputs. Another assumption here is that such date entry, although natural in speech, isn't so natural to write or type - especially if the keyboard has been switched to a numeric keyboard on the users device.
+`parse-numeric-date` can't take natural input such as "December 12, 2022" - it is purely for parsing numeric inputs. Another assumption here is that such date entry, although natural in speech, isn't so natural to type - especially if the keyboard has been switched to a numeric keyboard on the users device.
 
 If you want such parsing, perhaps you need:
-* [`parse-numeric-date`](https://github.com/kensnyder/any-date-parser)
+* [`anyDateParser`](https://github.com/kensnyder/any-date-parser)
 * [`parse-dob`](https://github.com/HenrikJoreteg/parse-dob)
+* [`chrono-node`](https://github.com/wanasit/chrono)
 
@@ -92,3 +93,3 @@ Both are excellent, but can't parse numeric dates quite as fully as `parse-numeric-date`.
 
-You can see a comparison between [`parse-numeric-date`](https://github.com/kensnyder/any-date-parser) and `anyDateParser` and [`parse-dob`](https://github.com/HenrikJoreteg/parse-dob) over on Codepen: [Date parse testing](https://codepen.io/13twelve/pen/rNrRoLB?editors=0010)
+You can see a comparison between `parse-numeric-date`, [`anyDateParser`](https://github.com/kensnyder/any-date-parser), [`parse-dob`](https://github.com/HenrikJoreteg/parse-dob) and [`chrono-node`](https://github.com/wanasit/chrono) over on Codepen: [Date parse testing](https://codepen.io/13twelve/pen/rNrRoLB?editors=0010)
 
@@ -95,0 +96,0 @@ `parse-dob` by [@HenrikJoreteg](https://github.com/HenrikJoreteg) was a great inspiration, we think that forking `parse-dob` and removing the previous date restriction would be very interesting.

No alert changes

Improved metrics

Total package byte prevSize

126521

0.04%

Number of lines in readme file

104

0.97%

No dependency changes