react_on_rails 8.0.2 → 9.0.0

data/docs/additional-reading/asset-pipeline.md

@@ -0,0 +1,20 @@
+# Asset Pipeline
+
+The plumbing of webpack produced assets through the asset pipeline is deprecated as of v9.0.
+
+The information in this document is here for those that have not yet upgraded.
+
+
+
+
+This option still works for your `/config/initializers/react_on_rails.rb` if you are still using the
+asset pipeline.
+```
+  ################################################################################
+  # MISCELLANEOUS OPTIONS
+  ################################################################################
+  # If you want to use webpack for CSS and images, and still use the asset pipeline,
+  # see https://github.com/shakacode/react_on_rails/blob/master/docs/additional-reading/rails-assets.md
+  # And you will use a setting like this.
+  config.symlink_non_digested_assets_regex = /\.(png|jpg|jpeg|gif|tiff|woff|ttf|eot|svg|map)/
+```

data/docs/additional-reading/hot-reloading-rails-development.md

@@ -1,5 +1,9 @@
 # Hot Reloading of Assets For Rails Development
 
+_Note, this document is not yet updated for React on Rails v8+. See [PR #865](https://github.com/shakacode/react_on_rails/pull/865) for a detailed example of doing hot reloading using V8+ with Webpack v2. Any volunteers to update this page? See [#772](https://github.com/shakacode/react_on_rails/issues/772) and [#361](https://github.com/shakacode/react-webpack-rails-tutorial/issues/361)._
+
+------
+
 This document outlines the steps to setup your React On Rails Environment so that you can experience the pleasure of hot reloading of JavaScript and Sass during your Rails development work. See [Issue 332](https://github.com/shakacode/react_on_rails/issues/332) for troubleshooting. There are 3 examples of this setup:
 
 1. [minimal demo here](https://github.com/retroalgic/react-on-rails-hot-minimal): The most simple and updated hot reloading setup.
@@ -16,8 +20,6 @@ We'll use a Webpack Dev server on port 3500 to provide the assets to Rails, rath
 
 `Procfile.static` provides an alternative that uses "static" assets, similar to a production deployment.
 
-The secret sauce is in the [app/views/layouts/application.html.erb](https://github.com/shakacode/react_on_rails/tree/master/spec/dummy/app/views/layouts/application.html.erb) where it uses view helps to configure the correct assets to load, being either the "hot" assets or the "static" assets.
-
 ## Places to Configure (Files to Examine)
 
 1. See the Webpack config files. Note, these examples are now setup for using [CSS Modules](https://github.com/css-modules/css-modules).
@@ -40,76 +42,3 @@ The secret sauce is in the [app/views/layouts/application.html.erb](https://gith
 ## Code Snippets
 Please refer to the examples linked above in `spec/dummy` as these code samples might be out of date.
 
-
-### config/initializers/assets.rb
-
-```ruby
-# Add folder with webpack generated assets to assets.paths
-Rails.application.config.assets.paths << Rails.root.join("app", "assets", "webpack")
-
-# Precompile additional assets.
-# application.js, application.css, and all non-JS/CSS in app/assets folder are already added.
-Rails.application.config.assets.precompile << "server-bundle.js"
-
-type = ENV["REACT_ON_RAILS_ENV"] == "HOT" ? "non_webpack" : "static"
-Rails.application.config.assets.precompile +=
-  [
-    "application_#{type}.js",
-    "application_#{type}.css"
-  ]
-```
-
-### app/views/layouts/application.html.erb
-
-```erb
-<head>
-  <title>Dummy</title>
-
-  <!-- These do use turbolinks 5 -->
-  <%= env_stylesheet_link_tag(static: 'application_static',
-                              hot: 'application_non_webpack',
-                              media: 'all',
-                              'data-turbolinks-track' => "reload") %>
-
-  <!-- These do not use turbolinks, so no data-turbolinks-track -->
-  <!-- This is to load the hot assets. -->
-  <%= env_javascript_include_tag(hot: ['http://localhost:3500/vendor-bundle.js',
-                                       'http://localhost:3500/app-bundle.js']) %>
-
-  <!-- These do use turbolinks 5 -->
-  <%= env_javascript_include_tag(static: 'application_static',
-                                 hot: 'application_non_webpack',
-                                 'data-turbolinks-track' => "reload") %>
-
-  <%= csrf_meta_tags %>
-</head>
-```
-
-### Procfile.static
-```
-  # Run Rails without hot reloading (static assets).
-  rails: REACT_ON_RAILS_ENV= rails s -b 0.0.0.0
-  
-  # Build client assets, watching for changes.
-  rails-client-assets: yarn run build:dev:client
-  
-  # Build server assets, watching for changes. Remove if not server rendering.
-  rails-server-assets: yarn run build:dev:server
-```
-
-### Procfile.hot
-
-```
-# Procfile for development with hot reloading of JavaScript and CSS 
-
-# Development rails requires both rails and rails-assets
-# (and rails-server-assets if server rendering)
-rails: REACT_ON_RAILS_ENV=HOT rails s -b 0.0.0.0
-
-# Run the hot reload server for client development
-hot-assets: HOT_RAILS_PORT=3500 yarn run hot-assets
-
-# Keep the JS fresh for server rendering. Remove if not server rendering
-rails-server-assets: yarn run build:dev:server
-```
-

data/docs/additional-reading/node-server-rendering.md

@@ -1,169 +1,5 @@
 # Node.js for Server Rendering
 
-Node.js can be used as the backend for server-side rendering instead of [execJS](https://github.com/rails/execjs). Before you try this, consider the tradeoff of extra complexity with your deployments versus *potential* performance gains. We've found that using ExecJS with [mini_racer](https://github.com/discourse/mini_racer) to be "fast enough" so far. That being said, we've heard of other large websites using Node.js for better server rendering performance.
+Node.js can be used as the backend for server-side rendering instead of [execJS](https://github.com/rails/execjs). Before you try this, consider the tradeoff of extra complexity with your deployments versus *potential* performance gains. While often ExecJS with [mini_racer](https://github.com/discourse/mini_racer) is "fast enough", we've heard of other large websites using Node.js for better server rendering performance.
 
-If you're serious about this comparing Node.js versus execJS/mini_racer, then [get in touch](mailto:justin@shakacode.com)! We can definitely collaborate with you on refining this solution. However, please try out these instructions first.
-
-## Setup of React on Rails with Node.js Server Rendering
-**Warning: this is an experimental feature.**
-
-* Every time the webpack bundle changes, you have to restart the server yourself.
-
-To do this you need to add a few files and then configure react_on_rails to use NodeJS. Here are the relevant files to add.
-
-Node server rendering allows you to use separate NodeJS process as a renderer. The process loads your configured server_bundle_js file and then executes javascript to render the component inside its environment. The communication between rails and node occurs
-via a socket (`client/node/node.sock`)
-
-### Getting started
-
-### Configuration
-
-#### Update the React on Rails Initializer
-
-To use node process just set `server_render_method = "NodeJS"` in `config/initializers/react_on_rails.rb`. To change back
-to ExecJS set `server_render_method = "ExecJS"`
-
-```ruby
-# app/config/initializers/react_on_rails.rb
-config.server_render_method = "NodeJS"
-```
-
-You need to configure the name of the server bundle in two places:
-
-1. JavaScript: Change the name of server bundle and adjust yarn start script in `client/node/package.json`
-2. Ruby: The configured server bundle file is defined in `config/react_on_rails.rb`, and you'll have a webpack file that creates this. You maybe using the same file for client rendering.
-
-```ruby
-  # This is the file used for server rendering of React when using `(prerender: true)`
-  # If you are never using server rendering, you may set this to "".
-  # If you are using the same file for client and server rendering, having this set probably does
-  # not affect performance.
-  config.server_bundle_js_file = "webpack-bundle.js"
-```
-
-And in `client/node/package.json`
-
-```javascript
-// client/node/package.json
-{
-    "name": "react_on_rails_node",
-    "version": "0.0.0",
-    "private": true,
-    "scripts": {
-        "start": "node ./server.js -s webpack-bundle.js"
-    },
-    "dependencies": {
-    }
-}
-```
-
-And you'll need this file: `client/node/server.js`
-
-```javascript
-// client/node/server.js
-const net = require('net');
-const fs = require('fs');
-
-const bundlePath = '../../app/assets/webpack/';
-let bundleFileName = 'server-bundle.js';
-
-let currentArg;
-
-class Handler {
-  constructor() {
-    this.queue = [];
-    this.initialized = false;
-  }
-
-  initialize() {
-    console.log(`Processing ${this.queue.length} pending requests`);
-    let callback;
-
-    // eslint-disable-next-line no-cond-assign
-    while (callback = this.queue.pop()) {
-      callback();
-    }
-
-    this.initialized = true;
-  }
-
-  handle(connection) {
-    const callback = () => {
-      const terminator = '\r\n\0';
-      let request = '';
-      connection.setEncoding('utf8');
-      connection.on('data', (data) => {
-        console.log(`Processing chunk: ${data}`);
-        request += data;
-        if (data.slice(-terminator.length) === terminator) {
-          request = request.slice(0, -terminator.length);
-
-          // eslint-disable-next-line no-eval
-          const response = eval(request);
-          connection.write(`${response}${terminator}`);
-          request = '';
-        }
-      });
-    };
-
-    if (this.initialized) {
-      callback();
-    } else {
-      this.queue.push(callback);
-    }
-  }
-}
-
-const handler = new Handler();
-
-process.argv.forEach((val) => {
-  if (val[0] === '-') {
-    currentArg = val.slice(1);
-    return;
-  }
-
-  if (currentArg === 's') {
-    bundleFileName = val;
-  }
-});
-
-function loadBundle() {
-  if (handler.initialized) {
-    console.log('Reloading server bundle must be implemented by restarting the node process!');
-    return;
-  }
-
-  /* eslint-disable */
-  require(bundlePath + bundleFileName);
-  /* eslint-enable */
-  console.log(`Loaded server bundle: ${bundlePath}${bundleFileName}`);
-  handler.initialize();
-}
-
-try {
-  fs.mkdirSync(bundlePath);
-} catch (e) {
-  if (e.code !== 'EEXIST') {
-    throw e;
-  } else {
-    loadBundle();
-  }
-}
-
-fs.watchFile(bundlePath + bundleFileName, (curr) => {
-  if (curr && curr.blocks && curr.blocks > 0) {
-    loadBundle();
-  }
-});
-
-const unixServer = net.createServer((connection) => {
-  handler.handle(connection);
-});
-
-unixServer.listen('node.sock');
-
-process.on('SIGINT', () => {
-  unixServer.close();
-  process.exit();
-});
-```
+If you want to use a node server for server rendering, [get in touch](mailto:justin@shakacode.com). ShakaCode has built a premium Node rendering server for React on Rails.

data/docs/additional-reading/rails-assets-relative-paths.md

@@ -1,3 +1,5 @@
+*Note: this doc needs updating to reflect how v8.x+ no longer puts Webpack generated files through the asset pipeline. PR's welcome!*
+
 # Using Webpack bundled assets with the Rails Asset Pipeline
 
 **If you're looking to use assets in your react components, look no further. This doc is for you.**
@@ -136,7 +138,7 @@ module.exports = {
   ],
 
   output: {
-    filename: 'webpack-bundle.js',
+    filename: 'hello-world-bundle.js',
     path: '../app/assets/webpack'
   },
 

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

@@ -20,7 +20,7 @@ Rake.application.remove_task('react_on_rails:assets:compile_environment')
 
 task 'react_on_rails:assets:compile_environment' do
   path = File.join(YourEngineName::Engine.root, 'client')
-  sh "cd #{path} && #{ReactOnRails.configuration.npm_build_production_command}"
+  sh "cd #{path} && #{ReactOnRails.configuration.build_production_command}"
 end
 ``` 
 ## In the project including your engine

data/docs/additional-reading/rspec-configuration.md

@@ -5,7 +5,6 @@ ReactOnRails provides a helper method called `ReactOnRails::TestHelper.configure
 
 ```ruby
 RSpec.configure do |config|
-  # Next line will ensure that assets are built if webpack -w is not running to build the bundles
   ReactOnRails::TestHelper.configure_rspec_to_compile_assets(config)
 ```
 
@@ -24,7 +23,9 @@ If you are using Webpack to build CSS assets, you should do something like this
 ```
 
 Please take note of the following:
-- This utility uses your `npm_build_test_command` to build the static generated files. This command **must** not include the `--watch` option. If you have different server and client bundle files, this command **must** create all the bundles.
+- This utility uses your `build_test_command` to build the static generated files. This command **must not** include the `--watch` option. If you have different server and client bundle files, this command **must** create all the bundles. If you are using webpacker, the default value will come from the `config/webpacker.yml` value for the `public_output_path` and the `source_path`
+- If you add an older file to your source files, that is already older than the produced output files, no new recompilation is done. The solution to this issue is to clear out your directory of webpack generated files when adding new source files that may have older dates. This is actually a common occurrence when you've built your test generated files and then you sync up your repository files.
+
 - By default, the webpack processes look for the `app/assets/webpack` folders (configured as setting `webpack_generated_files` in the `config/react_on_rails.rb`. If this folder is missing, is empty, or contains files in the `config.webpack_generated_files` list with `mtime`s older than any of the files in your `client` folder, the helper will recompile your assets. You can override the location of these files inside of `config/initializers/react_on_rails.rb` by passing a filepath (relative to the root of the app) to the `generated_assets_dir` configuration option.
 
 The following `config/react_on_rails.rb` settings **must** match your setup:
@@ -35,37 +36,19 @@ The following `config/react_on_rails.rb` settings **must** match your setup:
   config.generated_assets_dir = File.join(%w[public webpack], Rails.env)
 
   # Define the files we need to check for webpack compilation when running tests.
-  config.webpack_generated_files = %w( webpack-bundle.js )
+  # Generally, the manifest.json is good enough for this check if using webpacker
+  config.webpack_generated_files = %w( hello-world-bundle.js )
   
   # If you are using the ReactOnRails::TestHelper.configure_rspec_to_compile_assets(config)
   # with rspec then this controls what yarn command is run
   # to automatically refresh your webpack assets on every test run.
-  config.npm_build_test_command = "yarn run build:test"
+  config.build_test_command = "yarn run build:test"
 ```
 
-If you want to speed up the re-compiling process, you can call `yarn run build:development` (per below script) to have webpack run in "watch" mode and recompile these files in the background, which will be much faster when making incremental changes than compiling from scratch, assuming you have your setup like this:
-
-```
-  "scripts": {
-    "build:test": "webpack --config webpack.config.js",
-    "build:production": "NODE_ENV=production webpack --config webpack.config.js",
-    "build:development": "webpack -w --config webpack.config.js"
-  },
-```
+If you want to speed up the re-compiling process so you don't wait to run your tests to build the files, you can run your test compilation with the "watch" flags.
 
 [spec/dummy](https://github.com/shakacode/react_on_rails/tree/master/spec/dummy) contains examples of how to set the proc files for this purpose.
 
-## Hot Reloading
-If you're using the hot reloading setup, you'll be running a Webpack development server to provide the JavaScript and mabye CSS assets to your Rails app. If you're doing server rendering, you'll also have a webpack watch process to refresh the server rendering file. **If your server and client bundles are different**, and you run specs, the client bundle files will not be created until React on Rails detects it's out of date. Then your script to create all bundle files will redo the server bundle file. There's a few simple remedies for this situation:
-
-1. Switch to using static compilation of the webpack bundle files. This way, you're running a Webpack watch process to generate the same files used for tests as well as developmentment. You should have a separate Procfile for doing development using a "static" setup, rather than a "hot" setup.
-2. Change your Procfile for starting the hot reloading server to also run a webpack process to automatically rebuild a the client assets while also doing hot reloading for browser testing.
-
-Note, none of these issues matter if you're using the same file for both server and client side rendering.
-
-## Using RubyMine and other IDEs that save files right before invoking tests
-We had previously tried to allow using a process check to see if a Webpack watch process would already be automatically compiling the files. However, we removed this as it proved to be fragile with various setups. Thus, you want to hit the save keystroke when you save a JavaScript file, and then run your tests. Yes, you might not do this in time, and the test runner may be building the same files as you Webpack watch processes. This will probably happen infrequently, but if this does become an issue, we can look into bring back this functionality ([#398](https://github.com/shakacode/react_on_rails/pull/398)).
-
 If you want to use a testing framework other than RSpec, please submit let us know on the changes you need to do and we'll update the docs.
 
 ![2016-01-27_02-36-43](https://cloud.githubusercontent.com/assets/1118459/12611951/7c56d070-c4a4-11e5-8a80-9615f99960d9.png)

data/docs/api/ruby-api-hot-reload-view-helpers.md

@@ -1,4 +1,4 @@
-## NOTE: These helpers are NOT needed if using webpacker_lite
+## NOTE: These helpers are NOT needed if using webpacker
 
 ## Hot Reloading View Helpers
 The `env_javascript_include_tag` and `env_stylesheet_link_tag` support the usage of a webpack dev server for providing the JS and CSS assets during development mode. See the [shakacode/react-webpack-rails-tutorial](https://github.com/shakacode/react-webpack-rails-tutorial/) for a working example.
@@ -17,7 +17,7 @@ static vs. hot is picked based on whether `ENV["REACT_ON_RAILS_ENV"] == "HOT"`
  <!-- This is to load the hot assets. -->
  
  <!-- Note, you can have multiple files here. It's an array. -->
- <%= env_javascript_include_tag(hot: ['http://localhost:3500/webpack-bundle.js]') %>
+ <%= env_javascript_include_tag(hot: ['http://localhost:3500/hello-world-bundle.js]') %>
 
  <!-- These do use turbolinks -->
  <%= env_javascript_include_tag(static: 'application_static',

data/{lib/generators/react_on_rails/templates/base/base/config/initializers/react_on_rails.rb.tt → docs/basics/configuration.md}

@@ -1,54 +1,92 @@
-# Shown below are the defaults for configuration
-ReactOnRails.configure do |config|
-  # Client bundles are configured in application.js
+Here is the full set of config options.
 
-  # Directory where your generated assets go. All generated assets must go to the same directory.
-  # Configure this in your webpack config files. This relative to your Rails root directory.
-  config.generated_assets_dir = File.join(%w[public webpack], Rails.env)
+```yaml
+# frozen_string_literal: true
 
-  # Define the files we need to check for webpack compilation when running tests.
-  config.webpack_generated_files = %w( webpack-bundle.js )
+# NOTE: you typically will leave the commented out configurations set to their defaults.
+# Thus, you only need to pay careful attention to the non-commented settings in this file.
 
-  # This is the file used for server rendering of React when using `(prerender: true)`
-  # If you are never using server rendering, you may set this to "".
-  # If you are using the same file for client and server rendering, having this set probably does
-  # not affect performance.
-  config.server_bundle_js_file = "webpack-bundle.js"
-
-  # If you are using the ReactOnRails::TestHelper.configure_rspec_to_compile_assets(config)
-  # with rspec then this controls what yarn command is run
-  # to automatically refresh your webpack assets on every test run.
-  config.npm_build_test_command = "yarn run build:test"
+ReactOnRails.configure do |config|
+  # defaults to "" (top level)
+  #
+  config.node_modules_location = ""
 
   # This configures the script to run to build the production assets by webpack. Set this to nil
   # if you don't want react_on_rails building this file for you.
-  config.npm_build_production_command = "yarn run build:production"
+  config.build_production_command = "RAILS_ENV=production bin/webpack"
 
   ################################################################################
-  # CLIENT RENDERING OPTIONS
-  # Below options can be overriden by passing options to the react_on_rails
-  # `render_component` view helper method.
   ################################################################################
-  # default is false
-  config.prerender = false
+  # TEST CONFIGURATION OPTIONS
+  # Below options are used with the use of this test helper:
+  # ReactOnRails::TestHelper.configure_rspec_to_compile_assets(config)
+  ################################################################################
 
-  # default is true for development, off otherwise
-  config.trace = Rails.env.development?
+  # If you are using this in your spec_helper.rb (or rails_helper.rb):
+  #
+  # ReactOnRails::TestHelper.configure_rspec_to_compile_assets(config)
+  #
+  # with rspec then this controls what yarn command is run
+  # to automatically refresh your webpack assets on every test run.
+  #
+  config.build_test_command = "RAILS_ENV=test bin/webpack"
 
+  # Directory where your generated assets go. All generated assets must go to the same directory.
+  # If you are using webpacker, this value will come from your config/webpacker.yml file. 
+  # This is the default in webpacker.yml:
+  #   public_output_path: packs-test
+  # which means files in /public/packs-test
+  #
+  # Alternately, you may configure this. It is relative to your Rails root directory.
+  # A custom, non-webpacker, config might use something like:
+  #
+  config.generated_assets_dir = File.join(%w[public webpack], Rails.env)
+
+  # The test helper needs to know where your JavaScript files exist. The default is configured
+  # by your config/webpacker.yml soure_path:
+  # source_path: app/javascript
+  #
+  # If you have a non-default `node_modules_location`, that is assumed to be the location of your source
+  # files.
+
+  # Define the files we need to check for webpack compilation when running tests.
+  # The default is `%w( manifest.json )` as will be sufficient for most webpacker builds.
+  #
+  config.webpack_generated_files = %w( manifest.json )
+
+  ################################################################################
   ################################################################################
   # SERVER RENDERING OPTIONS
   ################################################################################
+  # This is the file used for server rendering of React when using `(prerender: true)`
+  # If you are never using server rendering, you should set this to "".
+  # Note, there is only one server bundle, unlike JavaScript where you want to minimize the size
+  # of the JS sent to the client. For the server rendering, React on Rails creates a pool of
+  # JavaScript execution instances which should handle any component requested.
+  #
+  # While you may configure this to be the same as your client bundle file, this file is typically
+  # different.
+  config.server_bundle_js_file = "server-bundle.js"
+
   # If set to true, this forces Rails to reload the server bundle if it is modified
+  # Default value is Rails.env.development?
+  #
   config.development_mode = Rails.env.development?
 
   # For server rendering. This can be set to false so that server side messages are discarded.
   # Default is true. Be cautious about turning this off.
+  # Default value is true
+  #
   config.replay_console = true
 
   # Default is true. Logs server rendering messages to Rails.logger.info
+  #
   config.logging_on_server = true
 
-  config.raise_on_prerender_error = false # change to true to raise exception on server if the JS code throws
+  # Default is to false to NOT raise exception on server if the JS code throws.
+  # Reason is that it's easier to debug this when you get the error over to the client.
+  # 
+  config.raise_on_prerender_error = false
 
   # Server rendering only (not for render_component helper)
   # You can configure your pool of JS virtual machines and specify where it should load code:
@@ -65,25 +103,26 @@ ReactOnRails.configure do |config|
   # Replace the following line to the location where you keep translation.js & default.js for use
   # by the npm packages react-intl. Be sure this directory exists!
   # config.i18n_dir = Rails.root.join("client", "app", "libs", "i18n")
+  # If not using the i18n feature, then leave this section commented out or set the value
+  # of config.i18n_dir to nil.
   #
   # Replace the following line to the location where you keep your client i18n yml files
   # that will source for automatic generation on translations.js & default.js
-  # By default(without this option) all yaml files from Rails.root.join("config", "locales") and installed gems are loaded
-  # config.i18n_yml_dir = Rails.root.join("config", "locales", "client")
+  # By default(without this option) all yaml files from Rails.root.join("config", "locales")
+  # and installed gems are loaded
+  config.i18n_yml_dir = Rails.root.join("config", "locales", "client")
 
   ################################################################################
-  # MISCELLANEOUS OPTIONS
   ################################################################################
+  # CLIENT RENDERING OPTIONS
+  # Below options can be overriden by passing options to the react_on_rails
+  # `render_component` view helper method.
+  ################################################################################
+  # default is false
+  config.prerender = false
 
-  # The server render method - either ExecJS or NodeJS
-  <%- if options.node? -%>
-  config.server_render_method = "NodeJS"
-  <%- else -%>
-  config.server_render_method = "ExecJS"
-  <%- end -%>
-
-  # If you want to use webpack for CSS and images, and still use the asset pipeline,
-  # see https://github.com/shakacode/react_on_rails/blob/master/docs/additional-reading/rails-assets.md
-  # And you will use a setting like this.
-  # config.symlink_non_digested_assets_regex = /\.(png|jpg|jpeg|gif|tiff|woff|ttf|eot|svg|map)/
+  # default is true for development, off otherwise
+  config.trace = Rails.env.development?
 end
+
+```

data/docs/basics/generator.md

@@ -13,7 +13,6 @@ Usage:
 
 Options:
   -R, [--redux], [--no-redux]                      # Install Redux gems and Redux version of Hello World Example. Default: false
-  -N, [--node], [--no-node]                        # Sets up node as a server rendering option. Default: false
       [--ignore-warnings], [--no-ignore-warnings]  # Skip warnings. Default: false
 
 Runtime options:
@@ -70,7 +69,3 @@ If you have used the `--redux` generator option, you will notice the familiar ad
 
 Note the organizational paradigm of "bundles". These are like application domains and are used for grouping your code into webpack bundles, in case you decide to create different bundles for deployment. This is also useful for separating out logical parts of your application. The concept is that each bundle will have it's own Redux store. If you have code that you want to reuse across bundles, including components and reducers, place them under `/client/app/lib`.
 
-### Using Images and Fonts
-The generator has amended the folders created in `client/assets/` to Rails's asset path. We recommend that if you have any existing assets that you want to use with your client code, you should move them to these folders and use webpack as normal. This allows webpack's development server to have access to your assets, as it will not be able to see any assets in the default Rails directories which are above the `/client` directory.
-
-Alternatively, if you have many existing assets and don't wish to move them, you could consider creating symlinks from client/assets that point to your Rails assets folders inside of `app/assets/`. The assets there will then be visible to both Rails and webpack.

data/docs/basics/installation-overview.md

@@ -4,11 +4,14 @@ Here's an overview of installation if you're not using the generator.
 
 Note, the best way to understand how to use ReactOnRails is to study the examples:
 
-1. [spec/dummy](../../spec/dummy): Simple, no DB example.
-2. [github.com/shakacode/react-webpack-rails-tutorial](https://github.com/shakacode/react-webpack-rails-tutorial): Full featured example.
+1. Run the generator per the [Tutorial](../../tutorial.md).
+2. [spec/dummy](../../spec/dummy): Simple, no DB example.
+3. [github.com/shakacode/react-webpack-rails-tutorial](https://github.com/shakacode/react-webpack-rails-tutorial): Full featured example.
 
 ## Configure the `/client` Directory
 
+Note, version 9.0 of React on Rails removed the requirement to place all client side files in the `/client` directory.
+
 This directory has no references to Rails outside of the destination directory for the files created by the various Webpack config files.
 
 The only requirements within this directory for basic React on Rails integration are:
@@ -23,12 +26,10 @@ The default path: `public/webpack` can be loaded with webpackConfigLoader as sho
 1. You create scripts in `client/package.json` per the example apps. These are used for building your Webpack assets. Also do this for your top level `package.json`.
 
 ## Rails Steps (outside of /client)
-1. Add  `gem "webpacker_lite"` to the Gemfile, run bundle. The gem provides the `stylesheet_pack_tag` and `javascript_pack_tag` helpers which is used to load the bundled assets to your layouts.[Dummy Example](../../spec/dummy/app/views/layouts/application.html.erb)
+1. Add  `gem "webpacker"` to the Gemfile, run bundle. The gem provides the `stylesheet_pack_tag` and `javascript_pack_tag` helpers which is used to load the bundled assets to your layouts.[Dummy Example](../../spec/dummy/app/views/layouts/application.html.erb)
 1. Configure the `config/initializers/react_on_rails.rb`. You can adjust some necessary settings and defaults. See file [spec/dummy/config/initializers/react_on_rails.rb](../../spec/dummy/config/initializers/react_on_rails.rb) for a detailed example of configuration, including comments on the different values to configure.
 1. Configure your Procfiles per the example apps. These are at the root of your Rails installation.
 1. Configure your top level JavaScript files for inclusion in your layout. You'll want a version that you use for static assets, and you want a file for any files in your setup that are not part of your webpack build. The reason for this is for use with hot-reloading. If you are not using hot reloading, then you only need to configure your `application.js` file to include your Webpack generated files. For more information on hot reloading, see [Hot Reloading of Assets For Rails Development](../additional-reading/hot-reloading-rails-development.md)
-
-1. Configure your `lib/tasks/assets.rake` file to run webpack during asset precompilation.
 1. If you are deploying to Heroku, see [heroku-deployment.md](/docs/additional-reading/heroku-deployment.md)
 
 If I missed anything, please submit a PR or file an issue.

data/docs/contributor-info/generator-testing.md

@@ -9,12 +9,3 @@ We are currently using Travis for CI. Because of the way Travis works, it is not
 ## Configuring what Apps are Generated
 You can specify additional apps to generate and test by adding to the rakelib/examples_config.yml file. The necessary build and test tasks will automatically be created for you dynamically at runtime.
 
-## More on the Rake Tasks
-In order to maximize efficiency, we took several steps to improve the performance of the rake tasks that utilize somewhat advanced rake functionality such as task dependencies, `file` tasks, task synthesizing, and concurrent tasks with `multitask`.
-
-For example, re-generating the app, running `yarn`, and re-generating the webpack bundles are all only done when they need to be done. Rake will also run certain tasks, including those that generate multiple applications, concurrently. 
-
-For more insight, see:
-
-- [Avdi Grimm's series of articles on Rake](http://devblog.avdi.org/2014/04/30/learn-advanced-rake-in-7-episodes/)
-- [Martin Fowler's rake article](http://martinfowler.com/articles/rake.html)