chore: releases

Julien-R44 · Nov 23, 2024 · 6126a5e · 6126a5e
1 parent 413c3ac
commit 6126a5e
Show file tree

Hide file tree

Showing 9 changed files with 42 additions and 34 deletions.
diff --git a/.changeset/blue-taxis-poke.md b/.changeset/blue-taxis-poke.md
diff --git a/.changeset/hot-owls-rhyme.md b/.changeset/hot-owls-rhyme.md
diff --git a/.changeset/spotty-donkeys-doubt.md b/.changeset/spotty-donkeys-doubt.md
diff --git a/packages/dump_viewer/CHANGELOG.md b/packages/dump_viewer/CHANGELOG.md
@@ -1,5 +1,13 @@
 # @hot-hook/dump-viewer
 
+## 0.4.0
+
+### Patch Changes
+
+- Updated dependencies [0ab1205]
+- Updated dependencies [623294e]
+  - [email protected]
+
 ## 0.3.7
 
 ### Patch Changes

diff --git a/packages/dump_viewer/package.json b/packages/dump_viewer/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@hot-hook/dump-viewer",
-  "version": "0.3.7",
+  "version": "0.4.0",
   "type": "module",
   "files": [
     "build"

diff --git a/packages/hot_hook/CHANGELOG.md b/packages/hot_hook/CHANGELOG.md
@@ -1,5 +1,30 @@
 # hot-hook
 
+## 0.4.0
+
+### Minor Changes
+
+- 0ab1205: Earlier, with this release https://github.com/Julien-R44/hot-hook/releases/tag/hot-hook%400.3.0 we were just throwing and thus killing the app when a boundary file was not dynamically imported because it prevented hot-hook from hot-reloading.
+
+  Now, we no longer throw the error by default, we simply emit a message of type "hot-hook:full-reload" to the parent process, which will be responsible for restarting the entire app. This "hot-hook:full-reload" message is not new, it was already used for files that should trigger a full reload.
+
+  If you still want to throw the error, then you can pass the `throwWhenBoundariesAreNotDynamicallyImported` option to true, when you call `hot.init` or in your `package.json`:
+
+  ```json
+  {
+    "hotHook": {
+      "throwWhenBoundariesAreNotDynamicallyImported": true
+    }
+  }
+  ```
+
+### Patch Changes
+
+- 623294e: See https://github.com/tailwindlabs/tailwindcss/discussions/15105
+
+  Sometimes in the resolve hook, we receive a parentUrl that is just `data:`. I didn't really understand
+  why yet, for now we just ignore these cases and that seems to fix the issue with Tailwind V4.
+
 ## 0.3.1
 
 ### Patch Changes

diff --git a/packages/hot_hook/package.json b/packages/hot_hook/package.json
@@ -1,7 +1,7 @@
 {
   "name": "hot-hook",
   "description": "Easy hot module reloading (HMR) for Node.js and ESM",
-  "version": "0.3.1",
+  "version": "0.4.0",
   "main": "index.js",
   "type": "module",
   "files": [

diff --git a/packages/runner/CHANGELOG.md b/packages/runner/CHANGELOG.md
@@ -1,5 +1,11 @@
 # @hot-hook/runner
 
+## 0.1.0
+
+### Minor Changes
+
+- 0ab1205: The runner will now full-reload the application when a file changes and the boundaries are not dynamically imported.
+
 ## 0.0.7
 
 ### Patch Changes

diff --git a/packages/runner/package.json b/packages/runner/package.json
@@ -1,7 +1,7 @@
 {
   "name": "@hot-hook/runner",
   "description": "Runner for applications that use hot-hook",
-  "version": "0.0.7",
+  "version": "0.1.0",
   "main": "build/bin/run.js",
   "type": "module",
   "files": [