As an extension for Matestack Ui Core, Matestack Ui Bootstrap ships all you need to build beautiful, reactive UIs in pure Ruby and smart CRUD components based on Bootstrap v5. Don't think about styling anymore and just create admin or application UIs faster than ever before!
Issue 25: Running npm install on dummy app fails to build
Changes
[x] Bumped @rails/xxx JS packages in dummy app to match their Rails gem counterparts.
[x] Added gcompat for nokogiri capabilities on M1 Macs.
Notes
@rails/webpacker@5.2.1 was the presumed culprit of this as per inspection of the package-lock.
Also noticed that the JS packages for the Rails gem counterparts were out-of-sync (Rails 7.x gems with rails@6.x JS package versions).
When running ./bin/webpack now, I noticed there's an issue that pops up listing:
DEPRECATION WARNING: $weight: Passing a number without unit % (100) is deprecated.
To preserve current behavior: $weight * 1%
More info: https://sass-lang.com/d/function-units
> @return mix(rgba($foreground, 1), $background, opacity($foreground) * 100);
Upon a bit of research, it seems it's an actual Sass/Bootstrap problem and should be addressed in Bootstrap v5.2.3, as mentioned here . Perhaps this should be an update taken care of an a separate issue (bumping the Bootstrap version. I don't know what the compatibility rules are when it regards to this and an open source project.). Have you seen this in any of your branches/projects? @jonasjabari I haven't seen it in any client projects come up using matestack-ui-bootstrap with webpacker or with importmap.
Issue 25: Running
npm installon dummy app fails to buildChanges
@rails/xxxJS packages in dummy app to match their Rails gem counterparts.gcompatfor nokogiri capabilities on M1 Macs.Notes
@rails/webpacker@5.2.1was the presumed culprit of this as per inspection of the package-lock. Also noticed that the JS packages for the Rails gem counterparts were out-of-sync (Rails 7.x gems withrails@6.xJS package versions).When running
./bin/webpacknow, I noticed there's an issue that pops up listing:Upon a bit of research, it seems it's an actual Sass/Bootstrap problem and should be addressed in Bootstrap v5.2.3, as mentioned here . Perhaps this should be an update taken care of an a separate issue (bumping the Bootstrap version. I don't know what the compatibility rules are when it regards to this and an open source project.). Have you seen this in any of your branches/projects? @jonasjabari I haven't seen it in any client projects come up using matestack-ui-bootstrap with webpacker or with importmap.