cssbundling-rails 0.1.0 → 0.1.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 157a239ed259b5466360204b02cbe2b260f6bd1fe9357e7a8d190f24658f21e4
-  data.tar.gz: beaa568932183609d735427a7cb32f3bc8a54c468296eeb86bd09f1e101b9c76
+  metadata.gz: d009b77062edc08fa7e499ebe915ca706a3c8245e1437f78e5f5fa7bb2829426
+  data.tar.gz: 7936295528cee5b579b2a0ff6c2b928dd3626bfbfd4e056f03819ff71fa3dd46
 SHA512:
-  metadata.gz: 50acd8f5b93b5f7be810b2fed9a563fc1a5526362985206865d3478e01b1f555e97018793c129f62835552475a929a22579eef2722e6eb0b77787ff99901e78e
-  data.tar.gz: b50e046ba8cef422ee3d7d404696e66dae05c341d1f7342f98d92d748cece0b81e9c6198dd096e89700334dbc49605b0c970de1c20b0c443d8178e5ec90ab2a9
+  metadata.gz: 1e5651b29b1fc938881fcc0dfa05db4bebb8333fab87febfdb5036dd5915eff9d2e24dfa5cbfc30062e76930598c018f77fe67af2d349f078b833da38657ead4
+  data.tar.gz: 8646a47e848a271ccf001768e1bdd2b58076096b6dabe29031a4a1464d448b37db4803dd06eef98268710e6a86ce7d6ab088d520f11559c087a8664157bd48a6

data/README.md

@@ -1,6 +1,6 @@
 # CSS Bundling for Rails
 
-Use [Tailwind CSS](https://tailwindcss.com), [PostCSS](https://postcss.org), or [Dart Sass](https://sass-lang.com/) to bundle and process your JavaScript, 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).
+Use [Tailwind CSS](https://tailwindcss.com), [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_include_tag "application" %>`.
 

data/lib/cssbundling/version.rb

@@ -1,3 +1,3 @@
 module Cssbundling
-  VERSION = "0.1.0"
+  VERSION = "0.1.1"
 end

data/lib/install/tailwind/package.json

@@ -2,6 +2,6 @@
   "name": "app",
   "private": "true",
   "scripts": {
-    "build:css": "tailwindcss -i ./app/assets/stylesheets/application.tw.css -o ./app/assets/builds/application.css"
+    "build:css": "tailwindcss -i ./app/assets/stylesheets/application.tailwind.css -o ./app/assets/builds/application.css"
   }
 }

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: cssbundling-rails
 version: !ruby/object:Gem::Version
-  version: 0.1.0
+  version: 0.1.1
 platform: ruby
 authors:
 - David Heinemeier Hansson