react-manifest-rails 0.2.32 → 0.2.33

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: cfebc711293e26ed0feb2d97ba630782e2d2de8592d4e0d4b3392c54ecda6f5a
-  data.tar.gz: 4501274e0565b053dbdf110f87a747e631811e8a5b4d9b248e76e28a6b4a54ea
+  metadata.gz: 03532c58c1ba02316a423460c591adf2b8caa7d6366ff89abfc5c344d1e3a8fc
+  data.tar.gz: 3ab9a668ad0196bec652c804535307f788a7b6a9abea8418bb3c206d6f6ddba6
 SHA512:
-  metadata.gz: 358aa7190d5e0f146b1a9fce2065b41890a23bd8b9b6c42855c895905bf8af6567bb6fec372f8b2bd2363cfd7c68b5a5cd7a535fe8632474be60e5bd8d91b5fa
-  data.tar.gz: bb655465c8ce7a9eb63ad3dde98cbb6f354a1d1eaef8efd948a4b11dc0657ef673c943fb2ca8549e0fb672f7c7abec8f9b4c3e312a77c26bdb870ea4807622b5
+  metadata.gz: 6ff77f4444719e08a35032a2b07bc2d6e0621d49a5db73e2b77880bbddd0172f8c3f2aea1b38b3ce40ff7feaad8d59a141fa7edabe0ce8430091f89656904a42
+  data.tar.gz: d683a77dbcb098e2f5b08c74b1b36dac9d53e56587bf6ec7e958b5f0af25701d98fb9f70a305ceeff2ee0e2656bb81112fddf60cb61f33f21029bf6b445b8291

data/CHANGELOG.md

@@ -7,6 +7,11 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.2.33] - 2026-07-01
+
+### Fixed
+- `resolve_bundle_for_component`/`resolve_bundles_for_component(_direct)` (used by the `react_component` view helper) now pick up new controllers and components added while a development server is still running. Their `component_maps` cache is keyed only on config values, not on what's on disk, so once anything primed the cache (any earlier `react_component` call in the process), a controller dir or component added afterward was invisible until the process restarted — `react_component` would silently render with no bundle injected. The file watcher now invalidates this cache on every file change, the same way it already invalidates the scanner's per-file symbol cache.
+
 ## [0.2.32] - 2026-07-01
 
 ### Added

data/lib/react_manifest/version.rb

@@ -1,3 +1,3 @@
 module ReactManifest
-  VERSION = "0.2.32".freeze
+  VERSION = "0.2.33".freeze
 end

data/lib/react_manifest/watcher.rb

@@ -91,6 +91,7 @@ module ReactManifest
         end
 
         (modified + added + removed).each { |f| Scanner.invalidate(f) }
+        ReactManifest.invalidate_component_maps!
         schedule_regeneration(config)
       end
 

data/lib/react_manifest.rb

@@ -35,6 +35,15 @@ module ReactManifest
       Scanner.clear_cache!
     end
 
+    # Drop the cached component-symbol -> bundle map used by
+    # resolve_bundle_for_component / resolve_bundles_for_component(_direct).
+    # Unlike reset!, this does NOT touch the current Configuration — safe to
+    # call whenever ux/ files change (e.g. from the file watcher) so newly
+    # added controllers/components are picked up without losing app config.
+    def invalidate_component_maps!
+      @component_maps_cache = nil
+    end
+
     # Returns the ordered list of bundle logical names for a given controller.
     # Used by the react_bundle_tag view helper.
     def resolve_bundles(ctrl_name)

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: react-manifest-rails
 version: !ruby/object:Gem::Version
-  version: 0.2.32
+  version: 0.2.33
 platform: ruby
 authors:
 - Oliver Noonan