react-on-rails - npm Package Versions

[11.0.8] - 2018-06-15

Fixed

• HashWithIndifferent access for props threw if used for props. PR 1100 by justin808.
• Test helper for detecting stale bundles did not properly handle the case of a server-bundle.js without a hash.PR 1102 by justin808.
• Fix test helper determination of stale assets. PR 1093 by justin808.

Changed

• Document how to manually rehydrate XHR-substituted components on client side. PR 1095 by hchevalier.

[11.0.7] - 2018-05-16

Fixed

• Fix npm publishing. PR 1090 by 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 by justin808.

[11.0.5] - 2018-05-11

Changed

• More detailed errors for Honeybadger and Sentry. PR 1081 by 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 by 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 by justin808.

[11.0.3] - 2018-04-24

Fixed

• Fixed issue with component script initialization when using react_component_hash. PR 1071 by jblasco3.

[11.0.2] - 2018-04-24

Fixed

• Server rendering error for React on Rails Pro. PR 1069 by justin808.

[11.0.1] - 2018-04-23

Added

• react_component allows logging_on_server specified at the component level. PR 1068 by justin808.

Fixed

• Missing class when throwing some error messages. PR 1068 by 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.

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.
• 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. PR 1065 by justin808.

Fixes

• More exact version checking. We keep the react_on_rails gem and the react-on-rails node package at the same exact versions so that we can be sure that the interaction between them is precise. This is so that if a bug is detected after some update, it's critical that both the gem and the node package get the updates. This change ensures that the package.json specification does not use a ~ or ^ as reported in issue #1062. PR 1063 by justin808.
• Sprockets: Now use the most recent manifest when creating symlinks. See issue #1023. PR 1064 by justin808.