react_on_rails 11.0.5 → 13.4.0

data/docs/javascript/troubleshooting-when-using-shakapacker.md

@@ -0,0 +1,77 @@
+# Client rendering crashes when configuring `optimization.runtimeChunk` to `multiple`
+
+## Context
+
+1. Ruby version: 3.1
+2. Rails version: 7.0.6
+3. Shakapacker version: 6.6.0
+4. React on Rails version: 13.3.5
+
+## The failure
+
+Configuring Webpack to embed the runtime in each chunk and calling `react_component` twice in a rails view/partial causes the client render to crash with the following error:
+
+```
+Could not find component registered with name XXX. Registered component names include [ YYY ]. Maybe you forgot to register the component?
+```
+
+```
+VM4859 clientStartup.js:132 Uncaught Error: ReactOnRails encountered an error while rendering component: XXX. See above error message.
+    at Object.get (ComponentRegistry.js:40:15)
+    at Object.getComponent (ReactOnRails.js:211:44)
+    at render (VM4859 clientStartup.js:103:53)
+    at forEachReactOnRailsComponentRender (VM4859 clientStartup.js:138:9)
+    at reactOnRailsPageLoaded (VM4859 clientStartup.js:164:5)
+    at renderInit (VM4859 clientStartup.js:205:9)
+    at onPageReady (VM4859 clientStartup.js:234:9)
+    at HTMLDocument.onReadyStateChange (VM4859 clientStartup.js:238:13)
+```
+
+## Configs
+
+### Webpack configuration
+
+```js
+optimization: {
+  runtimeChunk: 'multiple'
+},
+```
+
+### Rails view
+
+```haml
+= react_component("XXX", props: @props)
+= yield
+= react_component("YYY", props: @props)
+```
+
+## The problem
+
+Configuring Webpack to embed the runtime in each chunk and calling `react_component` twice in a rails view/partial causes the client render to crash.
+
+Read more at https://github.com/shakacode/react_on_rails/issues/1558.
+
+## Solution
+
+To overcome this issue, we could use [shakapacker](https://github.com/shakacode/shakapacker)'s default optimization configuration (pseudo-code):
+
+```js
+const { webpackConfig: baseClientWebpackConfig } = require('shakapacker');
+
+// ...
+
+config.optimization = baseClientWebpackConfig.optimization;
+```
+As it set the `optimization.runtimeChunk` to `single`. See its source:
+
+`package/environments/base.js:115`
+```js
+  optimization: {
+    splitChunks: { chunks: 'all' },
+
+    runtimeChunk: 'single'
+  },
+```
+https://github.com/shakacode/shakapacker/blob/cdf32835d3e0949952b8b4b53063807f714f9b24/package/environments/base.js#L115-L119
+
+Or set `optimization.runtimeChunk` to `single` directly.

data/docs/{additional-reading → javascript}/webpack.md

@@ -18,5 +18,5 @@ Webpack v2 makes this very convenient! See:
 * [Implicit Common Vendor Chunk](https://webpack.js.org/guides/code-splitting-libraries/#implicit-common-vendor-chunk)
 * [Manifest File](https://webpack.js.org/guides/code-splitting-libraries/#manifest-file)
 
-
-
+## Webpack v4
+Webpack v4 is heartily recommended. If you need help with migrating your project to Webpack v4, please contact me, [justin@shakacode.com](mailto:justin@shakacode.com).

data/docs/misc/articles.md

@@ -0,0 +1,20 @@
+# Articles, Videos, and Podcasts
+
+## Articles
+
+* [Introducing React on Rails v9 with Webpacker Support](https://blog.shakacode.com/introducing-react-on-rails-v9-with-webpacker-support-f2584c6c8fa4) for an overview of the integration of React on Rails with Webpacker.
+* [Webpacker Lite: Why Fork Webpacker?](https://blog.shakacode.com/webpacker-lite-why-fork-webpacker-f0a7707fac92)
+* [React on Rails, 2000+ 🌟 Stars](https://medium.com/shakacode/react-on-rails-2000-stars-32ff5cfacfbf#.6gmfb2gpy)
+* [The React on Rails Doctrine](https://medium.com/@railsonmaui/the-react-on-rails-doctrine-3c59a778c724)
+* [Simple Tutorial](https://www.shakacode.com/react-on-rails/docs/guides/tutorial/).
+
+## Videos
+
+*  [Video of running the v9 installer with Webpacker v3](https://youtu.be/M0WUM_XPaII). History, motivations, philosophy, and overview.
+1. [GORUCO 2017: Front-End Sadness to Happiness: The React on Rails Story by Justin Gordon](https://www.youtube.com/watch?v=SGkTvKRPYrk)
+2. [egghead.io: Creating a component with React on Rails](https://egghead.io/lessons/react-creating-a-component-with-react-on-rails)
+3. [egghead.io: Creating a redux component with React on Rails](https://egghead.io/lessons/react-add-redux-state-management-to-a-react-on-rails-project)
+4. [React On Rails Tutorial Series](https://www.youtube.com/playlist?list=PL5VAKH-U1M6dj84BApfUtvBjvF-0-JfEU)
+  1. [History and Motivation](https://youtu.be/F4oymbUHvoY)
+  2. [Basic Tutorial Walkthrough](https://youtu.be/_bjScw60FBk)
+  3. [Code Walkthrough](https://youtu.be/McQ9UM-_ocQ)

data/docs/misc/doctrine.md

@@ -4,7 +4,7 @@ By Justin Gordon, January 26, 2016
 
 This document is an extension and complement to [The Rails Doctrine](http://rubyonrails.org/doctrine/). If you haven't read that document, I suggest you do so first.
 
-As stated in the [React on Rails README](../../README.md), the project objective is to provide an opinionated and optimal framework for integrating **Ruby on Rails** with modern JavaScript tooling and libraries. When considering what goes into **react_on_rails**, we ask ourselves, is the functionality related to the intersection of using Rails and with modern JavaScript? A good example is view helper integration of React components on a Rails view. If the answer is yes, then the functionality belongs right here. In other cases, we're releasing separate npm packages or Ruby gems. For example, we needed an easy way to integrate [Twitter Bootstrap](http://getbootstrap.com/) with Webpack, and we released the [npm bootstrap-loader](https://github.com/shakacode/bootstrap-loader/). 
+As stated in the [React on Rails README](https://www.shakacode.com/react-on-rails/docs/), the project objective is to provide an opinionated and optimal framework for integrating **Ruby on Rails** with modern JavaScript tooling and libraries. When considering what goes into **react_on_rails**, we ask ourselves, is the functionality related to the intersection of using Rails and with modern JavaScript? A good example is view helper integration of React components on a Rails view. If the answer is yes, then the functionality belongs right here. In other cases, we're releasing separate npm packages or Ruby gems. For example, we needed an easy way to integrate [Twitter Bootstrap](http://getbootstrap.com/) with Webpack, and we released the [npm bootstrap-loader](https://github.com/shakacode/bootstrap-loader/).
 
 Besides the project objective, let's stick with the "Rails Doctrine" and keep the following in mind.
 
@@ -19,15 +19,14 @@ The React on Rails setup provides several key components related to front-end de
 6. Happiness for us is actively participating in open source, so we want to be where the action is, which is with the npm libraries on github.com.
 7. You can get set up on React on Rails **FAST** using our application generator.
 8. By placing all client-side development inside of the `/client` directory, pure JavaScript developers can productively do development separate from Rails. Instead of Rails APIs, stub APIs on an express server can provide a simple backend, allowing for rapid iteration of UI prototypes.
-9. Just because we're not relying on the Rails asset pipeline for ES6 conversion does not mean that we're deploying Rails apps in any different way. We still use the asset pipeline to include our Webpack compiled JavaScript. This only requires a few small modifications, as explained in our doc [Heroku Deployment](../additional-reading/heroku-deployment.md).
+9. Just because we're not relying on the Rails asset pipeline for ES6 conversion does not mean that we're deploying Rails apps in any different way. We still use the asset pipeline to include our Webpack compiled JavaScript. This only requires a few small modifications, as explained in [our heroku deployment documentation](https://www.shakacode.com/react-on-rails/docs/deployment/heroku-deployment/).
 
 ## Convention over Configuration
 * React on Rails has taken the hard work out of figuring out the JavaScript tooling that works best with Rails. Not only could you spend lots of time researching different tooling, but then you'd have to figure out how to splice it all together. This is where a lot of "JavaScript fatigue" comes from. The following keep the code clean and consistent:
-* [Style Guide](../coding-style/style.md)
-* [linters](../contributor-info/linters.md)
-* [Recommended Project Structure](../additional-reading/recommended-project-structure.md)
+* [Style Guide](https://www.shakacode.com/react-on-rails/docs/misc/style/)
+* [linters](https://www.shakacode.com/react-on-rails/docs/contributor-info/linters/)
 
-We're big believers in this quote from the Rails Doctrine: 
+We're big believers in this quote from the Rails Doctrine:
 
 > The same goes even when you understand how all the pieces go together. When there’s an obvious next step for every change, we can scoot through the many parts of an application that is the same or very similar to all the other applications that went before it. A place for everything and everything in its place. Constraints liberate even the most able minds.
 

data/docs/outdated/deferred-rendering.md

@@ -0,0 +1,39 @@
+# Deferred Rendering
+
+Please see [React on Rails Pro](https://www.shakacode.com/react-on-rails-pro/] if you are interested in code splitting using
+[loadable-components.com](https://loadable-components.com/docs) with React on Rails.
+
+-----
+
+What is code splitting? From the webpack documentation:
+
+> For big web apps it’s not efficient to put all code into a single file, especially if some blocks of code are only required under some circumstances. Webpack has a feature to split your codebase into “chunks” which are loaded on demand. Some other bundlers call them “layers”, “rollups”, or “fragments”. This feature is called “code splitting”.
+
+## Server Rendering and Code Splitting
+
+Let's say you're requesting a page that needs to fetch a code chunk from the server before it's able to render. If you do all your rendering on the client side, you don't have to do anything special. However, if the page is rendered on the server, you'll find that React will spit out the following error:
+
+> Warning: React attempted to reuse markup in a container but the checksum was invalid. This generally means that you are using server rendering and the markup generated on the server was not what the client was expecting. React injected new markup to compensate which works but you have lost many of the benefits of server rendering. Instead, figure out why the markup being generated is different on the client or server:
+
+> (client) <!-- react-empty: 1 -
+
+> (server) <div data-reactroot="
+<!--This comment is here because the comment beginning on line 13 messes up Sublime's markdown parsing-->
+
+Different markup is generated on the client than on the server. Why does this happen? When you register a component or Render-Function with `ReactOnRails.register`, React on Rails will by default render the component as soon as the page loads. However, code splitting requires that components render at a later time when the JavaScript chunks have loaded.
+
+## Solution
+
+To prevent this, you have to wait until the code chunk is fetched before doing the initial render on the client side. To accomplish this, react on rails allows you to register a renderer. This works just like registering a Render-Function, except that the function you pass takes three arguments: `renderer(props, railsContext, domNodeId)`, and is responsible for calling `ReactDOM.render` or `ReactDOM.hydrate` to render the component to the DOM. React on rails will automatically detect when a Render-Function takes three arguments, and will **not** call `ReactDOM.render` or `ReactDOM.hydrate`, instead allowing you to control the initial render yourself. Note, you have to be careful to call `ReactDOM.hydrate` rather than `ReactDOM.render` if you are are server rendering.
+
+
+## Server vs. Client Code Caveats
+
+If you're going to try to do code splitting with server rendered routes, you'll probably need to use seperate route definitions for client and server to prevent code splitting from happening for the server bundle. The server bundle should be one file containing all the JavaScript code. This will require you to have seperate webpack configurations for client and server.
+
+Do not attempt to register a renderer function on the server. Instead, register either a Render-Function or a component. If you register a renderer in the server bundle, you'll get an error when react on rails tries to server render the component.
+
+
+## React on Rails Pro
+[React on Rails Pro](https://www.shakacode.com/react-on-rails-pro/] includes a complete setup using this technique for code splitting using
+[loadable-components.com](https://loadable-components.com/docs) with React on Rails.

data/docs/{additional-reading → outdated}/rails-assets-relative-paths.md

@@ -1,4 +1,4 @@
-*Note: this doc needs updating to reflect how v8.x+ no longer puts Webpack generated files through the asset pipeline. PR's welcome!*
+*Note: this doc reflects using Sprockets for assets and has not been updated for Shakapacker or rails/webpacker*
 
 # Using Webpack bundled assets with the Rails Asset Pipeline
 
@@ -77,7 +77,7 @@ Note: _You can output these files in the asset pipeline wherever you see fit. My
 
 Lastly, we will set the publicPath to our file(s). This will be the endpoint on our rails web server that you can visit to reach the asset (if you don't know how this works, read the [intro](#using-webpack-bundled-assets-with-the-rails-asset-pipeline)). If you've been following the previous steps, you know that we set our outputPath for our assets to be absolute at `app/assets/webpack/webpack-assets/`, which your rails app should end up hosting at `/assets/webpack-assets/file-name+hash.ext` when the server is run.
 
-Note: _If you're having a hard time figuring out what an asset's path will be on your rails server, simply run `rake assets:precompile` and `cd public/`. The path from there to your file will then be the path/url on your web server to that asset. On top of this, it is also a good idea to check out [this doc](./rails-assets.md) to understand how `react_on_rails` allows us to access these files after precompilation, when Rails applies another hash onto the asset._
+Note: _If you're having a hard time figuring out what an asset's path will be on your rails server, simply run `rake assets:precompile` and `cd public/`. The path from there to your file will then be the path/url on your web server to that asset. On top of this, it is also a good idea to check out [this doc](https://www.shakacode.com/react-on-rails/docs/outdated/rails-assets/) to understand how `react_on_rails` allows us to access these files after precompilation, when Rails applies another hash onto the asset._
 
 Our publicPath setting will match the path to our outputted assets on our rails web server. Given our assets in this example will be outputted to `/app/assets/webpack/webpack-assets/` and hosted at `/assets/webpack-assets/`, our publicPath would be:
 
@@ -179,7 +179,7 @@ module.exports = {
         // The important stuff
         test: /\.(jpg|jpeg|png)(\?.*)?$/, // Load only .jpg .jpeg, and .png files
         use: {
-          loader: 'file-loader', 
+          loader: 'file-loader',
           options: {
             name: '[name][md5:hash].[ext]', // Name of bundled asset
             outputPath: 'webpack-assets/', // Output location for assets. Final: `app/assets/webpack/webpack-assets/`
@@ -192,4 +192,4 @@ module.exports = {
 };
 ```
 
-If you'd like to understand how react_on_rails handles these bundled assets after asset precompilation and in production mode, check out: [Rails Assets](./rails-assets.md).
+If you'd like to understand how react_on_rails handles these bundled assets after asset precompilation and in production mode, check out: [Rails Assets](https://www.shakacode.com/react-on-rails/docs/outdated/rails-assets/).

data/docs/{additional-reading → outdated}/rails-assets.md

@@ -1,5 +1,7 @@
 # Rails assets and the Extract Text Plugin
 
+*This doc needs updating for the use of  Shakapacker or rails/webpacker with React on Rails*
+
 The [Webpack file loader](https://github.com/webpack/file-loader) copies referenced files to
 the destination output directory, with an MD5 hash. The other term for this is a "digest".
 
@@ -11,41 +13,31 @@ CSS and fonts for CSS. However, this applies to any file that might be processed
 Webpack file loader.
 
 ## The Problem
-To understand the problem, it helps to read this article: 
+To understand the problem, it helps to read this article:
 [What is fingerprinting and why should I care](http://guides.rubyonrails.org/asset_pipeline.html#what-is-fingerprinting-and-why-should-i-care-questionmark)
 Basically, when Rails prepares assets for production deployments, it also adds a digest
-to the file names. E.g., `img1.jpg` becomes `img1-dbu097452jf2v2.jpg`. 
+to the file names. E.g., `img1.jpg` becomes `img1-dbu097452jf2v2.jpg`.
 
-When compiling its native css Rails transforms all urls and links to digested 
-versions, i.e. `background-image: image-url(img1.jpg)` becomes 
-`background-image: url(img1-dbu097452jf2v2.jpg)`. However this doesn't happen for js and 
-css files compiled by webpack on the client side, because they don't use 
+When compiling its native css Rails transforms all urls and links to digested
+versions, i.e. `background-image: image-url(img1.jpg)` becomes
+`background-image: url(img1-dbu097452jf2v2.jpg)`. However this doesn't happen for js and
+css files compiled by webpack on the client side, because they don't use
 `image-url` and `asset-url`. Without some fix, these assets would fail to load.
 
-When Webpack's client JavaScript uses images in render methods, e.g. `<img src='...' />` or 
+When Webpack's client JavaScript uses images in render methods, e.g. `<img src='...' />` or
 in css, e.g. `background-image: url(...)` The code (such as the CSS) generated by the Webpack
 will have the Webpack digested name (MD5 hash). Since the Webpack generated CSS expects
 just one level of "digesting", this "double-digesting" from Rails will cause such these assets
 fail to load.
 
-_If you are interested in learning how to use assets in your React components, read this doc: [Webpack, the Asset Pipeline, and Using Assets w/ React](./rails-assets-relative-paths.md)._
+_If you are interested in learning how to use assets in your React components, read this doc: [Webpack, the Asset Pipeline, and Using Assets w/ React](https://www.shakacode.com/react-on-rails/docs/outdated/rails-assets-relative-paths/)_
 
 ## The Solution: Symlink Original File Names to New File Names
-React on Rails creates symlinks of non-digested versions (original webpack digested file names) 
-to the Rails deployed digested versions when doing a Rails assets compile. The solution is 
-implemented using `assets:precompile` after-hook in 
-file [lib/tasks/assets.rake](../../lib/tasks/assets.rake)
-The assets for symlinking are defined by `config.symlink_non_digested_assets_regex` in 
-`config/initializers/react_on_rails.rb`.
-
-## Disabling the Symlinking
-To disable symlinks set this parameter to `nil`.
-
+_Note, this solution was removed in v14. If you're intersted in this symlink solution, please create
+a github issue._
 
 ## Example from /spec/dummy
 
-If you run
-
 ```
 cd spec/dummy
 RAILS_ENV=production bundle exec rake assets:precompile

data/docs/{misc → outdated}/rails3.md

@@ -1,9 +1,9 @@
 # Rails 3
 
-* Please let us know if you find any issues with Rails 3. 
+* Please let us know if you find any issues with Rails 3.
 * Rails 3 is confirmed to work up with versions up to 6.8.x.
 * We are not testing it for new releases. If you find an issue, you will have to submit a PR to get it fixed.
 
 ## Known Issues
 
-1. If you do not skip bootstrap for the generator, you cannot generate a working app, as bootstrap-sass does not not support Rails 3, or at least the version we're using.
+1. If you do not skip bootstrap for the generator, you cannot generate a working app, as bootstrap-sass does not support Rails 3, or at least the version we're using.

data/docs/rails/convert-rails-5-api-only-app.md

@@ -0,0 +1,19 @@
+# Convert Rails 5 API only app to a Rails app
+
+1. Go to the directory where you created your app
+
+```bash
+$ rails new your-current-app-name
+```
+
+Rails will start creating the app and will skip the files you have already created. If there is some conflict then it will stop and you need to resolve it manually. be careful at this step as it might replace you current code in conflicted files.
+
+2. Resolve conflicts
+
+```
+1. Press "d" to see the difference
+2. If it is only adding lines then press "y" to continue
+3. If it is removeing some of your code then press "n" and add all additions manually
+```
+
+3. Run `bundle install` and follow [the instructions for installing into an existing Rails app](https://www.shakacode.com/react-on-rails/docs/guides/installation-into-an-existing-rails-app/)

data/docs/rails/rails-engine-integration.md

@@ -0,0 +1,32 @@
+## In your engine
+
++ At the top of `config/initializers/react_on_rails.rb`
+```ruby
+ActiveSupport.on_load(:action_view) do
+  include ReactOnRailsHelper
+end
+```
++ In your `<engine_name>.gemspec`:
+```ruby
+s.add_dependency 'react_on_rails', '~> 6'
+```
++ In your `lib/<engine_name>.rb` (the entry point for your engine)
+```ruby
+require "react_on_rails"
+```
+## In the project including your engine
+
+Place `gem 'react_on_rails', '~> 6'` before the gem pointing at your engine in your gemfile.
+
+Requiring `react_on_rails` and including the helper will get rid of any issues where react on rails or react_component is undefined.
+
+As far as solving the assets issue, `lib/tasks/assets.rake` in `react_on_rails` would somehow have to know that `react_on_rails` was included in an engine, and decide the path accordingly. This might be impossible, especially in the case of multiple engines using `react_on_rails` in a single application.
+
+Another solution would be to detach this rake task from the `rails assets:precompile` task. This can be done by adding `REACT_ON_RAILS_PRECOMPILE=false` to your environment. If you do so, then react assets will have to be bundled separately from `rails assets:precompile`.
+
+# Github Issues
+
+* [Integration with an engine #342](https://github.com/shakacode/react_on_rails/issues/342)
+* [Feature: target destination option for the install generator #459](https://github.com/shakacode/react_on_rails/issues/459)
+* [Integration with Rails 5 Engines #562](https://github.com/shakacode/react_on_rails/issues/562)
+* [Run inside a Rails engine? #257](https://github.com/shakacode/react_on_rails/issues/257)

data/docs/{additional-reading → rails}/rails_view_rendering_from_inline_javascript.md

@@ -12,9 +12,10 @@ You can easily render React components in your JavaScript with `render` method t
  * @param name Name of your registered component
  * @param props Props to pass to your component
  * @param domNodeId
+ * @param hydrate [optional] Pass truthy to update server rendered html. Default is falsy
  * @returns {virtualDomElement} Reference to your component's backing instance
  */
-ReactOnRails.render(componentName, props, elementId)
+ReactOnRails.render(componentName, props, domNodeId)
 ```
 
 ## Why do we need this?

data/docs/{additional-reading → rails}/turbolinks.md

@@ -1,4 +1,15 @@
-# Turbolinks
+# Turbolinks and Turbo
+
+## Updated to support Turbo
+* See [PR 1374](https://github.com/shakacode/react_on_rails/pull/1374).
+* Ability to use with Turbo (@hotwired/turbo), as Turbolinks gets obsolete.
+
+To configure turbo the following option can be set:
+  `ReactOnRails.setOptions({ turbo: true })`
+
+Turbo is not auto-detected like older Turbolinks.
+
+*Below docs maybe outdated*
 
 * See [Turbolinks on Github](https://github.com/rails/turbolinks)
 * React on Rails currently supports 2.5.x of Turbolinks and 5.0.0 of Turbolinks 5.
@@ -73,6 +84,7 @@ To turn on tracing of Turbolinks events, put this in your registration file, whe
 ```js
    ReactOnRails.setOptions({
      traceTurbolinks: true,
+     turbo: true,
    });
 ```
 

data/docs/react-on-rails-pro/react-on-rails-pro.md

@@ -0,0 +1,43 @@
+## React on Rails Pro
+
+Support React on Rails development [by becoming a Github sponsor](https://github.com/sponsors/shakacode) and get these benefits:
+
+1. 1-hour per month of support via Slack, PR reviews, and Zoom for React on Rails,
+   React-Rails, Shakapacker, rails/webpacker, ReScript (ReasonML), TypeScript, Rust, etc.
+2. React on Rails Pro Software that extends React on Rails with Node server rendering,
+   fragment caching, code-splitting, and other performance enhancements for React on Rails.
+
+See the [React on Rails Pro Support Plan](https://www.shakacode.com/react-on-rails-pro/).
+
+ShakaCode can also help you with your custom software development needs. We specialize in
+marketplace and e-commerce applications that utilize both Rails and React.
+Because we own [HiChee.com](https://hichee.com), we can leverage that code for your app!
+
+Please email Justin Gordon [justin@shakacode.com](mailto:justin@shakacode.com), the
+maintainer of React on Rails, for more information.
+
+### Pro: Fragment Caching
+
+Fragment caching is a [React on Rails Pro](https://www.shakacode.com/react-on-rails-pro/) feature. Fragment caching is a **HUGE** performance booster for your apps. Use the `cached_react_component` and `cached_react_component_hash`. The API is the same as `react_component` and `react_component_hash`, but for 2 differences:
+
+1. The `cache_key` takes the same parameters as any Rails `cache` view helper.
+1. The **props** are passed via a block so that evaluation of the props is not done unless the cache is broken. Suppose you put your props calculation into some method called `some_slow_method_that_returns_props`:
+
+```ruby
+<%= cached_react_component("App", cache_key: [@user, @post], prerender: true) do
+  some_slow_method_that_returns_props
+end %>
+```
+
+Such fragment caching saves CPU work for your web server and greatly reduces the request time. It completely skips the evaluation costs of:
+
+1. Database calls to compute the props.
+2. Serialization the props values hash into a JSON string for evaluating JavaScript to server render.
+3. Costs associated with evaluating JavaScript from your Ruby code.
+4. Creating the HTML string containing the props and the server-rendered JavaScript code.
+
+Note, even without server rendering (without step 3 above), fragment caching is still effective.
+
+### Pro: Integration with Node.js for Server Rendering
+
+Default server rendering is done by ExecJS. If you want to use a Node.js server for better performing server rendering, [email justin@shakacode.com](mailto:justin@shakacode.com). ShakaCode has built a premium Node rendering server that is part of [React on Rails Pro](https://www.shakacode.com/react-on-rails-pro).

data/docs/testimonials/hvmn.md

@@ -0,0 +1,25 @@
+# HVMN Testimonial, Written by Paul Benigeri, October 12, 2018
+
+For some years, we used React on Rails for server-side rendering at [HVMN](https://hvmn.com). Our entire backend was already built in Rails, and we love React. As a content & e-commerce site, server-side rendering is critical, for UX performance and SEO crawler indexing.
+
+During the 12 months leading up to our React on Rails Pro transition, our traffic grew 10x. Our team of 2 engineers was focused on shipping features, and we started to face performance issues. We had some fragment caching of our React server rending, but it didn’t work that well.
+
+I discussed our growing pains with Justin, and as it turned out, ShakaCode just came out with React on Rails Pro and set it up on [egghead.io](https://egghead.io). The performance improvements were impressive, and Justin’s team was an ideal partner to help with the integration.
+
+We decided to give it a shot. Over three weeks, the ShakaCode team helped us migrate to React on Rails Pro, set up Webpack v4, migrated our entire asset pipeline to Webpack v4.
+
+Results were great. Our blog and product pages are 80-90% faster after that effort. The improved fragment caching was quick to set up and made a huge dent in our average server response times. We also observed an additional drop in response times when ShakaCode shipped the standalone Node server-side React renderer.
+
+Working with ShakaCode was a pleasure. Justin is one of the smartest Rails architects I know, and his team was responsive and productive.
+
+The price we paid for the consultation + the React on Rails pro license has already been made back a couple of times from hosting fees alone. The entire process was super hands off, and our core team was able to focus on shipping new feature during that sprint.
+
+If you have any questions, please reach out.
+
+Paul Benigeri, Head of E-Commerce
+
+[paul@hvmn.com](mailto:paul@hvmn.com), [LinkedIn](https://www.linkedin.com/in/benigeri/)
+
+Related Article: [HVMN’s 90% Reduction in Server Response Time from React on Rails Pro](https://blog.shakacode.com/hvmns-90-reduction-in-server-response-time-from-react-on-rails-pro-eb08226687db)
+
+[![image](https://user-images.githubusercontent.com/1118459/46911126-577abd00-ceee-11e8-86c6-6703ff80fc2f.png)](https://www.linkedin.com/in/benigeri/)

data/docs/testimonials/resortpass.md

@@ -0,0 +1,13 @@
+# ResortPass Testimonial, by Leora Juster, December 10, 2018
+
+Many can write code that "works." Even fewer can write sophisticated code that both works and reflects a deep understanding of the technologies and paradigms involved. Only a select few can do the aforementioned while assisting in managing the expectations and time constraints of less technically informed members of software product teams to make the best design decisions possible. Justin and his team were instrumental in assisting us in setting design foundations and standards for our transition to a react on rails application. Just three months of work with the team at Shaka code and we have a main page of our application server-side rendering at exponentially improved speeds. The code and CSS files are well-organized and contain repeatable patterns easy to understand, allowing my team to build on what has already been accomplished. I learned a great deal from my interactions with Justin and his team, as they are just as great teachers as they are developers, and feel like I get to continually learn from them as I build on top of their code. Their different support and pro plan options make it easy to build a continuous professional relationship despite fluctuations in my team's funding, and their team is always extremely personable, punctual, and professional. 
+
+Leora Juster, Full-Stack Lead Software Developer
+
+[LinkedIn](https://www.linkedin.com/in/leora-juster-38933050)
+
+![image](https://user-images.githubusercontent.com/1118459/50050877-30399b00-00ab-11e9-9e52-2977de45ccae.png)
+
+[ResortPass](https://resortpass.com/)
+
+[![2018-12-15_20-48-35](https://user-images.githubusercontent.com/1118459/50050866-03858380-00ab-11e9-8588-461112f8045b.png)](https://resortpass.com/)

data/docs/testimonials/testimonials.md

@@ -0,0 +1,28 @@
+# Testimonials
+# [HVMN Testimonial, Written by Paul Benigeri, October 12, 2018](https://www.shakacode.com/react-on-rails/docs/testimonials/hvmn/)
+
+> The price we paid for the consultation + the React on Rails pro license has already been made back a couple of times from hosting fees alone. The entire process was super hands off, and our core team was able to focus on shipping new feature during that sprint.
+
+Full writeup [here](https://www.shakacode.com/react-on-rails/docs/testimonials/hvmn/).
+
+---
+
+# [Leora from ResortPass](https://www.shakacode.com/react-on-rails/docs/testimonials/resortpass/), December 10, 2018
+
+Justin and his team were instrumental in assisting us in setting design foundations and standards for our transition to a react on rails application. Just three months of work with the team at Shaka code and we have a main page of our application server-side rendering at exponentially improved speeds.
+
+Full writeup [here](https://www.shakacode.com/react-on-rails/docs/testimonials/resortpass/).
+
+---
+
+From Joel Hooks, Co-Founder, Chief Nerd at [egghead.io](https://egghead.io/), January 30, 2017:
+
+![2017-01-30_11-33-59](https://cloud.githubusercontent.com/assets/1118459/22443635/b3549fb4-e6e3-11e6-8ea2-6f589dc93ed3.png)
+
+---
+
+From Kyle Maune of Cooper Aerial, May 4, 2018
+
+![image](https://user-images.githubusercontent.com/1118459/40891236-9b0b406e-671d-11e8-80ee-c026dbd1d5a2.png)
+
+For more testimonials, see [Live Projects](https://github.com/shakacode/react_on_rails/tree/master/PROJECTS.md) and [Kudos](https://github.com/shakacode/react_on_rails/tree/master/KUDOS.md).

data/jest.config.js

@@ -0,0 +1,4 @@
+module.exports = {
+  preset: 'ts-jest/presets/js-with-ts',
+  testEnvironment: 'jsdom',
+};

data/lib/generators/USAGE

@@ -21,4 +21,4 @@ Then you may run
 
 More Details:
 
-    `https://github.com/shakacode/react_on_rails/blob/master/docs/basics/generator.md`
+    `https://github.com/shakacode/react_on_rails/blob/master/docs/basics/generator-details.md`

data/lib/generators/react_on_rails/adapt_for_older_shakapacker_generator.rb

@@ -0,0 +1,41 @@
+# frozen_string_literal: true
+
+require "rails/generators"
+require_relative "generator_helper"
+
+module ReactOnRails
+  module Generators
+    class AdaptForOlderShakapackerGenerator < Rails::Generators::Base
+      include GeneratorHelper
+      Rails::Generators.hide_namespace(namespace)
+
+      def change_spelling_to_webpacker
+        puts "Change spelling to webpacker v7"
+        files = %w[
+          Procfile.dev
+          Procfile.dev-static
+          config/shakapacker.yml
+          config/initializers/react_on_rails.rb
+        ]
+        files.each { |file| gsub_file(file, "shakapacker", "webpacker") }
+      end
+
+      def rename_config_file
+        puts "Rename to config/webpacker.yml"
+        puts "Renaming shakapacker.yml into webpacker.yml"
+        FileUtils.mv("config/shakapacker.yml", "config/webpacker.yml")
+      end
+
+      def modify_requiring_webpack_config_in_js
+        puts "Update commonWebpackConfig.js to follow the Shakapacker v6 interface"
+        file = "config/webpack/commonWebpackConfig.js"
+        gsub_file(file, "const baseClientWebpackConfig = generateWebpackConfig();\n\n", "")
+        gsub_file(
+          file,
+          "const { generateWebpackConfig, merge } = require('shakapacker');",
+          "const { webpackConfig: baseClientWebpackConfig, merge } = require('shakapacker');"
+        )
+      end
+    end
+  end
+end