everything-json - npm Package Compare versions

Comparing version 1.0.0-rc.0 to 1.0.0

CHANGELOG.md

 # Changelog
 
-# [1.0.0]
+# [1.0.0] 2023-10-30
 
@@ -8,2 +8,3 @@ - Implement an object store keeping weak references to all objects returned to JavaScript and reusing them when possible
  - Allow the suppression of the exception in `.path()`
+ - Fix [#15](https://github.com/mmomtchev/everything-json/issues/15), `.toObjectAsync()` crash on empty objects
 
@@ -10,0 +11,0 @@ ### [0.9.4] 2023-10-09

package.json

@@ -23,3 +23,3 @@ {
   "name": "everything-json",
-  "version": "1.0.0-rc.0",
+  "version": "1.0.0",
   "description": "JSON Async",
@@ -53,4 +53,4 @@ "repository": {
     "@types/mocha": "^10.0.2",
-    "@typescript-eslint/eslint-plugin": "^6.7.3",
-    "@typescript-eslint/parser": "^6.7.3",
+    "@typescript-eslint/eslint-plugin": "^6.7.4",
+    "@typescript-eslint/parser": "^6.7.4",
     "benny": "^3.7.1",
@@ -57,0 +57,0 @@ "c8": "^8.0.1",

README.md

@@ -176,3 +176,3 @@ # `everything-json`
 
-## `twitter.json` : deep JSON
+## `twitter.json` : JSON with lots of strings and a deep structure
 
@@ -195,2 +195,8 @@ | / | Builtin `JSON.parse()` | `everything-json` from `Buffer` | `everything-json` from UTF8 string | `simdjson` | `yieldable-json` |
 
+# Is a browser WASM version feasible?
+
+Although possible, it won't match the performance of the native Node.js version and it is not planned at the moment.
+
+The solution would be to have a pre-spawned Web Worker that is going to run an eventual WASM port of `simdjson`. It will store its JSON tape in a `SharedArrayBuffer` which will be read by the main thread.
+
 # Copyright
@@ -197,0 +203,0 @@

Fixed alerts

No v1

Quality

Package is not semver >=1. This means it is not stable and does not support ^ ranges.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

5633260

increased by0.01%

Number of low quality alerts

0

decreased by-100%

Number of lines in readme file

209

increased by2.96%

No dependency changes