@teambit/ipc-events 1.0.310 → 1.0.311

package/artifacts/__bit_junit.xml

@@ -1,4 +1,4 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <testsuites tests="0" failures="0" errors="0" skipped="0">
-  <testsuite name="teambit.harmony/ipc-events@1.0.310" tests="0" failures="0" errors="0" skipped="0"/>
+  <testsuite name="teambit.harmony/ipc-events@1.0.311" tests="0" failures="0" errors="0" skipped="0"/>
 </testsuites>

package/artifacts/schema.json

@@ -36,7 +36,8 @@
               "character": 1
             },
             "raw": "/**\n * imagine you have multiple processes running in the background, such as `bit watch`, `bit start`, `bit server`.\n * the user is running `bit install` from the cli, how do you let these processes know that the installation is complete?\n * `bit start` for instance could use ths info to clear the \"component issues\" of the components that were missing packages.\n *\n * this class provides a mechanism to achieve this by writing the event into the filesystem (`.bit/events/event-name`),\n * while each one of the processes has a watcher in the background watch this file. once they got the data from the watcher,\n * they can act upon it.\n *\n * in the previous example, when the user is running `bit install`, the install aspect runs `this.publishIpcEvent` to\n * write `.bit/events/onPostInstall` to the filesystem. then, the watcher of `bit start` process got a notification\n * that this file has changed/added and it runs `triggerGotEvent` to run all aspects registered to its gotEventSlot.\n * the installer in turn is registered to this slot and once its function is triggered, it check whether the eventName\n * is onPostInstall and then triggers its own OnPostInstall slot.\n */",
-            "comment": "imagine you have multiple processes running in the background, such as `bit watch`, `bit start`, `bit server`.\nthe user is running `bit install` from the cli, how do you let these processes know that the installation is complete?\n`bit start` for instance could use ths info to clear the \"component issues\" of the components that were missing packages.\n\nthis class provides a mechanism to achieve this by writing the event into the filesystem (`.bit/events/event-name`),\nwhile each one of the processes has a watcher in the background watch this file. once they got the data from the watcher,\nthey can act upon it.\n\nin the previous example, when the user is running `bit install`, the install aspect runs `this.publishIpcEvent` to\nwrite `.bit/events/onPostInstall` to the filesystem. then, the watcher of `bit start` process got a notification\nthat this file has changed/added and it runs `triggerGotEvent` to run all aspects registered to its gotEventSlot.\nthe installer in turn is registered to this slot and once its function is triggered, it check whether the eventName\nis onPostInstall and then triggers its own OnPostInstall slot."
+            "comment": "imagine you have multiple processes running in the background, such as `bit watch`, `bit start`, `bit server`.\nthe user is running `bit install` from the cli, how do you let these processes know that the installation is complete?\n`bit start` for instance could use ths info to clear the \"component issues\" of the components that were missing packages.\n\nthis class provides a mechanism to achieve this by writing the event into the filesystem (`.bit/events/event-name`),\nwhile each one of the processes has a watcher in the background watch this file. once they got the data from the watcher,\nthey can act upon it.\n\nin the previous example, when the user is running `bit install`, the install aspect runs `this.publishIpcEvent` to\nwrite `.bit/events/onPostInstall` to the filesystem. then, the watcher of `bit start` process got a notification\nthat this file has changed/added and it runs `triggerGotEvent` to run all aspects registered to its gotEventSlot.\nthe installer in turn is registered to this slot and once its function is triggered, it check whether the eventName\nis onPostInstall and then triggers its own OnPostInstall slot.",
+            "tags": []
           },
           "signature": "class IpcEventsMain",
           "name": "IpcEventsMain",
@@ -190,7 +191,8 @@
                   "character": 3
                 },
                 "raw": "/**\n   * this gets called from the watcher only.\n   * as soon as the watcher finds out that a new event has been written to the filesystem, it triggers this function\n   */",
-                "comment": "this gets called from the watcher only.\nas soon as the watcher finds out that a new event has been written to the filesystem, it triggers this function"
+                "comment": "this gets called from the watcher only.\nas soon as the watcher finds out that a new event has been written to the filesystem, it triggers this function",
+                "tags": []
               },
               "signature": "(method) IpcEventsMain.triggerGotEvent(eventName: EventName): Promise<void>",
               "name": "triggerGotEvent",
@@ -245,7 +247,8 @@
                   "character": 3
                 },
                 "raw": "/**\n   * write event data into the filesystem, so then other processes, such as \"bit start\", \"bit watch\", could use the\n   * watcher to get the event data.\n   */",
-                "comment": "write event data into the filesystem, so then other processes, such as \"bit start\", \"bit watch\", could use the\nwatcher to get the event data."
+                "comment": "write event data into the filesystem, so then other processes, such as \"bit start\", \"bit watch\", could use the\nwatcher to get the event data.",
+                "tags": []
               },
               "signature": "(method) IpcEventsMain.publishIpcEvent(eventName: EventName, data?: Record<string, any>): Promise<void>",
               "name": "publishIpcEvent",
@@ -607,7 +610,8 @@
               "character": 1
             },
             "raw": "/**\n * imagine you have multiple processes running in the background, such as `bit watch`, `bit start`, `bit server`.\n * the user is running `bit install` from the cli, how do you let these processes know that the installation is complete?\n * `bit start` for instance could use ths info to clear the \"component issues\" of the components that were missing packages.\n *\n * this class provides a mechanism to achieve this by writing the event into the filesystem (`.bit/events/event-name`),\n * while each one of the processes has a watcher in the background watch this file. once they got the data from the watcher,\n * they can act upon it.\n *\n * in the previous example, when the user is running `bit install`, the install aspect runs `this.publishIpcEvent` to\n * write `.bit/events/onPostInstall` to the filesystem. then, the watcher of `bit start` process got a notification\n * that this file has changed/added and it runs `triggerGotEvent` to run all aspects registered to its gotEventSlot.\n * the installer in turn is registered to this slot and once its function is triggered, it check whether the eventName\n * is onPostInstall and then triggers its own OnPostInstall slot.\n */",
-            "comment": "imagine you have multiple processes running in the background, such as `bit watch`, `bit start`, `bit server`.\nthe user is running `bit install` from the cli, how do you let these processes know that the installation is complete?\n`bit start` for instance could use ths info to clear the \"component issues\" of the components that were missing packages.\n\nthis class provides a mechanism to achieve this by writing the event into the filesystem (`.bit/events/event-name`),\nwhile each one of the processes has a watcher in the background watch this file. once they got the data from the watcher,\nthey can act upon it.\n\nin the previous example, when the user is running `bit install`, the install aspect runs `this.publishIpcEvent` to\nwrite `.bit/events/onPostInstall` to the filesystem. then, the watcher of `bit start` process got a notification\nthat this file has changed/added and it runs `triggerGotEvent` to run all aspects registered to its gotEventSlot.\nthe installer in turn is registered to this slot and once its function is triggered, it check whether the eventName\nis onPostInstall and then triggers its own OnPostInstall slot."
+            "comment": "imagine you have multiple processes running in the background, such as `bit watch`, `bit start`, `bit server`.\nthe user is running `bit install` from the cli, how do you let these processes know that the installation is complete?\n`bit start` for instance could use ths info to clear the \"component issues\" of the components that were missing packages.\n\nthis class provides a mechanism to achieve this by writing the event into the filesystem (`.bit/events/event-name`),\nwhile each one of the processes has a watcher in the background watch this file. once they got the data from the watcher,\nthey can act upon it.\n\nin the previous example, when the user is running `bit install`, the install aspect runs `this.publishIpcEvent` to\nwrite `.bit/events/onPostInstall` to the filesystem. then, the watcher of `bit start` process got a notification\nthat this file has changed/added and it runs `triggerGotEvent` to run all aspects registered to its gotEventSlot.\nthe installer in turn is registered to this slot and once its function is triggered, it check whether the eventName\nis onPostInstall and then triggers its own OnPostInstall slot.",
+            "tags": []
           },
           "signature": "class IpcEventsMain",
           "name": "IpcEventsMain",
@@ -761,7 +765,8 @@
                   "character": 3
                 },
                 "raw": "/**\n   * this gets called from the watcher only.\n   * as soon as the watcher finds out that a new event has been written to the filesystem, it triggers this function\n   */",
-                "comment": "this gets called from the watcher only.\nas soon as the watcher finds out that a new event has been written to the filesystem, it triggers this function"
+                "comment": "this gets called from the watcher only.\nas soon as the watcher finds out that a new event has been written to the filesystem, it triggers this function",
+                "tags": []
               },
               "signature": "(method) IpcEventsMain.triggerGotEvent(eventName: EventName): Promise<void>",
               "name": "triggerGotEvent",
@@ -816,7 +821,8 @@
                   "character": 3
                 },
                 "raw": "/**\n   * write event data into the filesystem, so then other processes, such as \"bit start\", \"bit watch\", could use the\n   * watcher to get the event data.\n   */",
-                "comment": "write event data into the filesystem, so then other processes, such as \"bit start\", \"bit watch\", could use the\nwatcher to get the event data."
+                "comment": "write event data into the filesystem, so then other processes, such as \"bit start\", \"bit watch\", could use the\nwatcher to get the event data.",
+                "tags": []
               },
               "signature": "(method) IpcEventsMain.publishIpcEvent(eventName: EventName, data?: Record<string, any>): Promise<void>",
               "name": "publishIpcEvent",
@@ -1340,7 +1346,7 @@
   "componentId": {
     "scope": "teambit.harmony",
     "name": "ipc-events",
-    "version": "1.0.310"
+    "version": "1.0.311"
   },
   "taggedModuleExports": []
 }

package/package.json

@@ -1,20 +1,20 @@
 {
   "name": "@teambit/ipc-events",
-  "version": "1.0.310",
+  "version": "1.0.311",
   "homepage": "https://bit.cloud/teambit/harmony/ipc-events",
   "main": "dist/index.js",
   "componentId": {
     "scope": "teambit.harmony",
     "name": "ipc-events",
-    "version": "1.0.310"
+    "version": "1.0.311"
   },
   "dependencies": {
     "fs-extra": "10.0.0",
     "p-map-series": "2.1.0",
     "@teambit/harmony": "0.4.6",
-    "@teambit/cli": "0.0.887",
-    "@teambit/logger": "0.0.980",
-    "@teambit/scope": "1.0.310"
+    "@teambit/cli": "0.0.888",
+    "@teambit/logger": "0.0.981",
+    "@teambit/scope": "1.0.311"
   },
   "devDependencies": {
     "@types/fs-extra": "9.0.7",