All Versions
130
Latest Version
Avg Release Cycle
61 days
Latest Release
607 days ago

Changelog History
Page 11

  • v6.0.4 Changes

    June 13, 2016
    🛠 Fixed
    • Added polyfill for clearTimeout which is used by babel-polyfill #451 by martyphee

  • v6.0.3 Changes

    June 07, 2016
    🛠 Fixed

  • v6.0.2 Changes

    June 06, 2016
    🛠 Fixed
    • Fix colisions in ids of DOM nodes generated by react_component by indexing in using an UUID rather than an auto-increment value. This means that it should be overriden using the id parameter of react_component if one wants to generate a predictable id (e.g. for testing purpose). See Issue #437. Fixed in #438 by Michael Baudino.

  • v6.0.1 Changes

    May 27, 2016
    🛠 Fixed

  • v6.0.0 Changes

    May 25, 2016
    💥 Breaking Changes
    • ➕ Added automatic compilation of assets at precompile is now done by ReactOnRails. Thus, you don't need to provide your own assets.rake file that does the precompilation. #398 by robwise, jbhatab, and justin808.

    • Migration to v6

      • Do not run the generator again if you've already run it.
      • See shakacode/react-webpack-rails-tutorial/pull/287 for an example of upgrading from v5.
      • To configure the asset compliation you can either
      • Specify a config/react_on_rails setting for build_production_command to be nil to turn this feature off.
      • Specify the script command you want to run to build your production assets, and remove your assets.rake file.
      • If you are using the ReactOnRails test helper, then you will need to add the 'config.npm_build_test_command' to your config to tell react_on_rails what command to run when you run rspec.

    • ⬆️ See shakacode/react-webpack-rails-tutorial #287 for an upgrade example. The PR has a few comments on the upgrade.

    Here is the addition to the generated config file:

      # 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.build_production_command = "npm run build:production"

  # If you are using the ReactOnRails::TestHelper.configure_rspec_to_compile_assets(config)
  # with rspec then this controls what npm command is run
  # to automatically refresh your webpack assets on every test run.
  config.npm_build_test_command = "npm run build:test"
    🛠 Fixed
    • Fixed errors when server rendered props contain \u2028 or \u2029 characters #375 by mariusandra
    • Fixed "too early unmount" which caused problems with Turbolinks 5 not updating the screen #425 by szyablitsky
    ➕ Added
    • Experimental ability to use node.js process for server rendering. See #380 by alleycat-at-git.
    • Non-digested version of assets in public folder #413 by alleycat-at-git.
    • Cache client/node_modules directory to prevent Heroku from reinstalling all modules from scratch #324 by modosc.
    • ReactOnRails.reactOnRailsPageLoaded() is exposed in case one needs to call this manually and information on async script loading added. See #315 by SqueezedLight.
    🔄 Changed
    • #398 by robwise, jbhatab, and justin808 contains:
      • Only one webpack config is generated for server and client config. Package.json files were changed to reflect this.
      • Added npm_build_test_command to allow developers to change what npm command is automatically run from rspec.
    • Replace URI with Addressable gem. See #405 by lucke84
    ✂ Removed
    • #398 by robwise, jbhatab, and justin808 contains:
      • Server rendering is no longer an option in the generator and is always accessible.
      • Removed lodash, jquery, and loggerMiddleware from the generated code.
      • Removed webpack watch check for test helper automatic compilation.

  • v5.2.0 Changes

    April 08, 2016
    ➕ Added
    • Support for React 15.0 to react_on_rails. See #379 by brucek.
    • Support for Node.js server side rendering. See #380 by alleycat and doc
    ✂ Removed
    • Generator removals to simplify installer. See #364 by jbhatab.
      • Removed options for heroku, boostrap, and the linters from generator.
      • Removed install for the Webpack Dev Server, as we can now do hot reloading with Rails, so the complexity of this feature is not justified. Nevertheless, the setup of React on Rails still supports this setup, just not with the generator.
      • Documentation added for removed installer options.

  • v5.1.1 Changes

    April 04, 2016
    🛠 Fixed
    • Security Fixes: Address failure to sanitize console messages when server rendering and displaying in the browser console. See #366 and #370 by justin808
    ➕ Added
    • 🚅 railsContext includes the port number and a boolean if the code is being run on the server or client.

  • v5.1.0 Changes

    April 03, 2016
    ➕ Added

    All 5.1.0 changes can be found in #362 by justin808.

    • Generator enhancements
      • Generator adds line to spec/rails_helper.rb so that running specs will ensure assets are compiled.
      • Other small changes to the generator including adding necessary npm scripts to allow React on Rails to build assets.
      • Npm modules updated for generator.
      • Added babel-runtime in to the client/package.json created.
    • Server rendering
      • Added more diagnostics for server rendering.
      • Calls to setTimeout and setInterval are not logged for server rendering unless env TRACE_REACT_ON_RAILS is set to YES.
    • ⚡️ Updated all project npm dependencies to latest.
    • ⚡️ Update to node 5.10.0 for CI.
    • ➕ Added babel-runtime as a peer dependency for the npm module.

  • v5.0.0 Changes

    April 01, 2016
    ➕ Added
    • Added railsContext, an object which gets passed always as the second parameter to both react component and redux store generator functions, both for server and client rendering. This provides data like the current locale, the pathname, etc. The data values are customizable by a new configuration called rendering_extension where you can create a module with a method called rendering_extension. This allows you to add additional values to the Rails Context. Implement one static method called custom_context(view_context) and return a Hash. See #345 by justin808
    🔄 Changed
    • Previously, you could pass arbitrary additional html attributes to react_component. Now, you need to pass them in as a named parameter html_options to react_component.
    💥 Breaking Changes
    • 👀 You must provide named attributes, including props for view helper react_component. See this commit for an example migration used for www.reactrails.com.

  • v4.0.3 Changes

    March 17, 2016
    🛠 Fixed
    • 🗄 ReactOnRailsHelper#react_component: Invalid deprecation message when called with only one paramter, the component name.