rails 5.2 启动警告 warning: previous definition of VERSION was here和bootsnap

bootsnap依赖问题

 You should add gem 'bootsnap' to your gemfile to install it or remove the line require 'bootsnap/setup' in config/boot.rb

or

 using rails new myapp --skip-bootsnap

 If the app doesn’t contain the bootsnap gem already then we will need to add it manually since rails app:update task adds the bootsnap/setup line to boot.rb regardless of its presence in the Gemfile.

or

 https://blog.bigbinary.com/2018/01/01/rails-5-2-adds-bootsnap-to-the-app-to-speed-up-boot-time.html

warning: previous definition of VERSION was here

 https://github.com/ruby/fileutils/issues/22

 Ran into this, and the solution here works: https://stackoverflow.com/questions/51334732/rails-5-2-0-with-ruby-2-5-1-console-warning-already-initialized-constant

 I understand 1.0. stays installed as the default, 1.1. being installed too. Hence the issue.

 When installed automatically, I get the warnings. Following command shows (new rails app, 2.5.) :

 gem list | grep fileutils
 fileutils (1.1., default: 1.0.)

 Then doing:

 gem uninstall fileutils
 gem update fileutils --default

 makes the warnings disappear. And btw, it shows:

 gem list | grep fileutils
 fileutils (default: 1.1., default: 1.0.)

 Hope it will help fixing this annoyance. Sorry I cannot be of more help, not really a wizard with those versioning topics!