react_on_rails 13.4.0 → 14.0.0

data/.scss-lint.yml

@@ -1,205 +0,0 @@
-# See http://sass-guidelin.es/#zeros
-
-scss_files:
-  - 'spec/dummy/app/assets/stylesheets/**/*.scss'
-exclude:
-  - 'spec/dummy/app/assets/stylesheets/application.css'
-linters:
-#  BangFormat:
-#    enabled: true
-#    space_before_bang: true
-#    space_after_bang: false
-#
-#  BorderZero:
-#    enabled: true
-#    convention: zero # or `none`
-#
-  ColorKeyword:
-    enabled: false
-  ColorVariable:
-    enabled: false
-#
-#  Comment:
-#    enabled: true
-#
-#  DebugStatement:
-#    enabled: true
-#
-#  DeclarationOrder:
-#    enabled: true
-#
-#  DuplicateProperty:
-#    enabled: true
-#
-#  ElsePlacement:
-#    enabled: true
-#    style: same_line # or 'new_line'
-#
-#  EmptyLineBetweenBlocks:
-#    enabled: true
-#    ignore_single_line_blocks: true
-#
-#  EmptyRule:
-#    enabled: true
-#
-#  FinalNewline:
-#    enabled: true
-#    present: true
-#
-  HexLength:
-    enabled: true
-    style: long
-
-  HexNotation:
-    enabled: true
-    style: uppercase
-#
-#  HexValidation:
-#    enabled: true
-#
-  IdSelector:
-    enabled: true
-#
-#  ImportantRule:
-#    enabled: true
-#
-#  ImportPath:
-#    enabled: true
-#    leading_underscore: false
-#    filename_extension: false
-#
-#  Indentation:
-#    enabled: true
-#    allow_non_nested_indentation: false
-#    character: space # or 'tab'
-#    width: 2
-#
-  LeadingZero:
-    enabled: true
-    style: include_zero
-#
-#  MergeableSelector:
-#    enabled: true
-#    force_nesting: true
-#
-#  NameFormat:
-#    enabled: true
-#    allow_leading_underscore: true
-#    convention: hyphenated_lowercase # or 'camel_case', or 'snake_case', or a regex pattern
-#
-#  NestingDepth:
-#    enabled: true
-#    max_depth: 3
-#
-#  PlaceholderInExtend:
-#    enabled: true
-#
-#  PropertyCount:
-#    enabled: false
-#    include_nested: false
-#    max_properties: 10
-#
-#  PropertyUnits:
-#    enabled: true
-#    global: [
-#      'ch', 'em', 'ex', 'rem',                 # Font-relative lengths
-#      'cm', 'in', 'mm', 'pc', 'pt', 'px', 'q', # Absolute lengths
-#      'vh', 'vw', 'vmin', 'vmax',              # Viewport-percentage lengths
-#      'deg', 'grad', 'rad', 'turn',            # Angle
-#      'ms', 's',                               # Duration
-#      'Hz', 'kHz',                             # Frequency
-#      'dpi', 'dpcm', 'dppx',                   # Resolution
-#      '%',                                     # Other
-#    ]
-#    properties: {}
-#
-#  PropertySortOrder:
-#    enabled: true
-#    ignore_unspecified: false
-#    separate_groups: false
-#
-#  PropertySpelling:
-#    enabled: true
-#    extra_properties: []
-#
-#  QualifyingElement:
-#    enabled: true
-#    allow_element_with_attribute: false
-#    allow_element_with_class: false
-#    allow_element_with_id: false
-#
-#  SelectorDepth:
-#    enabled: true
-#    max_depth: 3
-#
-#  SelectorFormat:
-#    enabled: true
-#    convention: hyphenated_lowercase # or 'strict_BEM', or 'hyphenated_BEM', or 'snake_case', or 'camel_case', or a regex pattern
-#
-#  Shorthand:
-#    enabled: true
-#    allowed_shorthands: [1, 2, 3]
-#
-#  SingleLinePerProperty:
-#    enabled: true
-#    allow_single_line_rule_sets: true
-#
-#  SingleLinePerSelector:
-#    enabled: true
-#
-#  SpaceAfterComma:
-#    enabled: true
-#
-#  SpaceAfterPropertyColon:
-#    enabled: true
-#    style: one_space # or 'no_space', or 'at_least_one_space', or 'aligned'
-#
-#  SpaceAfterPropertyName:
-#    enabled: true
-#
-#  SpaceBeforeBrace:
-#    enabled: true
-#    style: space # or 'new_line'
-#    allow_single_line_padding: false
-#
-#  SpaceBetweenParens:
-#    enabled: true
-#    spaces: 0
-#
-#  StringQuotes:
-#    enabled: true
-#    style: single_quotes # or double_quotes
-#
-#  TrailingSemicolon:
-#    enabled: true
-#
-#  TrailingZero:
-#    enabled: false
-#
-#  UnnecessaryMantissa:
-#    enabled: true
-#
-#  UnnecessaryParentReference:
-#    enabled: true
-#
-#  UrlFormat:
-#    enabled: true
-#
-#  UrlQuotes:
-#    enabled: true
-#
-#  VariableForProperty:
-#    enabled: false
-#    properties: []
-#
-#  VendorPrefix:
-#    enabled: true
-#    identifier_list: base
-#    additional_identifiers: []
-#    excluded_identifiers: []
-#
-#  ZeroUnit:
-#    enabled: true
-#
-#  Compass::*:
-#    enabled: false

data/.travis.yml

@@ -1,61 +0,0 @@
-sudo: required
-
-language: ruby
-
-rvm:
-  - 2.5.3
-  - 2.6.5
-  - 2.7.0
-
-services:
-  - docker
-
-cache:
-  bundler: true
-  directories:
-    - node_modules # NPM packages
-  yarn: true
-
-gemfile:
-  - spec/dummy/Gemfile
-
-env:
-  global:
-    - RAILS_ENV=test
-    - DRIVER=selenium_chrome
-    - CHROME_BIN=/usr/bin/google-chrome
-    - USE_COVERALLS=TRUE
-
-before_install:
-  - sudo apt-get update
-  - sudo apt-get install -y xvfb libappindicator1 fonts-liberation
-  - wget https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb
-  - sudo dpkg -i google-chrome*.deb
-  - "/sbin/start-stop-daemon --start --quiet --pidfile /tmp/custom_xvfb_99.pid --make-pidfile --background --exec /usr/bin/Xvfb -- :99 -ac -screen scn 1600x1200x16"
-
-install:
-  - travis_retry gem install bundler -v '>2'
-  - travis_retry nvm install 14
-  - node -v
-  - travis_retry npm i -g yarn
-  - travis_retry yarn global add yalc
-  - travis_retry yalc add react-on-rails
-  - travis_retry yarn
-  - travis_retry bundle install
-  - travis_retry yarn run build
-  - travis_retry yalc publish
-  - cd spec/dummy
-  - travis_retry yalc add react-on-rails
-  - travis_retry yarn
-  - cd ../..
-  - bundle exec rake prepare_for_ci
-
-before_script:
-  - "export DISPLAY=:99"
-
-script:
-  - bundle exec rake
-
-notifications:
-  slack:
-    secure: LfcUk4AJ4vAxWwRIyw4tFh8QNbYefMwfG/oLfsN3CdRMWMOtCOHR1GGsRhAOlfVVJ/FvHqVqWj5gK7z7CaO5Uvl7rD3/zJ8QzExKx/iH9yWj55iIPuKLzwFNnBwRpFW/cqyU2lFPPRxGD50BUn3c+qybkuSqtKZ6qtTowwqlxLa5iyM3N95aZp7MEIKCP7cPcnHfLbJyP8wBpotp/rtw62eXM2HIRJJwgjcp+n+My7VFR9DnBXNFf6R91aZHM4U4cHHDbu15HFtH8honVrzK1JQdyqMNHga+j04dFuaS7z9Q369/hsELMOBp/227+Pz7ZRfWZFK4UASguOvyeX7RmGTRpTuWLm1XJeUzfsPZVROecaSVQBve+U7F12yKqilt97QlvRXn2EGyBILqvxtFNNR4S9kgAf72/6EFgiM1TKq7i9zy6lVOnagU2+7amq7UeopX1uoFsUfNKMR7YbgV1WjF0IK95UP0b0/7ZOJlPYgi5zzkQi129qAFWSMmxGk+ZpsttHh/tjJtvAh0A3mHq/zb5w4ub/MbSyZqeDUNgGj72QArOWUFSAStQT1ybsVLeDoKPgOvVq7OV1D64rpcHjBXcqOCit8tDZ+TqkFhcYJo2cITSaqE4zJXn+4F5s7So5O8CyfKYQq+kFJCooYGmfgTUckJpGl7eIvKmL4TN9Q=

data/book.json

@@ -1,18 +0,0 @@
-{
-  "gitbook": "3.1.1",
-  "title": "React on Rails Documentation",
-  "plugins": ["prism", "-highlight", "github"],
-  "pluginsConfig": {
-    "github": {
-      "url": "https://github.com/shakacode/react_on_rails/"
-    },
-    "sharing": {
-      "facebook": true,
-      "twitter": true,
-      "google": true,
-      "weibo": true,
-      "instapaper": true,
-      "vk": true
-    }
-  }
-}

data/docs/additional-details/generator-details.md

@@ -1,56 +0,0 @@
-# Generator Details
-
-The `react_on_rails:install` generator combined with the example pull requests of generator runs will get you up and running efficiently. There's a fair bit of setup with integrating Webpack with Rails. Defaults for options are such that the default is for the flag to be off. For example, the default for `-R` is that `redux` is off, and the default of `-b` is that `skip-bootstrap` is off.
-
-Run `rails generate react_on_rails:install --help` for descriptions of all available options:
-
-```
-Usage:
-  rails generate react_on_rails:install [options]
-
-Options:
-  -R, [--redux], [--no-redux]                      # Install Redux gems and Redux version of Hello World Example. Default: false
-      [--ignore-warnings], [--no-ignore-warnings]  # Skip warnings. Default: false
-
-Runtime options:
-  -f, [--force]                    # Overwrite files that already exist
-  -p, [--pretend], [--no-pretend]  # Run but do not make any changes
-  -q, [--quiet], [--no-quiet]      # Suppress status output
-  -s, [--skip], [--no-skip]        # Skip files that already exist
-
-Description:
-
-The react_on_rails:install generator integrates webpack with rails with ease. You
-can pass the redux option if you'd like to have redux setup for you automatically.
-
-* Redux
-
-    Passing the --redux generator option causes the generated Hello World example
-    to integrate the Redux state container framework. The necessary node modules
-    will be automatically included for you.
-
-*******************************************************************************
-
-
-Then you may run
-
-    `rails s`
-```
-
-Another good option is to create a simple test app per the [Tutorial](https://www.shakacode.com/react-on-rails/docs/guides/tutorial/).
-
-# Understanding the Organization of the Generated Client Code
-The generated client code follows our organization scheme. Each unique set of functionality, is given its own folder inside of `app/javascript/app/bundles`. Note, the recommended for bigger projects is `client/app/bundles`. This encourages for modularity of *domains*.
-
-Inside of the generated "HelloWorld" domain you will find the following folders:
-
-+  `startup`: This contains the entry point files for webpack. It defaults to a single file that is used for server and client compilation, but if these need to be different, then you can create two webpack configurations with separate endpoints.
-+ `containers`: "smart components" (components that have functionality and logic that is passed to child "dumb components").
-+ `components`: includes "dumb components", or components that simply render their properties and call functions given to them as properties by a parent component. Ultimately, at least one of these dumb components will have a parent container component.
-
-You may also notice the `app/lib` folder. This is for any code that is common between bundles and therefore needs to be shared (for example, middleware).
-
-## Redux
-If you have used the `--redux` generator option, you will notice the familiar additional redux folders in addition to the aforementioned folders. The Hello World example has also been modified to use Redux.
-
-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`.

data/docs/additional-details/manual-installation-overview.md

@@ -1,30 +0,0 @@
-# Manual Installation Overview
-
-TODO: Review this file
-
-
-This file summarizes what the React on Rails generator does.
-
-## Configure 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:
-
-1. Your webpack configuration files:
-   1. Create outputs in a directory like `/public/webpack`, which is customizable in your `config/initializers/react_on_rails.rb`.
-   1. Provide server rendering if you wish to use that feature.
-1. Your JavaScript code "registers" any components and stores per the ReactOnRails APIs of ReactOnRails.register(components) and ReactOnRails.registerStore(stores). See [our javascript API docs](https://www.shakacode.com/react-on-rails/docs/api/javascript-api/) and the [ReactOnRails.js source](https://github.com/shakacode/react_on_rails/tree/master/node_package/src/ReactOnRails.js).
-1. Set your registration file as an "entry" point in your Webpack configs.
-1. Add the [Manifest plugin](https://github.com/danethurber/webpack-manifest-plugin) to your config.
-The default path: `public/webpack` can be loaded with webpackConfigLoader as shown in the dummy example.
-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"` 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](https://github.com/shakacode/react_on_rails/tree/master/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 [https://github.com/shakacode/react_on_rails/tree/master/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) 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.
-1. If you are deploying to Heroku, see [our heroku deployment documentation](https://www.shakacode.com/react-on-rails/docs/deployment/heroku-deployment/)
-
-If I missed anything, please submit a PR or file an issue.

data/docs/additional-details/migrating-from-react-rails.md

@@ -1,17 +0,0 @@
-## Migrate From react-rails
-If you are using [react-rails](https://github.com/reactjs/react-rails) in your project, it is pretty simple to migrate to [react_on_rails](https://github.com/shakacode/react_on_rails).
-
-- Remove the 'react-rails' gem from your Gemfile.
-
-- Remove the generated lines for react-rails in your application.js file.
-
-```
-//= require react
-//= require react_ujs
-//= require components
-```
-
-- Follow our [getting started guide](https://www.shakacode.com/react-on-rails/docs/getting-started/).
-
-Note: If you have components from react-rails you want to use, then you will need to port them into react_on_rails which uses webpack instead of the asset pipeline.
-

data/docs/additional-details/recommended-project-structure.md

@@ -1,69 +0,0 @@
-# Recommended Project structure
-
-The React on Rails generator uses the standard Shakapacker convention of this structure:
-
-```yml
-app/javascript:
-  ├── bundles:
-  │   # Logical groups of files that can be used for code splitting
-  │   └── hello-world-bundle.js
-  ├── packs:
-  │   # only webpack entry files here
-  │   └── hello-world-bundle.js
-```
-
-Per the example repo [shakacode/react_on_rails_demo_ssr_hmr](https://github.com/shakacode/react_on_rails_demo_ssr_hmr),
-you should consider keeping your codebase mostly consistent with the defaults for [Shakapacker](https://github.com/shakacode/shakapacker).
-
-## Steps to convert from the generator defaults to use a `/client` directory for source code 
-
-1. Move the directory:
-
-```
-mv app/javascript client
-```
-
-2. Edit your `/config/shakapacker.yml` file. Change the `default/source_path`:
-
-```yml
-  source_path: client
-```
-
-## Moving node_modules from `/` to `/client` with a custom webpack setup.
-
-Shakapacker probably doesn't support having your main node_modules directory under `/client`, so only follow these steps if you want to use your own webpack configuration.
-
-1. Move the `/package.json` to `/client/package.json`
-2. Create a `/package.json` that delegates to `/client/package.json`. 
-   ```
-     "scripts": {
-       "heroku-postbuild": "cd ./client && yarn"
-     },
-   ```
-3. If your `node_modules` directory is not at the top level of the Rails project, then you will need to set the
-ENV value of `SHAKAPACKER_CONFIG` to the location of the `config/shakapacker.yml` file per [rails/webpacker PR 2561](https://github.com/rails/webpacker/pull/2561). (Notice the change of spelling from Webpacker to Shakapacker)
-
-## CSS, Sass, Fonts, and Images
-Should you move your styling assets to Webpack? Or stick with the plain Rails asset pipeline. It depends!
-
-Here's a good discussion of this option: [Why does Rails 6 include both Webpacker and Sprockets?](https://rossta.net/blog/why-does-rails-install-both-webpacker-and-sprockets.html). 
-
-You have 2 basic choices:
-
-### Simple Rails Way
-This isn't really any technique, as you keep handling all your styling assets using Rails standard tools, such as using the [sass-rails gem](https://rubygems.org/gems/sass-rails/versions/5.0.4). Basically, Webpack doesn't get involved with styling. Your Rails layouts just doing the styling the standard Rails way.
-
-#### Advantages to the Simple Rails Way
-1. Much simpler! There's no changes really from your current processes.
-
-### Using Webpack to Manage Styling Assets
-This technique involves customization of the webpack config files to generate CSS, image, and font assets. 
-
-#### Directory structure
-1. `/client/app/assets`: Assets for CSS for client app.
-1. `/client/app/assets/fonts` and `/client/app/assets/styles`: Globally shared assets for styling. Note, most Sass and image assets will be stored next to the JavaScript files.
-
-#### Advantages to having Webpack Manage Styles
-1. You can use [CSS modules](https://github.com/css-modules/css-modules), which is super compelling once you seen the benefits.
-1. You can use CSS in JS.
-1. You can do hot reloading of your assets. Thus, you do not have to refresh your web page to see asset change, including changing styles.

data/docs/additional-details/tips-for-usage-with-sp6.md

@@ -1,15 +0,0 @@
-# Tips for usage with Shakapacker 6
-
-As mentioned earlier in the documentation, we assume you install ReactOnRails in a project with Shakapacker 7+ installed and configured. If you still use Shakapacker 6, we encourage you to check the upgrade to the version 7 guide. Otherwise, you need to consider the following:
-
-1. The install generator tries to take the necessary steps to adapt the installed files to match the file structure and configurations for Shakapacker 6. So you don't need to be worried about the ReactOnRails installation process.
-
-2. Check the following table to map the references in the documentation to the relevant ones in Shakapacker 6:
-
-  |Usage in Shakapacker 7      |Equivalant in Shakapacker 6|
-  |----------------------------|---------------------------|
-  |`config/shakapacker.yml`    |`config/webpacker.yml`     |
-  |`bin/shakapacker`           |`bin/webpacker`            |
-  |`bin/shakapacker-dev-server`|`bin/webpacker-dev-server` |
-
-3. Any environment variables starting with `SHAKAPACKER_*` should be changed to `WEBPACKER_*`.

data/docs/additional-details/updating-dependencies.md

@@ -1,31 +0,0 @@
-# Updating Dependencies
-
-If you frequently update you dependencies in small batches, you will avoid large and painful updates later. Then again, if you don't have good tests coverage, it's hazardous to update dependencies at any time.
-
-## Ruby
-
-Delete any unwanted version constraints from your Gemfile and run:
-
-```bash
-bundle update
-```
-
-## NPM
-
-1. Install [npm-check-updates](https://www.npmjs.com/package/npm-check-updates)
-1. Run `yarn outdated` and read CHANGELOGs of major updated packages before you update. You might not be ready for some updates.
-1. Run these commands. You may or may not need to `rm -rf` your `node_modules` directory. 
-
-```
-cd client
-ncu -u -a
-yarn
-```
-
-Some combinations that I often run:
-
-### remove old installed `node_modules` so you only get what corresponds to package.json
-```
-ncu -u -a && rm -rf node_modules && yarn
-```
-

data/docs/additional-details/upgrade-webpacker-v3-to-v4.md

@@ -1,10 +0,0 @@
-# Upgrading rails/webpacker v3.5 to v4
-
-The following steps can be followed to update a Webpacker v3.5 app to v4.
-
-1. Update the gem `webpacker` and the package `@rails/webpacker`
-1. Merge changes from the new default [.babelrc](https://github.com/shakacode/react_on_rails/tree/master/lib/install/config/.babelrc) to your `/.babelrc`. If you are using React, you need to add `"@babel/preset-react"`, to the list of `presets`.
-1. Copy the file [.browserslistrc](https://github.com/shakacode/react_on_rails/tree/master/lib/install/config/.browserslistrc) to `/`.
-1. Merge any differences between [config/webpacker.yml](https://github.com/shakacode/react_on_rails/tree/master/lib/install/config/webpacker.yml) and your `/config/webpacker.yml`.
-
-Here is an [example commit of these changes](https://github.com/shakacode/react_on_rails-tutorial-v11/pull/1/files).

data/docs/api/javascript-api.md

@@ -1,99 +0,0 @@
-# ReactOnRails JavaScript API
-## CSRF protection
-
-Rails has built-in protection for Cross-Site Request Forgery (CSRF), see [Rails Documentation](http://guides.rubyonrails.org/security.html#cross-site-request-forgery-csrf). To nicely utilize this feature in JavaScript requests, React on Rails provides two helpers that can be used as following for POST, PUT or DELETE requests:
-
-```js
-import ReactOnRails from 'react-on-rails';
-
-// reads from DOM csrf token generated by Rails in <%= csrf_meta_tags %>
-csrfToken = ReactOnRails.authenticityToken();
-
-// compose Rails specific request header as following { X-CSRF-Token: csrfToken, X-Requested-With: XMLHttpRequest }
-header = ReactOnRails.authenticityHeaders(otherHeader);
-```
-
-If you are using [jquery-ujs](https://github.com/rails/jquery-ujs) for AJAX calls, then these helpers are not needed because the [jquery-ujs](https://github.com/rails/jquery-ujs) library updates header automatically, see [jquery-ujs documentation](https://robots.thoughtbot.com/a-tour-of-rails-jquery-ujs#cross-site-request-forgery-protection).
-
-
-
-## API
-
-The best source of docs is the main [ReactOnRails.js](https://github.com/shakacode/react_on_rails/node_package/src/ReactOnRails.js) file. Here's a quick summary. No guarantees that this won't be outdated!
-
-```js
-  /**
-   * Main entry point to using the react-on-rails npm package. This is how Rails will be able to
-   * find you components for rendering. Components get called with props, or you may use a
-   * "Render-Function" to return a React component or an object with the following shape:
-   * { renderedHtml, redirectLocation, error }.
-   * For server rendering, if you wish to return multiple HTML strings from a Render-Function,
-   * you may return an Object from your Render-Function with a single top level property of
-   * renderedHtml. Inside this Object, place a key called componentHtml, along with any other
-   * needed keys. This is useful when you using side effects libraries like react helmet.
-   * Your Ruby code with get this Object as a Hash containing keys componentHtml and any other
-   * custom keys that you added:
-   * { renderedHtml: { componentHtml, customKey1, customKey2 } }
-   * See the example in https://www.shakacode.com/react-on-rails/docs/javascript/react-helmet
-   * @param components (key is component name, value is component)
-   */
-  register(components)
-
-  /**
-   * Allows registration of store generators to be used by multiple react components on one Rails
-   * view. store generators are functions that take one arg, props, and return a store. Note that
-   * the setStore API is different in tha it's the actual store hydrated with props.
-   * @param stores (key is store name, value is the store generator)
-   */
-  registerStore(stores)
-
-  /**
-   * Allows retrieval of the store by name. This store will be hydrated by any Rails form props.
-   * Pass optional param throwIfMissing = false if you want to use this call to get back null if the
-   * store with name is not registered.
-   * @param name
-   * @param throwIfMissing Defaults to true. Set to false to have this call return undefined if
-   *        there is no store with the given name.
-   * @returns Redux Store, possibly hydrated
-   */
-  getStore(name, throwIfMissing = true )
-
-  /**
-   * Renders or hydrates the react element passed. In case react version is >=18 will use the new api.
-   * @param domNode
-   * @param reactElement
-   * @param hydrate if true will perform hydration, if false will render
-   * @returns {Root|ReactComponent|ReactElement|null}
-   */
-  reactHydrateOrRender(domNode, reactElement, hydrate)
-
-  /**
-   * Set options for ReactOnRails, typically before you call ReactOnRails.register
-   * Available Options:
-   * `traceTurbolinks: true|false Gives you debugging messages on Turbolinks events
-   */
-  setOptions(options)
-
-  /**
-   * Allow directly calling the page loaded script in case the default events that trigger react
-   * rendering are not sufficient, such as when loading JavaScript asynchronously with TurboLinks:
-   * More details can be found here:
-   * https://www.shakacode.com/react-on-rails/docs/rails/turbolinks
-   */
-  reactOnRailsPageLoaded()
-
-  /**
-   * Returns CSRF authenticity token inserted by Rails csrf_meta_tags
-   * @returns String or null
-   */
-
-  authenticityToken()
-
-  /**
-   * Returns header with csrf authenticity token and XMLHttpRequest
-   * @param {*} other headers
-   * @returns {*} header
-   */
-
-  authenticityHeaders(otherHeaders = {})
-```