chore: prelease mode + version

Author: Julien-R44

.changeset/pre.json

@@ -0,0 +1,13 @@
+{
+  "mode": "pre",
+  "tag": "next",
+  "initialVersions": {
+    "adonisjs": "0.0.0",
+    "@hot-hook/dump-viewer": "0.4.0",
+    "hot-hook": "0.4.0",
+    "@hot-hook/runner": "0.1.0"
+  },
+  "changesets": [
+    "pretty-cycles-show"
+  ]
+}

packages/dump_viewer/CHANGELOG.md

@@ -1,5 +1,12 @@
 # @hot-hook/dump-viewer
 
+## 0.4.1-next.0
+
+### Patch Changes
+
+- Updated dependencies [d66a6d6]
+  - [email protected]
+
 ## 0.4.0
 
 ### Patch Changes

packages/dump_viewer/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@hot-hook/dump-viewer",
   "type": "module",
-  "version": "0.4.0",
+  "version": "0.4.1-next.0",
   "author": "Julien Ripouteau <[email protected]>",
   "license": "MIT",
   "keywords": [

packages/hot_hook/CHANGELOG.md

@@ -1,5 +1,32 @@
 # hot-hook
 
+## 0.4.1-next.0
+
+### Patch Changes
+
+- d66a6d6: ## Global watching and file-changed events
+
+  Add support for "global watching" and "file-changed" events
+
+  Before this commit, Hot-hook only watched files after they were imported at runtime. Now, it directly watches all project files and sends a "file-changed" event whenever a file is modified, deleted, or added. This allows "runners" to react in various ways to file changes based on their needs.
+
+  The option to configure which files to watch is `include`, and by default is set to `["**/*"]`, meaning all files from the `rootDirectory`.
+
+  The behavior will be as follows:
+
+  - If the file has not yet been imported at runtime, and therefore is not part of the import graph, and it is modified, then a `hot-hook:file-changed` event will be emitted with the payload `{ path: string, action: "change" | "add" | "unlink"}`
+  - If the file has already been imported at runtime, and it is hot reloadable, then a `hot-hook:invalidated` event will be emitted with the payload `{ path: string }`. As before.
+  - If the file has already been imported at runtime and it is not hot reloadable, then `hot-hook:full-reload` will be emitted with the payload `{ path: string }`. As before.
+
+  ## Environment variables configuration
+
+  You can now configure certain environment variables for hot-hook, which are:
+
+  - `HOT_HOOK_IGNORE`: for the `ignore` option. Example: `HOT_HOOK_IGNORE=**/node_modules/**,**/dist/**`
+  - `HOT_HOOK_INCLUDE`: for the `include` option. Example: `HOT_HOOK_INCLUDE=**/*`
+  - `HOT_HOOK_BOUNDARIES`: for the `boundaries` option. Example: `HOT_HOOK_BOUNDARIES=./controllers/**/*.ts`
+  - `HOT_HOOK_RESTART`: for the `restart` option. Example: `HOT_HOOK_RESTART=.env,./config/**/*.ts`
+
 ## 0.4.0
 
 ### Minor Changes

packages/hot_hook/package.json

@@ -1,7 +1,7 @@
 {
   "name": "hot-hook",
   "type": "module",
-  "version": "0.4.0",
+  "version": "0.4.1-next.0",
   "description": "Easy hot module reloading (HMR) for Node.js and ESM",
   "author": "Julien Ripouteau <[email protected]>",
   "license": "MIT",