React Renderer: refactor the code, clean it up and make it more generic

src/main/docs/guide/views/templates/react/reactsettingproperties.adoc

@@ -27,7 +27,7 @@ IMPORTANT: Watch out for the last property that disables virtual threads. If you
 [[react-dev-mode]]
 == Development
 
-During development you want the fastest iteration speed possible. Firstly turn off response caching so hot reload works with `npx webpack --watch`. Micronaut Views React will automatically notice the file changed on disk and reload it.
+During development you want the fastest iteration speed possible. These property changes will help:
 
 [configuration]
 ----
@@ -38,9 +38,15 @@ micronaut:
       responses:
         file:
           cache-seconds: 0
+  io:
+    watch:
+      enabled: true
+      paths: build/resources/main/views
 ----
 
-If using Maven turn off Micronaut's automatic restart features so that changes to the compiled bundle JS don't cause the whole server to reboot:
+The `paths` property is correct if you're using the default JS compilation setup created for you by Micronaut Starter. If your JS bundle is held in a different directory in your project, make sure to set the path appropriately.
+
+Now you can tell your build system to only recompile the needed files. In a Micronaut Starter based project that uses Gradle, just run `./gradlew --continuous processResources`. This will cause new bundles to be created for both client and server whenever your input JS changes. If using Maven turn off Micronaut's automatic restart features so that changes to the compiled bundle JS don't cause the whole server to reboot, and then make sure to re-run the Maven build when necessary:
 
 [xml]
 ----
@@ -61,4 +67,3 @@ If using Maven turn off Micronaut's automatic restart features so that changes t
     </configuration>
 </plugin>
 ----
-

views-react/README.md

@@ -1,17 +1,7 @@
 # React SSR support for Micronaut
 
-## TODO
+This module uses GraalJS to implement server-side rendering for applications using React or similar libraries like Preact.
 
-1. Eliminate all TODOs from the docs.
-2. Make HTTP prefetches run in parallel.
-3. Reduce the need for config:
-   1. Work out what `micronaut.views.folder` is supposed to be when run from Maven. Get rid of the need to specify this.
-   2. Make it configurable and allow the path to the static assets to be configured so it doesn't have to be served from MN itself.
-   3. Get rid of the blocking of the event loop when prefetching. Pending answer from MN team about why IO pool switch isn't implemented.
-4. Write unit tests.
-5. Document what you can and cannot do in GraalJS.
-6. Find a way to use `renderToPipeableStream`?
-7. Replace `__micronaut_prefetch` with Sam's implementation of fetch() for Micronaut?
-8. Document how to do debugging?
-9. Implement / get implemented TextEncoder/TextDecoder
-10. Update the micronaut-spa-app sample.
+To get a project that uses it, try Micronaut Starter and request Views React. That will give you a fully functional
+frontend project with build system integration (NPM and Webpack integrated with Maven and Gradle). You can then easily
+add components and build up your frontend, or connect up an existing frontend codebase.