Markus Doits 87e9ae053d Only run yarn:install before assets:precompile if bin/yarn present ... Based on discussion in https://github.com/rails/rails/issues/40795, it looks like `yarn:install` is *always* run, even if the Rails project disabled javascript and there is no `bin/yarn`. Check for the existence of `bin/yarn` to decide if `yarn:install` should be run or not. The check for this is taken from `railties/lib/rails/app_updater.rb`, where it does the same: ```ruby options[:skip_javascript] = !File.exist?(Rails.root.join("bin", "yarn")) ```		2020-12-11 15:54:29 +01:00
..
engine.rake	Combine and deprecate rails db:structure:{dump,load} tasks into rails db:schema:{dump,load}	2020-08-03 19:08:41 +03:00
framework.rake	feat(rubocop): Add Style/RedundantRegexpEscape	2020-12-08 18:57:09 +00:00
log.rake	Enable Layout/EmptyLinesAroundBlockBody to reduce review cost in the future	2018-07-12 21:29:48 +09:00
middleware.rake	Adding frozen_string_literal pragma to Railties.	2017-08-14 19:08:09 +02:00
misc.rake	remove reference to global rails command and replace with bin/rails	2019-12-27 19:32:37 +00:00
restart.rake	Make restart and dev:cache tasks work when customizing pid file path	2017-08-21 05:44:11 +09:00
statistics.rake	Add support for stylesheets and ERB views to rails stats.	2020-11-10 09:40:18 -07:00
tmp.rake	Adding frozen_string_literal pragma to Railties.	2017-08-14 19:08:09 +02:00
yarn.rake	Only run yarn:install before assets:precompile if bin/yarn present	2020-12-11 15:54:29 +01:00
zeitwerk.rake	files -> directories in zeitwerk:check warning [skip ci]	2020-04-29 11:12:46 +02:00