react_on_rails 11.0.0 → 12.0.0

data/CHANGELOG.md

@@ -1,28 +1,230 @@
 # Change Log
 All notable changes to this project's source code will be documented in this file. Items under `Unreleased` is upcoming features that will be out in next version. NOTE: major versions of the npm module and the gem must be kept in sync.
 
-Contributors: please follow the recommendations outlined at [keepachangelog.com](http://keepachangelog.com/). Please use the existing headings and styling as a guide, and add a link for the version diff at the bottom of the file. Also, please update the `Unreleased` link to compare to the latest release version.
+Migration instructions for the major updates can be found [here](docs/basics/upgrading-react-on-rails.md#upgrading-to-version-9.md). Some smaller migration information can be found here.
 
-See [Upgrading React on Rails](./docs/basics/upgrading-react-on-rails.md) for more concise instructions on upgrading.
+## Need Help Migrating?
+If you would like help in migrating between React on Rails versions or help with implementing server rendering, please contact [justin@shakacode.com](mailto:justin@shakacode.com) for information about our [React on Rails Pro Support Options](https://www.shakacode.com/react-on-rails-pro).
+
+We specialize in helping companies to quickly and efficiently move from versions before 9 to current. The older versions use the Rails asset pipeline to package client assets. The current and recommended way is to use Webpack 4 for asset preparation. You may also need help migrating from the `rails/webpacker`'s Webpack configuration to a better setup ready for Server Side Rendering.
+
+## Contributors
+Please follow the recommendations outlined at [keepachangelog.com](http://keepachangelog.com/). Please use the existing headings and styling as a guide, and add a link for the version diff at the bottom of the file. Also, please update the `Unreleased` link to compare to the latest release version.
 
 ## [Unreleased]
 Changes since last non-beta release.
 
 *Please add entries here for your pull requests that are not yet released.*
 
+## UPCOMING 12.0 RELEASE
+See [docs/basics/upgrading-react-on-rails.md](./docs/basics/upgrading-react-on-rails.md).
+
+### [12.0.0.pre.beta.2]
+* Changed the precompile task to use the rails/webpacker one by default
+
+### [12.0.0.pre.beta.1]
+* Updated generators to use React hooks
+
+### [12.0.0.pre.beta.0]
+Gem version: 12.0.0.pre.beta.0 and npm version 12.0.0-beta.0 released! Please try this out!
+
+#### BREAKING CHANGE
+In order to solve the issues regarding React Hooks compatibility, the number of parameters
+for functions is used to determine if you have a generator function that will get invoked to
+return a React component, or you are registering a functional React component. Alternately, you can
+set JavaScript property `renderFunction` on the function for which you want to return to be
+invoked to return the React component. In that case, you won't need to pass any unused params.
+[PR 1268](https://github.com/shakacode/react_on_rails/pull/1268) by [justin808](https://github.com/justin808)
+
+See [docs/basics/upgrading-react-on-rails](./docs/basics/upgrading-react-on-rails.md#upgrading-to-v12)
+for details.         
+
+* Requires the use of rails/webpacker helpers
+* If the webpacker webpack config files exist, then React on Rails will not override the default
+  assets:precompile setup by rails/webpacker. The fix is to remove the JS files inside of config/webpack,
+  like config/webpack/production.js.
+* Removed **env_javascript_include_tag** and **env_stylesheet_link_tag** as these are replaced by view helpers
+  from rails/webpacker
+* Removal of support for old Rubies and Rails.
+* Removal of config.symlink_non_digested_assets_regex as it's no longer needed with rails/webpacker.
+  If any business needs this, we can move the code to a separate gem.
+* Added configuration option `same_bundle_for_client_and_server` with default `false` because
+
+  1. Production applications would typically have a server bundle that differs from the client bundle
+  2. This change only affects trying to use HMR with react_on_rails with rails/webpacker. 
+  
+  The previous behavior was to always go to the webpack-dev-server for the server bundle if the 
+  webpack-dev-server was running _and_ the server bundle was found in the `manifest.json`. 
+  
+  If you are using the **same bundle for client and server rendering**, then set this configuration option
+  to `true`. By [justin808](https://github.com/shakacode/react_on_rails/pull/1240).
+  
+* Added support to export locales in JSON format. New option added `i18n_output_format` which allows to
+  specify locales format either `JSON` or `JS`. **`JSON` format is now the default.**
+ 
+  Use this config setting to get the old behavior: config.i18n_output_format = 'js'
+  
+  [PR 1271](https://github.com/shakacode/react_on_rails/pull/1271) by [ashgaliyev](https://github.com/ashgaliyev).
+
+#### Improved
+- Added Typescript definitions to the Node package. By [justin808](https://github.com/justin808) and [judahmeek](https://github.com/judahmeek) in [PR 1287](https://github.com/shakacode/react_on_rails/pull/1287).
+- Removed unnecessary restriction to keep the server bundle in the same directory with the client bundles. Rails/webpacker 4 has an advanced cleanup that will remove any files in the directory of other webpack files. Removing this restriction allows the server bundle to be created in a sibling directory. By [justin808](https://github.com/shakacode/react_on_rails/pull/1240).
+
+### [11.3.0] - 2019-05-24
+#### Added
+- Added method for retrieving any option from `render_options` [PR 1213](https://github.com/shakacode/react_on_rails/pull/1213)
+by [ashgaliyev](https://github.com/ashgaliyev).
+
+- html_options has an option for 'tag' to set the html tag name like this: `html_options: { tag: "span" }`.
+[PR 1208](https://github.com/shakacode/react_on_rails/pull/1208) by [tahsin352](https://github.com/tahsin352).
+
+### [11.2.2] - 2018-12-24
+#### Improved
+- rails_context can more easily be called from controller methods. The mandatory param of server_side has been made optional.
+
+### [11.2.1] - 2018-12-06
+## MIGRATION for v11.2
+- If using **React on Rails Pro**, upgrade react_on_rails_pro to a version >= 1.3.
+
+#### Improved
+- To support React v16, updated API for manually calling `ReactOnRails.render(name, props, domNodeId, hydrate)`. Added 3rd @param hydrate Pass truthy to update server rendered html. Default is falsey Any truthy values calls hydrate rather than render. [PR 1159](https://github.com/shakacode/react_on_rails/pull/1159) by [justin808](https://github.com/justin808) and [coopersamuel](https://github.com/coopersamuel).
+
+- Enabled the use of webpack-dev-server with Server-side rendering. [PR 1173](https://github.com/shakacode/react_on_rails/pull/1173) by [justin808](https://github.com/justin808) and [judahmeek](https://github.com/judahmeek).
+
+#### Changed
+- Changed the default for:
+  ```rb
+  config.raise_on_prerender_error = Rails.env.development?
+  ```
+
+  Thus, developers will need to fix server rendering errors before continuing.
+  [PR 1145](https://github.com/shakacode/react_on_rails/pull/1145) by [justin808](https://github.com/justin808).
+
+### 11.2.0 - 2018-12-06
+Do not use. Unpublished. Caused by an issue with the release script.
+
+### [11.1.8] - 2018-10-14
+
+#### Improved
+- Improved tutorial and support for HMR when using `rails/webpacker` for Webpack configuration. [PR 1156](https://github.com/shakacode/react_on_rails/pull/1156) by [justin808](https://github.com/justin808).
+
+### [11.1.7] - 2018-10-10
+#### Fixed
+- Fixed bug where intl parsing would fail when trying to parse integers or blank entries. by [sepehr500](https://github.com/sepehr500)
+
+### [11.1.6] - 2018-10-05
+#### Fixed
+- Fix client startup invoking render prematurely, **AGAIN**. Fix additional cases of client startup failing during interactive readyState". Closes [issue #1150](https://github.com/shakacode/react_on_rails/issues/1150). [PR 1152](https://github.com/shakacode/react_on_rails/pull/1152) by [rakelley](https://github.com/rakelley).
+
+### [11.1.5] - 2018-10-03
+#### Fixed
+- Fix client startup invoking render prematurely.  Closes [issue #1150](https://github.com/shakacode/react_on_rails/issues/1150). [PR 1151](https://github.com/shakacode/react_on_rails/pull/1151) by [rakelley](https://github.com/rakelley).
+
+### [11.1.4] - 2018-09-12
+
+#### Fixed
+- Ignore Arrays in Rails i18n yml files. [PR 1129](https://github.com/shakacode/react_on_rails/pull/1129) by [vcarel](https://github.com/vcarel).
+- Fix to apply transform-runtime. And work with Babel 6 and 7. (Include revert of [PR 1136](https://github.com/shakacode/react_on_rails/pull/1136)) [PR 1140](https://github.com/shakacode/react_on_rails/pull/1140) by [Ryunosuke Sato](https://github.com/tricknotes).
+- Upgrade Babel version to 7 [PR 1141](https://github.com/shakacode/react_on_rails/pull/1141) by [Ryunosuke Sato](https://github.com/tricknotes).
+
+### [11.1.3] - 2018-08-26
+
+#### Fixed
+- Don't apply babel-plugin-transform-runtime inside react-on-rails to work with babel 7. [PR 1136](https://github.com/shakacode/react_on_rails/pull/1136) by [Ryunosuke Sato](https://github.com/tricknotes).
+- Add support for webpacker 4 prereleases. [PR 1134](https://github.com/shakacode/react_on_rails/pull/1134) by [Judahmeek](https://github.com/Judahmeek))
+
+### [11.1.2] - 2018-08-18
+
+#### Fixed
+- Tests now properly exit if the config.build_test_command fails!
+- Source path for project using Webpacker would default to "app/javascript" even if when the node_modules
+  directory was set to "client". Fix now makes the configuration of this crystal clear.
+- renamed method RenderOptions.has_random_dom_id? to RenderOptions.random_dom_id? for rubocop rule.
+[PR 1133](https://github.com/shakacode/react_on_rails/pull/1133) by [justin808](https://github.com/justin808)
+
+### [11.1.1] - 2018-08-09
+#### Fixed
+- `TRUE` was deprecated in ruby 2.4, using `true` instead. [PR 1128](https://github.com/shakacode/react_on_rails/pull/1128) by [Aguardientico](https://github.com/Aguardientico).
+
+### [11.1.0] - 2018-08-07
+#### Added
+- Add random dom id option. This new global and react_component helper option allows configuring whether or not React on Rails will automatically add a random id to the DOM node ID. [PR 1121](https://github.com/shakacode/react_on_rails/pull/1121) by [justin808](https://github.com/justin808)
+  * Added configuration option random_dom_id
+  * Added method RenderOptions has_random_dom_id?
+#### Fixed
+- Fix invalid warn directive. [PR 1123](https://github.com/shakacode/react_on_rails/pull/1123) by [mustangostang](https://github.com/mustangostang).
+
+### [11.0.10] - 2018-07-22
+#### Fixed
+- Much better logging of rendering errors when there are lots of props. Only the a 1,000 chars are logged, and the center is indicated to be truncated. [PR 1117](https://github.com/shakacode/react_on_rails/pull/1117) and [PR 1118](https://github.com/shakacode/react_on_rails/pull/1118) by [justin808](https://github.com/justin808).
+- Properly clearing hydrated stores when server rendering. [PR 1120](https://github.com/shakacode/react_on_rails/pull/1120) by [squadette](https://github.com/squadette).
+
+### [11.0.9] - 2018-06-24
+- Handle <script async> for Webpack bundle transparently. Closes [issue #290](https://github.com/shakacode/react_on_rails/issues/290) [PR 1099](https://github.com/shakacode/react_on_rails/pull/1099) by [squadette](https://github.com/squadette). Merged in [PR 1107]( https://github.com/shakacode/react_on_rails/pull/1107).
+
+### [11.0.8] - 2018-06-15
+#### Fixed
+- HashWithIndifferent access for props threw if used for props. [PR 1100](https://github.com/shakacode/react_on_rails/pull/1100) by [justin808](https://github.com/justin808).
+- Test helper for detecting stale bundles did not properly handle the case of a server-bundle.js without a hash.[PR 1102](https://github.com/shakacode/react_on_rails/pull/1102) by [justin808](https://github.com/justin808).
+- Fix test helper determination of stale assets. [PR 1093](https://github.com/shakacode/react_on_rails/pull/1093) by [justin808](https://github.com/justin808).
+
+#### Changed
+- Document how to manually rehydrate XHR-substituted components on client side. [PR 1095](https://github.com/shakacode/react_on_rails/pull/1095) by [hchevalier](https://github.com/hchevalier).
+
+### [11.0.7] - 2018-05-16
+#### Fixed
+- Fix npm publshing. [PR 1090](https://github.com/shakacode/react_on_rails/pull/1090) by [justin808](https://github.com/justin808).
+
+### [11.0.6] - 2018-05-15
+#### Changed
+- Even more detailed errors for Honeybadger and Sentry when there's a JSON parse error on server rendering. [PR 1086](https://github.com/shakacode/react_on_rails/pull/1086) by [justin808](https://github.com/justin808).
+
+### [11.0.5] - 2018-05-11
+#### Changed
+- More detailed errors for Honeybadger and Sentry. [PR 1081](https://github.com/shakacode/react_on_rails/pull/1081) by [justin808](https://github.com/justin808).
+
+### [11.0.4] - 2018-05-3
+
+#### Changed
+- Throw if configuration.generated_assets_dir specified, and using webpacker, and if that doesn't match the public_output_path. Otherwise, warn if generated_assets_dir is specified
+- Fix the setup for tests for spec/dummy so they automatically rebuild by correctly setting the source_path in the webpacker.yml
+- Updated documentation for the testing setup.
+- Above in [PR 1072](https://github.com/shakacode/react_on_rails/pull/1072) by [justin808](https://github.com/justin808).
+- `react_component_hash` has implicit `prerender: true` because it makes no sense to have react_component_hash not use prerrender. Improved docs on `react_component_hash`. Also, fixed issue where checking gem existence. [PR 1077](https://github.com/shakacode/react_on_rails/pull/1077) by [justin808](https://github.com/justin808).
+
+### [11.0.3] - 2018-04-24
+
+#### Fixed
+- Fixed issue with component script initialization when using react_component_hash. [PR 1071](https://github.com/shakacode/react_on_rails/pull/1071) by [jblasco3](https://github.com/jblasco3).
+
+### [11.0.2] - 2018-04-24
+
+#### Fixed
+- Server rendering error for React on Rails Pro. [PR 1069](https://github.com/shakacode/react_on_rails/pull/1069) by [justin808](https://github.com/justin808).
+
+### [11.0.1] - 2018-04-23
+
+#### Added
+- `react_component` allows logging_on_server specified at the component level. [PR 1068](https://github.com/shakacode/react_on_rails/pull/1068) by [justin808](https://github.com/justin808).
+
+#### Fixed
+- Missing class when throwing some error messages. [PR 1068](https://github.com/shakacode/react_on_rails/pull/1068) by [justin808](https://github.com/justin808).
+
+### [11.0.0] - 2018-04-21
+
 ## MIGRATION for v11
 - Unused `server_render_method` was removed from the configuration. If you want to use a custom renderer, contact justin@shakacode.com. We have a custom node rendering solution in production for egghead.io.
 - Removed ReactOnRails::Utils.server_bundle_file_name and ReactOnRails::Utils.bundle_file_name. These are part of the performance features of "React on Rails Pro".
 - Removed ENV["TRACE_REACT_ON_RAILS"] usage and replacing it with config.trace.
 
-#### Enhanchements: Better Error Messages, Support for React on Rails Pro
+#### Enhancements: Better Error Messages, Support for React on Rails Pro
 - Tracing (debugging) options are simplified with a single `config.trace` setting that defaults to true for development and false otherwise.
-- Calls to setTimeout, setInterval, clearTimeout will now always log some message if config.trace is true. Your JavaScript code should not be calling setTimout when server rendering. 
+- Calls to setTimeout, setInterval, clearTimeout will now always log some message if config.trace is true. Your JavaScript code should not be calling setTimout when server rendering.
 - Errors raised are of type ReactOnRailsError, so you can see they came from React on Rails for debugging.
 - Removed ReactOnRails::Utils.server_bundle_file_name and ReactOnRails::Utils.bundle_file_name.
 - No longer logging the `railsContext` when server logging.
 - Rails.env is provided in the default railsContext, as suggested in [issue #697](https://github.com/shakacode/react_on_rails/issues/697).
-[PR 1018](https://github.com/shakacode/react_on_rails/pull/1065) by [justin808](https://github.com/justin808).
+[PR 1065](https://github.com/shakacode/react_on_rails/pull/1065) by [justin808](https://github.com/justin808).
 
 #### Fixes
 - More exact version checking. We keep the react_on_rails gem and the react-on-rails node package at
@@ -724,7 +926,34 @@ Best done with Object destructing:
 ##### Fixed
 - Fix several generator related issues.
 
-[Unreleased]: https://github.com/shakacode/react_on_rails/compare/10.1.4...master
+[Unreleased]: https://github.com/shakacode/react_on_rails/compare/12.0.0-beta.3...master
+[12.0.0.pre.beta.3]: https://github.com/shakacode/react_on_rails/compare/12.0.0-beta.2...12.0.0-beta.3
+[12.0.0.pre.beta.2]: https://github.com/shakacode/react_on_rails/compare/12.0.0-beta.1...12.0.0-beta.2
+[12.0.0.pre.beta.1]: https://github.com/shakacode/react_on_rails/compare/12.0.0-beta.0...12.0.0-beta.1
+[12.0.0.pre.beta.0]: https://github.com/shakacode/react_on_rails/compare/11.3.0...12.0.0-beta.0
+[11.3.0]: https://github.com/shakacode/react_on_rails/compare/11.2.2...11.3.0
+[11.2.2]: https://github.com/shakacode/react_on_rails/compare/11.2.1...11.2.2
+[11.2.1]: https://github.com/shakacode/react_on_rails/compare/11.1.8...11.2.1
+[11.1.8]: https://github.com/shakacode/react_on_rails/compare/11.1.7...11.1.8
+[11.1.7]: https://github.com/shakacode/react_on_rails/compare/11.1.6...11.1.7
+[11.1.6]: https://github.com/shakacode/react_on_rails/compare/11.1.5...11.1.6
+[11.1.5]: https://github.com/shakacode/react_on_rails/compare/11.1.4...11.1.5
+[11.1.4]: https://github.com/shakacode/react_on_rails/compare/11.1.3...11.1.4
+[11.1.3]: https://github.com/shakacode/react_on_rails/compare/11.1.2...11.1.3
+[11.1.2]: https://github.com/shakacode/react_on_rails/compare/11.1.1...11.1.2
+[11.1.1]: https://github.com/shakacode/react_on_rails/compare/11.1.0...11.1.1
+[11.1.0]: https://github.com/shakacode/react_on_rails/compare/11.0.10...11.1.0
+[11.0.10]: https://github.com/shakacode/react_on_rails/compare/11.0.9...11.0.10
+[11.0.9]: https://github.com/shakacode/react_on_rails/compare/11.0.8...11.0.9
+[11.0.8]: https://github.com/shakacode/react_on_rails/compare/11.0.7...11.0.8
+[11.0.7]: https://github.com/shakacode/react_on_rails/compare/11.0.6...11.0.7
+[11.0.6]: https://github.com/shakacode/react_on_rails/compare/11.0.5...11.0.6
+[11.0.5]: https://github.com/shakacode/react_on_rails/compare/11.0.4...11.0.5
+[11.0.4]: https://github.com/shakacode/react_on_rails/compare/11.0.3...11.0.4
+[11.0.3]: https://github.com/shakacode/react_on_rails/compare/11.0.2...11.0.3
+[11.0.2]: https://github.com/shakacode/react_on_rails/compare/11.0.1...11.0.2
+[11.0.1]: https://github.com/shakacode/react_on_rails/compare/11.0.0...11.0.1
+[11.0.0]: https://github.com/shakacode/react_on_rails/compare/10.1.4...11.0.0
 [10.1.4]: https://github.com/shakacode/react_on_rails/compare/10.1.3...10.1.4
 [10.1.3]: https://github.com/shakacode/react_on_rails/compare/10.1.2...10.1.3
 [10.1.2]: https://github.com/shakacode/react_on_rails/compare/10.1.1...10.1.2

data/CONTRIBUTING.md

@@ -1,46 +1,9 @@
 # Tips for Contributors
 
-* See [docs/contributor-info/Releasing](./docs/contributor-info/releasing.md) for instructions on releasing.
+* [docs/contributor-info/Releasing](./docs/contributor-info/releasing.md) for instructions on releasing.
+* [docs/contributor-info/pull-requests](./docs/contributor-info/pull-requests.md)
 * See other docs in [docs/contributor-info](./docs/contributor-info)
 
-## Summary
-
-For non-doc fixes:
-
-* Provide changelog entry in the [unreleased section of the CHANGELOG.md](https://github.com/shakacode/react_on_rails/blob/master/CHANGELOG.md#unreleased).
-* Ensure CI passes and that you added a test that passes with the fix and fails without the fix.
-* Squash all commits down to one with a nice commit message *ONLY* once final review is given. Make sure this single commit is rebased on top of master.
-* Please address all code review comments.
-* Ensure that docs are updated accordingly if a feature is added.
-
-## Commit Messages
-
-From [How to Write a Git Commit Message](http://chris.beams.io/posts/git-commit/)
-
-#### The seven rules of a great git commit message
-> Keep in mind: This has all been said before.
-
-1. Separate subject from body with a blank line
-1. Limit the subject line to 50 characters
-1. Capitalize the subject line
-1. Do not end the subject line with a period
-1. Use the imperative mood in the subject line
-1. Wrap the body at 72 characters
-1. Use the body to explain what and why vs. how
-
-
-## Doc Changes
-
-When making doc changes, we want the change to work on both the gitbook and the regular github site. The issue is that non-doc files will not go to the gitbook site, so doc references to non doc files must use the github URL.
-
-### Links to other docs:
-* When making references to doc files, use a relative URL path like:
-`[Installation Overview](docs/basics/installation-overview.md)`
-
-* When making references to source code files, use a full url path like:
-`[spec/dummy/config/initializers/react_on_rails.rb](https://github.com/shakacode/react_on_rails/tree/master/spec/dummy/config/initializers/react_on_rails.rb)`
-
-
 ## To run tests:
 * After updating code via git, to prepare all examples and run all tests:
 
@@ -75,7 +38,7 @@ It's critical to configure your IDE/editor to ignore certain directories. Otherw
 # Configuring your test app to use your local fork
 You can test the `react-on-rails` gem using your own external test app or the gem's internal `spec/dummy` app. The `spec/dummy` app is an example of the various setup techniques you can use with the gem.
 ```
-├── test
+├── test_app
 |    └── client
 └── react_on_rails
     └── spec
@@ -91,61 +54,63 @@ gem "react_on_rails", path: "../path-to-react-on-rails"
 
 Note that you will need to bundle install after making this change, but also that **you will need to restart your Rails application if you make any changes to the gem**.
 
-## Testing the Node package for react-on-rails
+## Testing the Node package for react-on-rails via Yalc
 In addition to testing the Ruby parts out, you can also test the node package parts of the gem with an external application. First, be **sure** to build the NPM package:
 
 ```sh
 cd react_on_rails/
 yarn
-yarn run build
+
+# Update the lib directory with babel compiled files
+yarn run build:watch
 ```
+   
+You need to do this once:
 
-Install the local package by using a relative path in your test/client app's `package.json`, like this:
-```sh
-cd test/client
-rm -rf node_modules/react-on-rails && npm i 'file:../path-to-react-on-rails-top-package.json'
 ```
-_Note: You must use npm here till yarn stops preferring cached packages over local. see [issue #2649](https://github.com/yarnpkg/yarn/issues/2649)_
+# Will send the updates to other folders
+yalc publish
+cd spec/dummy
+yalc add react-on-rails
+```
 
-When you use a relative path, be sure to run the above `yarn` command whenever you change the node package for react-on-rails.
+The workflow is:
+1. Make changes to the node package.
+2. We need yalc to push and then run yarn:
+```
+cd <top dir>
+# Will send the updates to other folders
+yalc push
+cd spec/dummy
 
-#### Example: Testing NPM changes with the dummy app
-1. Add `console.log('Hello!')` [here](https://github.com/shakacode/react_on_rails/blob/master/node_package/src/clientStartup.js#L181) in `react_on_rails/node_package/src/clientStartup.js` to confirm we're getting an update to the node package.
-2. The "postinstall" script of "spec/dummy/client" calls "yarn link react-on-rails" to setup a sym link to the parent package.
-3. Refresh the browser if the server is already running or start the server using `foreman start` from `react_on_rails/spec/dummy` and navigate to `http://localhost:5000/`. You will now see the `Hello!` message printed in the browser's console.
+# Will update from yalc
+yarn
+```
 
-_Note: running `npm i` automatically builds the npm package before installing. However, when using yarn you will need to run `yarn run build` in the root directory before the install script. This will be updated when [yarn issue #2649](https://github.com/yarnpkg/yarn/issues/2649) (above) is resolved._
+When you run `yalc push`, you'll get an informative message
 
-# Development Setup for Gem and Node Package Contributors
+```
+✗ yalc push
+react-on-rails@12.0.0-12070fd1 published in store.
+Pushing react-on-rails@12.0.0 in /Users/justin/shakacode/react-on-rails/react_on_rails/spec/dummy
+Package react-on-rails@12.0.0-12070fd1 added ==> /Users/justin/shakacode/react-on-rails/react_on_rails/spec/dummy/node_modules/react-on-rails.
+Don't forget you may need to run yarn after adding packages with yalc to install/update dependencies/bin scripts.
+```
 
-## Checklist before Committing
-1. `rake`: runs all linters and specs (you need Docker setup, see below)
-2. Did you need any more tests for your change?
-3. Did you document your change? Update the README.md?
+#### Example: Testing NPM changes with the dummy app
+1. Add `console.log('Hello!')` to [clientStartup.ts, function render](https://github.com/shakacode/react_on_rails/blob/master/node_package/src/clientStartup.ts in `/node_package/src/clientStartup.js` to confirm we're getting an update to the node package client side. Do the same for function `serverRenderReactComponent` in `/node_package/src/serverRenderReactComponent.ts`.
+2. Refresh the browser if the server is already running or start the server using `foreman start` from `react_on_rails/spec/dummy` and navigate to `http://localhost:5000/`. You will now see the `Hello!` message printed in the browser's console. If you did not see that message, then review the steps above for the workflow of making changes and pushing them via yalc.
+
+# Development Setup for Gem and Node Package Contributors
 
 ## Dev Initial Setup
 
 ### Prereqs
 After checking out the repo, making sure you have rvm and nvm setup (setup ruby and node), cd to `spec/dummy` and run `bin/setup` to install ruby dependencies. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
 
-Additionally, our RSpec tests use the poltergeist web driver. You will need to install the phantomjs node module:
-
-```sh
-yarn global add phantomjs-prebuilt
-```
-
-Note this *must* be installed globally for the dummy test project rspec runner to see it properly.
-
 ### Local Node Package
-Because the example and dummy apps rely on the react-on-rails node package, they should link directly to your local version to pick up any changes you may have made to that package. To achieve this, switch to the dummy app's root directory and run this command below which runs something like [this script](spec/dummy/package.json#L14)
 
-```sh
-cd react_on_rails/spec/dummy
-yarn run install-react-on-rails
-```
-_Note: this runs npm under the hood as explained in **Test NPM for react-on-rails** section above_
-
-From now on, the example and dummy apps will use your local node_package folder as the react-on-rails node package. This will also be done automatically for you via the `rake examples:gen_all` rake task.
+Note, the example and dummy apps will use your local node_package folder as the react-on-rails node package. This will also be done automatically for you via the `rake examples:gen_all` rake task.
 
 *Side note: It's critical to use the alias section of the webpack config to avoid a double inclusion error. This has already been done for you in the example and dummy apps, but for reference:*
 
@@ -172,7 +137,7 @@ spec/dummy.
 
 ```sh
 # Optionally change default selenium_firefox driver
-export DRIVER=poltergeist
+export DRIVER=selenium_firefox
 cd react_on_rails/
 yarn run dummy:spec
 ```
@@ -191,13 +156,6 @@ cd react_on_rails/spec/dummy
 rspec
 ```
 
-Eventually, we may have JS tests:
-
-```sh
-cd react_on_rails/spec/dummy/client
-yarn run test
-```
-
 ### Run most tests and linting
 
 ```sh
@@ -206,7 +164,7 @@ yarn run check
 ```
 
 ### Starting the Dummy App
-To run the dummy app, it's **CRITICAL** to not just run `rails s`. You have to run `foreman start`. If you don't do this, then `webpack` will not generate a new bundle, and you will be seriously confused when you change JavaScript and the app does not change. If you change the webpack configs, then you need to restart foreman. If you change the JS code for react-on-rails, you need to run `yarn run build`. Since the react-on-rails package should be sym linked, you don't have to `yarn react-on-rails` after every change.
+To run the dummy app, it's **CRITICAL** to not just run `rails s`. You have to run `foreman start` with one of the Procfiles. If you don't do this, then `webpack` will not generate a new bundle, and you will be seriously confused when you change JavaScript and the app does not change. If you change the webpack configs, then you need to restart foreman. If you change the JS code for react-on-rails, you need to run `yarn run build`. Since the react-on-rails package should be sym linked, you don't have to `yarn react-on-rails` after every change.
 
 ### RSpec Testing
 Run `rake` for testing the gem and `spec/dummy`. Otherwise, the `rspec` command only works for testing within the sample apps, like `spec/dummy`.
@@ -228,10 +186,26 @@ In your Rails app add this gem with a path to your fork.
 
 ```ruby
 gem 'react_on_rails', path: '../relative/path/to/react_on_rails'
-```
+```                                                             
+
+Then run `bundle`.
 
 The main installer can be run with ```rails generate react_on_rails:install```
 
+Then use yalc to add the npm module. 
+
+Be sure that your ran this first at the top level of React on Rails
+
+```
+yalc publish
+```
+
+Then add the node package to your test app:
+
+```
+yalc add react-on-rails
+```
+
 ### Testing the Generator
 The generators are covered by generator tests using Rails's generator testing helpers, but it never hurts to do a sanity check and explore the API. See [generator_testing_script.md](generator_testing_script.md) for a script on how to run the generator on a fresh project.
 
@@ -256,6 +230,12 @@ You can run specific linting for directories or files by using `docker-compose r
 
 `docker-compose run lint bash` sets you up to run from the container command line.
 
+### Updating Rubocop
+2 files require updating to update the Rubocop version:
+
+1. `react_on_rails.gemspec`
+2. `spec/dummy/Gemfile`
+
 ### Docker CI - Test and Linting
 Docker CI and Tests containers have a xvfd server automatically started for headless browser testing with selenium and Firefox.
 

data/Gemfile

@@ -15,14 +15,14 @@ gem "jbuilder"
 gem "jquery-rails"
 gem "mini_racer"
 gem "puma"
-
 gem "rails_12factor"
 gem "ruby-lint", require: false
 gem "sass-rails"
 gem "scss_lint", require: false
 gem "sdoc", group: :doc
 gem "spring"
-gem "sqlite3"
+gem "sprockets", "~>3.0"
+gem "sqlite3", "~> 1.3.6"
 gem "turbolinks"
 gem "uglifier"
 gem "web-console", group: :development
@@ -30,13 +30,11 @@ gem "web-console", group: :development
 # below are copied from spec/dummy/Gemfile
 gem "capybara"
 gem "capybara-screenshot"
-gem "chromedriver-helper"
 gem "launchy"
-gem "poltergeist"
 gem "rspec-rails"
 gem "rspec-retry"
 gem "selenium-webdriver"
-gem "webpacker"
+gem "webpacker", ">= 4.0.0"
 
 gem "equivalent-xml", github: "mbklein/equivalent-xml"
 gem "rainbow"

data/KUDOS.md

@@ -2,11 +2,14 @@ This is a sibling file to [PROJECTS.md](./PROJECTS.md).
 
 I'm looking for quotes on why you like using React on Rails. You might mention any benefits you particularly like and if you've migrated from react-rails. Just click to edit and github will automatically open up a PR. Thanks to everybody that contributes!
 
+## September 23, 2018, [#1148](https://github.com/shakacode/react_on_rails/issues/1148#issue-363039856).
+
+![2018-09-26_22-17-28](https://user-images.githubusercontent.com/1118459/46132537-ffe40e00-c1d9-11e8-8bbc-868370fcb8f9.png)
+
 ## September 20, 2017, By [ShakaCode Forum](https://forum.shakacode.com/t/new-ror-users-inbound/1014)
 
 ![2017-10-07_00-18-43](https://user-images.githubusercontent.com/1118459/31306902-341a537a-aaf5-11e7-8014-28c126a7c975.png)
 
-
 ## June 9, 2017
 By Github Issue [#868](https://github.com/shakacode/react_on_rails/issues/868)
 

data/{docs/LICENSE.md → LICENSE.md}

@@ -1,6 +1,6 @@
 # The MIT License (MIT)
 
-Copyright (c) 2017 Justin Gordon and ShakaCode, http://www.shakacode.com
+Copyright (c) 2017, 2018 Justin Gordon and ShakaCode, http://www.shakacode.com
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

data/PROJECTS.md

@@ -11,6 +11,13 @@ April 11, 2018: 2138
 
 ## Commercial Products Live
 * **[Hawaii Chee](https://www.hawaiichee.com/)**, the signature product of [ShakaCode](http://www.shakacode.com), which is a vacation rental site focusing on Hawaii.
+* **[RedFlagDeals](https://www.redflagdeals.com/)**, Canadian shopping site.
+* **[YourMechanic](https://www.yourmechanic.com/)**, home calls for mechanics.
+* **[Suntransfers](https://www.suntransfers.com/)**, airport car rides site.
+* **[Decanter](http://www.decanter.com/)**, wine site.
+* **[LocalWise](https://www.localwise.com/)**, local job site.
+* **[Ellevest](https://www.ellevest.com/)**, investments for women.
+* **[OppenheimerFunds](https://www.oppenheimerfunds.com/)**, investment site.
 * **[KissKissBankBank](https://www.kisskissbankbank.com/)**, large French crowdfunding platform.
 * **[HVMN](https://hvmn.com)**: Web ecommerce site for "biohacking" products.
 * **[GuavaPass](https://guavapass.com/)**: Coaching client of [ShakaCode](http://www.shakacode.com) and React on Rails fan!
@@ -27,7 +34,6 @@ April 11, 2018: 2138
 * **[Undeveloped](https://undeveloped.com/)**: Buy and sell domain names. ![image](https://cloud.githubusercontent.com/assets/1118459/19623703/7c6d63d0-9870-11e6-83f2-8b83ca49daa9.png)
 * **[Foxford.ru](http://foxford.ru/)**: Online School ![2016-12-17_13-23-21](https://cloud.githubusercontent.com/assets/1118459/21290377/1adacdf2-c45c-11e6-97c1-f726ab749b2d.png)
 * **[CareerBuilder for Employers](https://hiring.careerbuilder.com/)**: CareerBuilder's marketing/ecommerce website. We've integrated React on Rails and have deployed the application via Cloud 66, and are busy integrating this into other projects!
-* **[Josephine](https://www.josephine.com)**: The private network for home cooked meals.
 * **[first](https://first.io/)**: Data-driven Relational Marketing for Real Estate.
 
 ## Open Source Projects Live