worker-timers - npm Package Compare versions

Comparing version 4.0.26 to 4.0.27

package.json

@@ -49,3 +49,3 @@ {
     "load-grunt-config": "^0.19.0",
-    "mocha": "^5.0.4",
+    "mocha": "^5.0.5",
     "rollup": "^0.57.1",
@@ -56,3 +56,3 @@ "rollup-plugin-babel": "^3.0.3",
     "ts-loader": "^4.1.0",
-    "tsconfig-holy-grail": "^4.0.1",
+    "tsconfig-holy-grail": "^4.0.2",
     "tslint": "^5.9.1",
@@ -94,3 +94,3 @@ "tslint-config-holy-grail": "^23.0.3",
   "types": "build/es2015/module.d.ts",
-  "version": "4.0.26"
+  "version": "4.0.27"
 }

README.md

@@ -63,1 +63,10 @@ # worker-timers
 of a server-side rendered React app.
+
+## Angular (& zone.js)
+
+If WorkerTimers are used inside of an Angular App and Zones are used to detect changes, the
+behavior of WorkerTimers can be confusing. Angular is using a Zone which is patching the native
+setInterval() and setTimeout() functions to get notified about the execution of their callback
+functions. But Angular (more specifically zone.js) is not aware of WorkerTimers and doesn't patch
+them. Therefore Angular needs to be notified manually about state changes that occur inside of a
+callback function which was scheduled with the help of WorkerTimers.

No alert changes

Improved metrics

Total package byte prevSize

22577

increased by2.6%

Number of lines in readme file

72

increased by14.29%

No dependency changes