react_on_rails 11.0.5 → 13.4.0

data/docs/basics/configuration.md

@@ -1,163 +0,0 @@
-Here is the full set of config options. This file is `/config/initializers/react_on_rails.rb`
-
-```ruby
-# frozen_string_literal: true
-
-# NOTE: you typically will leave the commented out configurations set to their defaults.
-# Thus, you only need to pay careful attention to the non-commented settings in this file.
-ReactOnRails.configure do |config|
-  # `trace`: General debugging flag.
-  # The default is true for development, off otherwise.
-  # With true, you get detailed logs of rendering and stack traces if you call setTimout, 
-  # setInterval, clearTimout when server rendering.
-  config.trace = Rails.env.development?
-
-
-  # defaults to "" (top level)
-  #
-  config.node_modules_location = ""
-
-  # 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 = "RAILS_ENV=production bin/webpack"
-
-  ################################################################################
-  ################################################################################
-  # TEST CONFIGURATION OPTIONS
-  # Below options are used with the use of this test helper:
-  # ReactOnRails::TestHelper.configure_rspec_to_compile_assets(config)
-  ################################################################################
-
-  # If you are using this in your spec_helper.rb (or rails_helper.rb):
-  #
-  # ReactOnRails::TestHelper.configure_rspec_to_compile_assets(config)
-  #
-  # with rspec then this controls what yarn command is run
-  # to automatically refresh your webpack assets on every test run.
-  #
-  config.build_test_command = "RAILS_ENV=test bin/webpack"
-
-  # Directory where your generated assets go. All generated assets must go to the same directory.
-  # If you are using webpacker, this value will come from your config/webpacker.yml file. 
-  # This is the default in webpacker.yml:
-  #   public_output_path: packs-test
-  # which means files in /public/packs-test
-  #
-  # Alternately, you may configure this. It is relative to your Rails root directory.
-  # A custom, non-webpacker, config might use something like:
-  #
-  # config.generated_assets_dir = File.join(%w[public webpack], Rails.env)
-  # This setting should not be used if using webpacker. 
-
-  # The test helper needs to know where your JavaScript files exist. The default is configured
-  # by your config/webpacker.yml soure_path:
-  # source_path: app/javascript
-  #
-  # If you have a non-default `node_modules_location`, that is assumed to be the location of your source
-  # files.
-
-  # Define the files we need to check for webpack compilation when running tests.
-  # The default is `%w( manifest.json )` as will be sufficient for most webpacker builds.
-  #
-  config.webpack_generated_files = %w( manifest.json )
-  
-  # You can optionally add values to your rails_context. See example below for RenderingExtension
-  # config.rendering_extension = RenderingExtension
-
-  ################################################################################
-  ################################################################################
-  # SERVER RENDERING OPTIONS
-  ################################################################################
-  # This is the file used for server rendering of React when using `(prerender: true)`
-  # If you are never using server rendering, you should set this to "".
-  # Note, there is only one server bundle, unlike JavaScript where you want to minimize the size
-  # of the JS sent to the client. For the server rendering, React on Rails creates a pool of
-  # JavaScript execution instances which should handle any component requested.
-  #
-  # While you may configure this to be the same as your client bundle file, this file is typically
-  # different.
-  #
-  config.server_bundle_js_file = "server-bundle.js"
-
-  # If set to true, this forces Rails to reload the server bundle if it is modified
-  # Default value is Rails.env.development?
-  #
-  config.development_mode = Rails.env.development?
-
-  # For server rendering so that it replays in the browser console.
-  # This can be set to false so that server side messages are not displayed in the browser.
-  # Default is true. Be cautious about turning this off.
-  # Default value is true
-  # 
-  config.replay_console = true
-
-  # Default is true. Logs server rendering messages to Rails.logger.info. If false, you'll only
-  # see the server rendering messages in the browser console.
-  #
-  config.logging_on_server = true
-
-  # Default is to false to NOT raise exception on server if the JS code throws.
-  # Reason is that it's easier to debug this when you get the error over to the client.
-  # 
-  config.raise_on_prerender_error = false
-
-  ################################################################################
-  # Server Renderer Configuration for ExecJS
-  ################################################################################
-  # The default server rendering is ExecJS, probably using the mini_racer gem
-  # If you wish to use an alternative Node server rendering for higher performance, 
-  # contact justin@shakacode.com for details.
-  # 
-  # For ExecJS:
-  # You can configure your pool of JS virtual machines and specify where it should load code:
-  # On MRI, use `mini_racer` for the best performance
-  # (see [discussion](https://github.com/reactjs/react-rails/pull/290))
-  # On MRI, you'll get a deadlock with `pool_size` > 1
-  # If you're using JRuby, you can increase `pool_size` to have real multi-threaded rendering.
-  config.server_renderer_pool_size = 1 # increase if you're on JRuby
-  config.server_renderer_timeout = 20 # seconds
-
-  ################################################################################
-  # I18N OPTIONS
-  ################################################################################
-  # Replace the following line to the location where you keep translation.js & default.js for use
-  # by the npm packages react-intl. Be sure this directory exists!
-  # config.i18n_dir = Rails.root.join("client", "app", "libs", "i18n")
-  # If not using the i18n feature, then leave this section commented out or set the value
-  # of config.i18n_dir to nil.
-  #
-  # Replace the following line to the location where you keep your client i18n yml files
-  # that will source for automatic generation on translations.js & default.js
-  # By default(without this option) all yaml files from Rails.root.join("config", "locales")
-  # and installed gems are loaded
-  config.i18n_yml_dir = Rails.root.join("config", "locales", "client")
-  
-  ################################################################################
-  ################################################################################
-  # CLIENT RENDERING OPTIONS
-  # Below options can be overriden by passing options to the react_on_rails
-  # `render_component` view helper method.
-  ################################################################################
-  # default is false
-  config.prerender = false
-end
-
-```
-
-Example of a RenderingExtension for custom values in the `rails_context`:
-
-```ruby
-module RenderingExtension
-
-  # Return a Hash that contains custom values from the view context that will get merged with
-  # the standard rails_context values and passed to all calls to generator functions used by the
-  # react_component and redux_store view helpers
-  def self.custom_context(view_context)
-    {
-     somethingUseful: view_context.session[:something_useful]
-    }
-  end
-end
-```
-
-

data/docs/basics/i18n.md

@@ -1,77 +0,0 @@
-# How to add I18n
-
-Here's a summary of adding the I18n functionality.
-
-You can refer to [react-webpack-rails-tutorial](https://github.com/shakacode/react-webpack-rails-tutorial) and [PR #340](https://github.com/shakacode/react-webpack-rails-tutorial/pull/340), [commmited](https://github.com/shakacode/react-webpack-rails-tutorial/commit/ef369ed9d922aea5116ca7e50208169fd7831389) for a complete example.
-
-1. Add `react-intl` & `intl` to `client/package.json`, and remember to `bundle && yarn install`.
-
-  ```js
-  "dependencies": {
-    ...
-    "intl": "^1.2.5",
-    "react-intl": "^2.1.5",
-    ...
-  }
-  ```
-
-2. Add `config.i18n_dir` in `config/initializers/react_on_rails.rb`
-
-  `react-intl` requires locale files in json format. React on Rails will generate `translations.js` & `default.js` automatically after you configured your `config.i18n_dir` in `config/initializers/react_on_rails.rb`.
-
-  ```ruby
-  # Replace the following line to the location where you keep translation.js & default.js.
-  config.i18n_dir = Rails.root.join("PATH_TO", "YOUR_JS_I18N_FOLDER")
-  ```
-
-  Optionally you can also set `config.i18n_yml_dir` if you do not what to use all the locale files from rails.
-  ```ruby
-  # Replace the following line to the location where you keep your client i18n yml files
-  # By default(without this option), all yaml files from Rails.root.join("config", "locales") and installed gems are loaded
-  config.i18n_yml_dir = Rails.root.join("PATH_TO", "YOUR_YAML_I18N_FOLDER")
-  ```
-
-  `translations.js`: All your locales in json format.
-  `default.js`: Default settings in json format.
-
-3. Add `translations.js` and `default.js` to your `.gitignore` and `.eslintignore`.
-
-4. Javascript locale files must be generated before `yarn build`.
-
-  Once you setup `config.i18n_dir` as in the previous step, react_on_rails will automatically do this for testing (if using the `ReactOnRails::TestHelper.configure_rspec_to_compile_assets` and for production deployments if using the [default precompile rake hook](../additional-reading/heroku-deployment.md). For development, you should adjust your startup scripts (Procfiles) so that they run **`bundle exec rake react_on_rails:locale`** before running any webpack watch process (`yarn run build:development`). You may need to configure your CI to  run **`bundle exec rake react_on_rails:locale`** before any webpack process if you are not using the React on Rails test helper. Note, if you are try to lint before running tests, and you are depending on the test helper to build your locales, your linting will fail because the translations won't be built yet. The fix is either to 1) run the rake task to build the translations before running the lint command or 2) to run the tests first.
-
-5. In React, you need to initialize `react-intl`, and set parameters for it.
-
-  ```js
-  ...
-  import { addLocaleData } from 'react-intl';
-  import en from 'react-intl/locale-data/en';
-  import de from 'react-intl/locale-data/de';
-  import { translations } from 'path_to/i18n/translations';
-  import { defaultLocale } from 'path_to/i18n/default';
-  ...
-  // Initizalize all locales for react-intl.
-  addLocaleData([...en, ...de]);
-  ...
-  // set locale and messages for IntlProvider.
-  const locale = method_to_get_current_locale() || defaultLocale;
-  const messages = translations[locale];
-  ...
-  return (
-    <IntlProvider locale={locale} key={locale} messages={messages}>
-      <CommentScreen {...{ actions, data }} />
-    </IntlProvider>
-  )
-  ```
-  ```js
-  // In your component.
-  import { defaultMessages } from 'path_to/i18n/default';
-  ...
-  return (
-    { formatMessage(defaultMessages.yourLocaleKeyInCamelCase) }
-  )
-  ```
-  
-  # Notes
-  
-  * See [Support for Rails' i18n pluralization #1000](https://github.com/shakacode/react_on_rails/issues/1000) for a discussion of issues around pluralization.

data/docs/tutorial.md

@@ -1,220 +0,0 @@
-# React on Rails Basic Tutorial
-
-This tutorial guides you through setting up a new or existing Rails app with **React on Rails**, demonstrating Rails + React + Redux + Server Rendering. It is updated to 10.0.2.
-
-After finishing this tutorial you will get an application that can do the following (live on Heroku):
-
-![example](https://cloud.githubusercontent.com/assets/371302/17368567/111cc722-596b-11e6-9b72-ac5967a60e42.gif)
-
-You can find here:
-* [Source code for this app in PR, using the --redux option](https://github.com/shakacode/react_on_rails-test-new-redux-generation/pull/17) and [for Heroku](https://github.com/shakacode/react_on_rails-test-new-redux-generation/pull/18).
-* [Live on Heroku](https://react-on-rails-redux-gen-8-0-0.herokuapp.com/)
-
-By the time you read this, the latest may have changed. Be sure to check the versions here:
-
-* https://rubygems.org/gems/react_on_rails
-* https://www.npmjs.com/package/react-on-rails
-
-_Note: some of the screen images below show the "npm" command. react_on_rails 6.6.0 and greater uses `yarn`._
-
-## Setting up the environment
-
-Trying out **React on Rails** is super easy, so long as you have the basic prerequisites. This includes the basics for Rails 5.x and node version 6+. I recommend `rvm` and `nvm` to install Ruby and Node, and [brew](https://brew.sh/) to install [yarn](https://yarnpkg.com/en/docs/install#mac-tab). Rails can be installed as an ordinary gem.
-
-```
-nvm install node                # download and install latest stable Node
-nvm alias default node          # make it default version
-nvm list                        # check
-
-brew install yarn               # you can use other installer if desired
-
-rvm install 2.4.1               # download and install latest stable Ruby (update to exact version)
-rvm use 2.4.1 --default         # use it and make it default
-rvm list                        # check
-
-gem install rails               # download and install latest stable Rails
-gem install foreman             # download and install Foreman
-```
-
-Then we need to create a fresh Rails application with webpacker react support as following.
-
-First be sure to run `rails -v` and check you are using Rails 5.1.3 or above. If you are using an older version of Rails, you'll need to install webpacker with react per the instructions [here](https://github.com/rails/webpacker).
-
-```
-cd <directory where you want to create your new Rails app>
-
-# any name you like for the rails app
-rails new test-react-on-rails --webpack=react 
-
-cd test-react-on-rails
-```
-
-Note: if you are installing React On Rails in an existing app or an app that uses Rails pre 5.1.3, you will need to run these two commands as well:
-
-```
-bundle exec rails webpacker:install
-bundle exec rails webpacker:install:react
-```
-
-Add the **React On Rails** gem to your Gemfile:
-
-```
-gem 'react_on_rails', '10.0.2'         # prefer exact gem version to match npm version
-```
-
-Note: Latest released React On Rails version is considered stable. Please use the latest version to ensure you get all the security patches and the best support.
-
-Run `bundle` and commit the git repository (or `rails generate` will not work properly)
-
-
-```
-bundle
-
-# Here are git commands to make a new git repo and commit everything.
-# Newer versions of Rails create the git repo by default.
-git add -A
-git commit -m "Initial commit"
-```
-
-Install React on Rails: `rails generate react_on_rails:install` or `rails generate react_on_rails:install --redux`. You need to first git commit your files before running the generator, or else it will generate an error.
-
-```
-rails generate react_on_rails:install
-bundle && yarn
-```
-
-and then run server with
-
-```
-foreman start -f Procfile.dev
-```
-
-Visit http://localhost:3000/hello_world and see your **React On Rails** app running!
-Note, foreman defaults to PORT 5000 unless you set the value of PORT in your environment or in the Procfile.
-
-### Custom IP & PORT setup (Cloud9 example)
-
-In case you are running some custom setup with different IP or PORT you should also edit Procfile.dev. For example to be able to run on free Cloud9 IDE we are putting IP 0.0.0.0 and PORT 8080. The default generated file `Procfile.dev` uses `-p 3000`.
-
-``` Procfile.dev
-web: rails s -p 8080 -b 0.0.0.0
-```
-
-Then visit https://your-shared-addr.c9users.io:8080/hello_world 
-
-
-## RubyMine
-
-It's super important to exclude certain directories from RubyMine or else it will slow to a crawl as it tries to parse all the npm files.
-
-* Generated files, per the settings in your `config/webpacker.yml`, which default to `public/packs` and `public/packs-test`
-* `node_modules`
-
-## Deploying to Heroku
-
-### Create Your Heroku App
-*Assuming you can login to heroku.com and have logged into to your shell for heroku.*
-
-1. Visit https://dashboard.heroku.com/new and create an app, say named `my-name-react-on-rails`:
-
-![06](https://cloud.githubusercontent.com/assets/20628911/17465014/1f29bf3c-5cf4-11e6-869f-4215987ae854.png)
-
-Run this command that looks like this from your new heroku app
-
-    heroku git:remote -a my-name-react-on-rails
-
-Set heroku to use multiple buildpacks:
-
-    heroku buildpacks:set heroku/ruby
-    heroku buildpacks:add --index 1 heroku/nodejs
-
-
-### Swap out sqlite for postgres by doing the following:
-
-1. Delete the line with `sqlite` and replace it with:
-
-```ruby
-   gem 'pg'
-```
-
-![07](https://cloud.githubusercontent.com/assets/20628911/17465015/1f2f4042-5cf4-11e6-8287-2fb077550809.png)
-
-
-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
-```
-
-Then you need to setup postgres so you can run locally:
-
-```
-bundle
-rake db:setup
-rake db:migrate
-```
-
-![08](https://cloud.githubusercontent.com/assets/20628911/17465016/1f3559f0-5cf4-11e6-8ab4-c5572e4644a5.png)
-
-I'd recommend adding this line to the top of your `routes.rb`. That way, your root page will go to the Hello World page for React On Rails.
-
-```ruby
-root "hello_world#index"
-```
-
-![09](https://cloud.githubusercontent.com/assets/20628911/17465018/1f3b685e-5cf4-11e6-93f8-105fc48517d0.png)
-
-Next, configure your app for Puma, per the [instructions on Heroku](https://devcenter.heroku.com/articles/deploying-rails-applications-with-the-puma-web-server).
-
-`Procfile`
-```
-web: bundle exec puma -C config/puma.rb
-```
-
-`config/puma.rb`
-```rb
-workers Integer(ENV['WEB_CONCURRENCY'] || 2)
-threads_count = Integer(ENV['RAILS_MAX_THREADS'] || 5)
-threads threads_count, threads_count
-
-preload_app!
-
-rackup      DefaultRackup
-port        ENV['PORT']     || 3000
-environment ENV['RACK_ENV'] || 'development'
-
-on_worker_boot do
-  # Worker specific setup for Rails 4.1+
-  # See: https://devcenter.heroku.com/articles/deploying-rails-applications-with-the-puma-web-server#on-worker-boot
-  ActiveRecord::Base.establish_connection
-end
-```
-
-Then after all changes are done don't forget to commit them with git and finally you can push your app to Heroku!
-
-```
-git add -A
-git commit -m "Latest changes"
-git push heroku master
-```
-
-Feedback is greatly appreciated! As are stars on github! If you want personalized help, don't hesitate to get in touch with us at [contact@shakacode.com](mailto:contact@shakacode.com).

data/lib/generators/react_on_rails/templates/base/base/Procfile.dev-server

@@ -1,12 +0,0 @@
-# You can run these commands in separate shells instead of using foreman
-web: rails s -p 3000
-
-# Next line runs the webpack-dev-server
-# You can edit config/webpacker.yml to set HMR to true to see hot reloading.
-# Note, hot and live reloading don't work with the default generator setup on top of
-# the rails/webpacker Webpack config with server rendering.
-# If you have server rendering enabled, modify the call to bin/webpack-dev-server line
-# so you add `--inline=false` and then CSS is not inlined.
-# Otherwise, you will have an error. If you want HMR and Server Rendering, see
-# the example in the https://github.com/shakacode/react-webpack-rails-tutorial
-client: sh -c 'rm -rf public/packs/* || true && bundle exec rake react_on_rails:locale && bin/webpack-dev-server'

data/lib/react_on_rails/assets_precompile.rb

@@ -1,150 +0,0 @@
-# frozen_string_literal: true
-
-module ReactOnRails
-  class AssetsPrecompile
-    class SymlinkTargetDoesNotExistException < StandardError
-    end
-
-    # Used by the rake task
-    def default_asset_path
-      dir = File.join(Rails.configuration.paths["public"].first,
-                      Rails.configuration.assets.prefix)
-      Pathname.new(dir)
-    end
-
-    # assets_path should be a Pathname object
-    def initialize(assets_path: nil,
-                   symlink_non_digested_assets_regex: nil,
-                   generated_assets_dir: nil)
-      @assets_path = ReactOnRails::Utils.truthy_presence(assets_path) || default_asset_path
-      @symlink_non_digested_assets_regex =
-        ReactOnRails::Utils.truthy_presence(symlink_non_digested_assets_regex) ||
-        ReactOnRails.configuration.symlink_non_digested_assets_regex
-      @generated_assets_dir = ReactOnRails::Utils.truthy_presence(generated_assets_dir) ||
-                              ReactOnRails.configuration.generated_assets_dir
-    end
-
-    # target and symlink are relative to the assets directory
-    def symlink_file(target, symlink)
-      target_path = @assets_path.join(target)
-      symlink_path = @assets_path.join(symlink)
-
-      target_exists = File.exist?(target_path)
-      raise SymlinkTargetDoesNotExistException, "Target Path was: #{target_path}" unless target_exists
-
-      if symlink_and_points_to_existing_file?(symlink_path)
-        puts "React On Rails: Digested version of #{symlink} already exists indicating #{target} did not change."
-        return
-      end
-
-      if file_or_symlink_exists_at_path?(symlink_path)
-        puts "React On Rails: Removing existing invalid symlink or file #{symlink_path}"
-        FileUtils.remove_file(symlink_path, true)
-      end
-
-      # Might be like:
-      # "images/5cf5db49df178f9357603f945752a1ef.png":
-      # "images/5cf5db49df178f9357603f945752a1ef-033650e1d6193b70d59bb60e773f47b6d9aefdd56abc7cc.png"
-      # need to cd to directory and then symlink
-      target_sub_path, _divider, target_filename = target.rpartition("/")
-      _symlink_sub_path, _divider, symlink_filename = symlink.rpartition("/")
-      dest_path = File.join(@assets_path, target_sub_path)
-
-      puts "React On Rails: Symlinking \"#{target}\" to \"#{symlink}\""
-      FileUtils.chdir(dest_path) do
-        File.symlink(target_filename, symlink_filename)
-      end
-    end
-
-    def symlink_non_digested_assets
-      # digest ==> means that the file has a unique sha so the browser will load a new copy.
-      # Webpack's CSS extract-text-plugin copies digested asset files over to directory where we put
-      # we deploy the webpack compiled JS file. Since Rails will deploy the image files in this
-      # directory with a digest, then the files are essentially "double-digested" and the CSS
-      # references from webpack's CSS would be invalid. The fix is to symlink the double-digested
-      # file back to the original digested name, and make a similar symlink for the gz version.
-      return unless @symlink_non_digested_assets_regex
-      manifest_glob = Dir.glob(@assets_path.join(".sprockets-manifest-*.json")) +
-                      Dir.glob(@assets_path.join("manifest-*.json")) +
-                      Dir.glob(@assets_path.join("manifest.yml"))
-      if manifest_glob.empty?
-        puts "Warning: React On Rails: expected to find .sprockets-manifest-*.json, manifest-*.json "\
-                 "or manifest.yml at #{@assets_path}, but found none. Canceling symlinking tasks."
-        return -1
-      end
-      manifest_path = take_most_recent_manifest_path(manifest_glob)
-      manifest_file = File.new(manifest_path)
-      manifest_data = if File.extname(manifest_file) == ".json"
-                        manifest_file_data = File.read(manifest_path)
-                        JSON.parse(manifest_file_data)["assets"]
-                      else
-                        YAML.safe_load(manifest_file)
-                      end
-
-      # We realize that we're copying other Rails assets that match the regexp, but this just
-      # means that we'd be exposing the original, undigested names.
-      manifest_data.each do |original_filename, rails_digested_filename|
-        # TODO: we should remove any original_filename that is NOT in the webpack deploy folder.
-        next unless original_filename =~ @symlink_non_digested_assets_regex
-        # We're symlinking from the digested filename back to the original filename which has
-        # already been symlinked by Webpack
-        symlink_file(rails_digested_filename, original_filename)
-
-        # We want the gz ones as well if they exist
-        if File.exist?(@assets_path.join("#{rails_digested_filename}.gz"))
-          symlink_file("#{rails_digested_filename}.gz", "#{original_filename}.gz")
-        end
-      end
-    end
-
-    def delete_broken_symlinks
-      Dir.glob(@assets_path.join("*")).each do |filename|
-        next unless File.lstat(filename).symlink?
-        begin
-          target = File.readlink(filename)
-        rescue StandardError
-          puts "React on Rails: Warning: your platform doesn't support File::readlink method." \
-               "Skipping broken link check."
-          break
-        end
-        path = Pathname.new(File.dirname(filename))
-        target_path = path.join(target)
-        unless File.exist?(target_path)
-          puts "React on Rails: Deleting broken link: #{filename}"
-          File.delete(filename)
-        end
-      end
-    end
-
-    def clobber
-      dir = Rails.root.join(@generated_assets_dir)
-      if dir.present? && File.directory?(dir)
-        puts "Deleting files in directory #{dir}"
-        FileUtils.rm_r(Dir.glob(Rails.root.join("#{@generated_assets_dir}/*")))
-      else
-        puts "Could not find generated_assets_dir #{dir} defined in react_on_rails initializer: "
-      end
-    end
-
-    private
-
-    def take_most_recent_manifest_path(manifest_glob)
-      manifest_glob.max_by { |name| File.mtime(name) }
-    end
-
-    def symlink_and_points_to_existing_file?(symlink_path)
-      # File.exist?(symlink_path) will check the file the sym is pointing to is existing
-      # File.lstat(symlink_path).symlink? confirms that this is a symlink
-      File.exist?(symlink_path) && File.lstat(symlink_path).symlink?
-    end
-
-    def file_or_symlink_exists_at_path?(path)
-      # We use lstat and not stat, we we don't want to visit the file that the symlink maybe
-      # pointing to. We can't use File.exist?, as that would check the file pointed at by the symlink.
-      File.lstat(path)
-      true
-    rescue StandardError
-      false
-    end
-  end
-end