cssbundling-rails 0.2.4 → 0.2.5

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 2327f824df0a60b8114f3834b29a7d20b005bb2645d98083772ca1fa622b8d8c
-  data.tar.gz: 1bf817470b20cbe122c67a3b502ebdea182a7c526073b0059f05b6c262af5203
+  metadata.gz: 17fa9455564f88e8e8ea4034a948bdcd641be3108ac6e9eb8244a2515877971e
+  data.tar.gz: 87b5fa05bff61fb65e70ada26275be1e807734ad68af54c345dffe9aa6c893fc
 SHA512:
-  metadata.gz: c01ddba4ef303e6a03f59480709003950deeaad59238d7afd974009fa18914e872be4aa19ddd2ba7c976124bc06aad5f3fc6016e98672b4162feed7016e06826
-  data.tar.gz: cd093d2443110526f411698cbbabab0e222e3c81221f6a95139a04ef8bd0197d70de9a27aa8081ae3010e33888e1e5207c2bd693fa7a4bc1b70c432bd6af66b3
+  metadata.gz: 13e364e934c7ef424a5ad2d5f62c593c689185fa333fd283b53173183511bcad112177ec5a46a297f2e8fda06ce3d21616eb70e57df8b245bd5299586494a5d5
+  data.tar.gz: b03e89051ca7dfd506b4a8a861ea1b81d9979974e84421e62b5a987a61a2b4f60ec0d90fdfee3eefca1c308d022a06040e5604402dbcb6ae0bdc985c55da7789

data/README.md

@@ -2,7 +2,9 @@
 
 Use [Tailwind CSS](https://tailwindcss.com), [Bootstrap](https://getbootstrap.com/), [Bulma](https://bulma.io/), [PostCSS](https://postcss.org), or [Dart Sass](https://sass-lang.com/) to bundle and process your CSS, then deliver it via the asset pipeline in Rails. This gem provides installers to get you going with the bundler of your choice in a new Rails application, and a convention to use `app/assets/builds` to hold your bundled output as artifacts that are not checked into source control (the installer adds this directory to `.gitignore` by default).
 
-You develop using this approach by running the bundler in watch mode in a terminal with `yarn build:css --watch` (and your Rails server in another, if you're not using something like [puma-dev](https://github.com/puma/puma-dev)). Whenever the bundler detects changes to any of the stylesheet files in your project, it'll bundle `app/assets/stylesheets/application.[bundler].css` into `app/assets/builds/application.css`. This build output takes over from the regular asset pipeline default file. So you continue to refer to the build output in your layout using the standard asset pipeline approach with `<%= stylesheet_link_tag "application" %>`.
+You develop using this approach by running the bundler in watch mode in a terminal with `yarn build:css --watch` (and your Rails server in another, if you're not using something like [puma-dev](https://github.com/puma/puma-dev)). You can also use `./bin/dev`, which will start both the Rails server and the CSS build watcher (along with a JS build watcher, if you're also using `jsbundling-rails`).
+
+Whenever the bundler detects changes to any of the stylesheet files in your project, it'll bundle `app/assets/stylesheets/application.[bundler].css` into `app/assets/builds/application.css`. This build output takes over from the regular asset pipeline default file. So you continue to refer to the build output in your layout using the standard asset pipeline approach with `<%= stylesheet_link_tag "application" %>`.
 
 When you deploy your application to production, the `css:build` task attaches to the `assets:precompile` task to ensure that all your package dependencies from `package.json` have been installed via yarn, and then runs `yarn build:css` to process your stylesheet entrypoint, as it would in development. This output is then picked up by the asset pipeline, digested, and copied into public/assets, as any other asset pipeline file.
 
@@ -26,6 +28,16 @@ You must already have node and yarn installed on your system. You will also need
 Or, in Rails 7+, you can preconfigure your new application to use a specific bundler with `rails new myapp --css [tailwind|bootstrap|bulma|postcss|sass]`.
 
 
+## FAQ
+
+### How do I import relative CSS files with Tailwind?
+
+If you want to use `@import` statements as part of your Tailwind application.js file, you need to [configure Tailwind to use `postcss` and then `postcss-import`](https://tailwindcss.com/docs/using-with-preprocessors#build-time-imports). But you should also consider simply referring to your other CSS files directly, instead of bundling them all into one big file. It's better for caching, and it's simpler to setup. You can refer to other CSS files by expanding the `stylesheet_link_tag` in `application.html.erb` like so: `<%= stylesheet_link_tag "application", "other", "styles", "data-turbo-track": "reload" %>`.
+
+### How do I avoid SassC::SyntaxError exceptions on existing projects?
+
+Some CSS packages use new CSS features that are not supported by the default SassC rails integration that previous versions of Rails used. If you hit such an incompatibility, it'll likely be in the form of a `SassC::SyntaxError` when running `assets:precompile`. The fix is to `bundle remove sass-rails` (or `sassc-rails`, if you were using that).
+
 ## License
 
 CSS Bundling for Rails is released under the [MIT License](https://opensource.org/licenses/MIT).

data/lib/cssbundling/version.rb

@@ -1,3 +1,3 @@
 module Cssbundling
-  VERSION = "0.2.4"
+  VERSION = "0.2.5"
 end

data/lib/install/bootstrap/install.rb

@@ -14,7 +14,7 @@ say "Add build:css script"
 build_script = "sass ./app/assets/stylesheets/application.bootstrap.scss ./app/assets/builds/application.css --no-source-map --load-path=node_modules"
 
 if (`npx -v`.to_f < 7.1 rescue "Missing")
-  say %(Add "scripts": { "build:css": "#{build_script}" to your package.json), :green
+  say %(Add "scripts": { "build:css": "#{build_script}" } to your package.json), :green
 else
   run %(npm set-script build:css "#{build_script}")
 end

data/lib/install/bulma/install.rb

@@ -7,7 +7,7 @@ say "Add build:css script"
 build_script = "sass ./app/assets/stylesheets/application.bulma.scss ./app/assets/builds/application.css --no-source-map --load-path=node_modules"
 
 if (`npx -v`.to_f < 7.1 rescue "Missing")
-  say %(Add "scripts": { "build:css": "#{build_script}" to your package.json), :green
+  say %(Add "scripts": { "build:css": "#{build_script}" } to your package.json), :green
 else
   run %(npm set-script build:css "#{build_script}")
 end

data/lib/install/dev

@@ -1,3 +1,9 @@
 #!/usr/bin/env bash
 
+if ! command -v foreman &> /dev/null
+then
+  echo "Installing foreman..."
+  gem install foreman
+fi
+
 foreman start -f Procfile.dev

data/lib/install/postcss/install.rb

@@ -7,7 +7,7 @@ say "Add build:css script"
 build_script = "postcss ./app/assets/stylesheets/application.postcss.css -o ./app/assets/builds/application.css"
 
 if (`npx -v`.to_f < 7.1 rescue "Missing")
-  say %(Add "scripts": { "build:css": "#{build_script}" to your package.json), :green
+  say %(Add "scripts": { "build:css": "#{build_script}" } to your package.json), :green
 else
   run %(npm set-script build:css "#{build_script}")
 end

data/lib/install/sass/install.rb

@@ -6,7 +6,7 @@ say "Add build:css script"
 build_script = "sass ./app/assets/stylesheets/application.sass.scss ./app/assets/builds/application.css --no-source-map --load-path=node_modules"
 
 if (`npx -v`.to_f < 7.1 rescue "Missing")
-  say %(Add "scripts": { "build:css": "#{build_script}" to your package.json), :green
+  say %(Add "scripts": { "build:css": "#{build_script}" } to your package.json), :green
 else
   run %(npm set-script build:css "#{build_script}")
 end

data/lib/install/tailwind/install.rb

@@ -7,7 +7,7 @@ say "Add build:css script"
 build_script = "tailwindcss -i ./app/assets/stylesheets/application.tailwind.css -o ./app/assets/builds/application.css"
 
 if (`npx -v`.to_f < 7.1 rescue "Missing")
-  say %(Add "scripts": { "build:css": "#{build_script}" to your package.json), :green
+  say %(Add "scripts": { "build:css": "#{build_script}" } to your package.json), :green
 else
   run %(npm set-script build:css "#{build_script}")
 end

data/lib/tasks/cssbundling/build.rake

@@ -1,7 +1,7 @@
 namespace :css do
   desc "Build your CSS bundle"
-  task :build do
-    unless system "yarn install && yarn build:css"
+  task build: [ "yarn:install" ] do
+    unless system "yarn build:css"
       raise "cssbundling-rails: Command css:build failed, ensure yarn is installed and `yarn build:css` runs without errors"
     end
   end

data/lib/tasks/cssbundling/clean.rake

@@ -0,0 +1,8 @@
+namespace :css do
+  desc "Remove CSS builds"
+  task :clean do
+    rm_rf Dir["app/assets/builds/[^.]*.css"], verbose: false
+  end
+end
+
+Rake::Task["assets:clean"].enhance(["css:clean"])

metadata

@@ -1,15 +1,15 @@
 --- !ruby/object:Gem::Specification
 name: cssbundling-rails
 version: !ruby/object:Gem::Version
-  version: 0.2.4
+  version: 0.2.5
 platform: ruby
 authors:
 - David Heinemeier Hansson
 - Dom Christie
-autorequire: 
+autorequire:
 bindir: bin
 cert_chain: []
-date: 2021-09-29 00:00:00.000000000 Z
+date: 2021-11-15 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: railties
@@ -25,7 +25,7 @@ dependencies:
     - - ">="
       - !ruby/object:Gem::Version
         version: 6.0.0
-description: 
+description:
 email: david@loudthinking.com
 executables: []
 extensions: []
@@ -54,12 +54,13 @@ files:
 - lib/install/tailwind/package.json
 - lib/install/tailwind/tailwind.config.js
 - lib/tasks/cssbundling/build.rake
+- lib/tasks/cssbundling/clean.rake
 - lib/tasks/cssbundling/install.rake
 homepage: https://github.com/rails/cssbundling-rails
 licenses:
 - MIT
 metadata: {}
-post_install_message: 
+post_install_message:
 rdoc_options: []
 require_paths:
 - lib
@@ -74,8 +75,8 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.1.4
-signing_key: 
+rubygems_version: 3.2.22
+signing_key:
 specification_version: 4
 summary: Bundle and process CSS with Tailwind, Bootstrap, PostCSS, Sass in Rails via
   Node.js.