react_on_rails 12.0.0.pre.beta.1 → 12.0.1

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: react_on_rails
 version: !ruby/object:Gem::Version
-  version: 12.0.0.pre.beta.1
+  version: 12.0.1
 platform: ruby
 authors:
 - Justin Gordon
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2020-06-14 00:00:00.000000000 Z
+date: 2020-07-10 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: addressable
@@ -80,6 +80,20 @@ dependencies:
     - - "~>"
       - !ruby/object:Gem::Version
         version: '3.0'
+- !ruby/object:Gem::Dependency
+  name: webpacker
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '4.0'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '4.0'
 - !ruby/object:Gem::Dependency
   name: awesome_print
   requirement: !ruby/object:Gem::Requirement
@@ -332,6 +346,7 @@ files:
 - docs/additional-reading/asset-pipeline.md
 - docs/additional-reading/capistrano-deployment.md
 - docs/additional-reading/convert-rails-5-api-only-app.md
+- docs/additional-reading/converting-from-custom-webpack-config-to-rails-webpacker-config.md
 - docs/additional-reading/credits.md
 - docs/additional-reading/elastic-beanstalk.md
 - docs/additional-reading/foreman-issues.md
@@ -359,6 +374,8 @@ files:
 - docs/basics/configuration.md
 - docs/basics/deployment.md
 - docs/basics/generator-details.md
+- docs/basics/heroku-deployment.md
+- docs/basics/hmr-and-hot-reloading-with-the-webpack-dev-server.md
 - docs/basics/i18n.md
 - docs/basics/installation-into-an-existing-rails-app.md
 - docs/basics/migrating-from-react-rails.md
@@ -378,7 +395,6 @@ files:
 - docs/misc/code_of_conduct.md
 - docs/misc/doctrine.md
 - docs/outdated/code-splitting.md
-- docs/outdated/heroku-deployment.md
 - docs/outdated/how-react-on-rails-works.md
 - docs/outdated/manual-installation-overview.md
 - docs/outdated/rails-assets-relative-paths.md
@@ -488,9 +504,9 @@ required_ruby_version: !ruby/object:Gem::Requirement
       version: 2.5.0
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
-  - - ">"
+  - - ">="
     - !ruby/object:Gem::Version
-      version: 1.3.1
+      version: '0'
 requirements: []
 rubygems_version: 3.0.8
 signing_key: 

data/docs/outdated/heroku-deployment.md

@@ -1,86 +0,0 @@
-# Heroku Deployment
-The generator has created the necessary files and gems for deployment to Heroku. If you have installed manually, you will need to provide these files yourself:
-
-+ `Procfile`: used by Heroku and Foreman to start the Puma server
-+ `'puma'` gem: recommended Heroku webserver
-+ `config/puma.rb`: Puma webserver config file
-
-If you want to see an updated example deployed to Heroku, please visit the [github.com/shakacode/react-webpack-rails-tutorial](https://github.com/shakacode/react-webpack-rails-tutorial).
-
-## More details on precompilation using webpack to create JavaScript assets
-This is how the `assets:precompile` rake task gets modified by `react_on_rails`. You should be able to call `clear_prerequisites` and setup your own custom precompile if needed.
-```ruby
-# These tasks run as pre-requisites of assets:precompile.
-# Note, it's not possible to refer to ReactOnRails configuration values at this point.
-Rake::Task["assets:precompile"]
-    .clear_prerequisites
-    .enhance([:environment, "react_on_rails:assets:compile_environment"])
-```    
-
-For an example of how to do this, see the [dummy app](https://github.com/shakacode/react_on_rails/blob/master/spec/dummy/lib/tasks/assets.rake).
-
-## Caching Node Modules
-By default Heroku will cache the root `node_modules` directory between deploys but since we're installing in `client/node_modules` you'll need to add the following line to the `package.json` in your root directory (otherwise you'll have to sit through a full `yarn` on each deploy):
-
-```js
-"cacheDirectories": [
-  "node_modules",
-  "client/node_modules"
-],
-```
-
-## How to Deploy
-
-React on Rails requires both a ruby environment (for Rails) and a Node environment (for Webpack), so you will need to have Heroku use multiple buildpacks.
-
-Assuming you have downloaded and installed the Heroku command-line utility and have initialized the app, you will need to tell Heroku to use both buildpacks via the command-line:
-
-```
-heroku buildpacks:set heroku/ruby
-heroku buildpacks:add --index 1 heroku/nodejs
-```
-
-For more information, see [Using Multiple Buildpacks for an App](https://devcenter.heroku.com/articles/using-multiple-buildpacks-for-an-app)
-
-## Fresh Rails Install
-
-### Swap out sqlite for postgres by doing the following:
-
-#### 1. Delete the line with `sqlite` and replace it with:
-
-```ruby
-   gem 'pg'
-```
-
-#### 2. Replace your `database.yml` file with this (assuming your app name is "ror")
-
-```yml
-default: &default
-  adapter: postgresql
-  username:
-  password:
-  host: localhost
-
-development:
-  <<: *default
-  database: ror_development
-
-# Warning: The database defined as "test" will be erased and
-# re-generated from your development database when you run "rake".
-# Do not set this db to the same as development or production.
-test:
-  <<: *default
-  database: ror_test
-
-production:
-  <<: *default
-  database: ror_production
-```
-
-Run:
-
-```
-bundle
-bin/rake db:setup
-bin/rake db:migrate
-```