rails-assets.org is down, and bundler can't install anything while a
gem's source is unreachable, so CI fails for every branch before a
single spec runs. The one gem from there was
rails-assets-leaflet.markercluster; it now comes from npm, where the
React bundle's packages already come from, and node_modules is already
on the asset path. CI and Heroku both install npm packages.
That gem also brought in rails-assets-leaflet, a second copy of Leaflet
(1.5.1), which shadowed the leaflet-rails gem the Gemfile asks for. With
it gone, the maps get Leaflet 1.9.4 from leaflet-rails, as intended, so
the cluster plugin is its current release, 1.5.3, which supports it.
npm's peer dependency warning for leaflet is expected: Leaflet comes
from the gem, loaded before the plugin.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The CSS came from the material-sass gem, a Bootstrap 4 based Material Design
skin, while the JavaScript already came from the bootstrap gem (Bootstrap 5).
Import the bootstrap gem's SCSS instead and drop material-sass and its
'material' script.
Bootstrap 5 reads its settings from variables defined before it is imported,
so _variables.scss now sets the theme colours (primary/success green,
secondary blue, and so on), body colours, font and the site's own breakpoints
(lg 1200px, xl 1800px) in Bootstrap's terms, in place of the Material colour
maps. media-breakpoint-down(xs) is media-breakpoint-down(sm) in Bootstrap 5.
Class names from Bootstrap 3 and 4 that no longer exist are renamed in the
commits that follow.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
* Upgrade boostrap
* Remove deprecated bootstrap toggles
* Migrate other details
* Avoid accidentally including bootstrap twice
* Avoid accidentally including bootstrap twice
* Avoid accidentally including bootstrap twice
* Fix spec
* Fix spec, where the size of the screen has gone to a partial breakpoint/you can't click on your own name in tablet view
* Fix spec
* Cleanup
* Cleanup
