propshaft 0.1.3 → 0.1.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 263dfd4ede27b9d76a03f09280a5db8ec28f510833dbe9942de5a210af92e26a
-  data.tar.gz: e9dc23f7db673a8b3d3a0680e9a00836150ba058e62536c53ae3c09a2b0c6de6
+  metadata.gz: f5ac96be7b15334f58662f5033d02375a23050328d28aca71058777cd1778ba6
+  data.tar.gz: bb4c8a1c289ce56c380da154c0174d6bef08a988cd7a4e53fe0193b05f62b092
 SHA512:
-  metadata.gz: c37707a704e9a65c1e98c90c486a691fdc164c113580a94ea03442bc08ba179dc57351c176671cb17dc21eda7375da066cc4611799622f85a61fe0e5be3c977a
-  data.tar.gz: a84ac7c0da1a2e166c65bdb99098f4692a993d147d503d7b143fa06127eb91d7055033e0922eb2927f5ab3792f494fb68fab9d2386460d1cd8988d1976a94036
+  metadata.gz: e082b706b8d3e1733805697fdb3f3520ba977531533ec1da6078277cf9e7d59c8a2cf79464653ec8d058ae98b40db10cf372bc3e260ea56194aa062cf7f501b0
+  data.tar.gz: eb18c451c949637476e936afcf88a656dad3f0ae7217d326fbb117390bfc3de7ae83e5fe71f66848739300d7d841ba113abf6704cb6c3e95ddae47d9ca674547

data/README.md

@@ -1,8 +1,8 @@
 # Propshaft
 
-Propshaft is an asset pipeline library for Rails. It's built for era where bundling assets to save on HTTP connections is no longer urgent, where JavaScript and CSS is either compiled by dedicated Node.js bundlers or served directly to the browsers, and where increases in bandwidth has made the need for minification less pressing. These factors allow for a dramatically simpler and faster asset pipeline compared to previous options, like Sprockets.
+Propshaft is an asset pipeline library for Rails. It's built for an era where bundling assets to save on HTTP connections is no longer urgent, where JavaScript and CSS are either compiled by dedicated Node.js bundlers or served directly to the browsers, and where increases in bandwidth have made the need for minification less pressing. These factors allow for a dramatically simpler and faster asset pipeline compared to previous options, like Sprockets.
 
-So that's what Propshaft doesn't do. Here's what it actually does provide:
+So that's what Propshaft doesn't do. Here's what it does provide:
 
 1. **Configurable load path**: You can register directories from multiple places in your app and gems, and reference assets from all of these paths as though they were one.
 1. **Digest stamping**: All assets in the load path will be copied (or compiled) in a precompilation step for production that also stamps all of them with a digest hash, so you can use long-expiry cache headers for better performance. The digested assets can be referred to through their logical path because the processing leaves a manifest file that provides a way to translate.
@@ -17,16 +17,16 @@ With Rails 7+, you can start a new application with propshaft using `rails new m
 
 ## Usage
 
-Propshaft makes all the assets from all the paths its been configured with through `config.assets.paths` available for serving and will copy all of them into `public/assets` when precompiling. This is unlike Sprockets, which did not copy over assets that hadn't been explicitly included in one of bundled assets.
+Propshaft makes all the assets from all the paths it's been configured with through `config.assets.paths` available for serving and will copy all of them into `public/assets` when precompiling. This is unlike Sprockets, which did not copy over assets that hadn't been explicitly included in one of the bundled assets.
 
-These assets can be referenced through their logical path using the normal helpers like `asset_path`, `image_tag`, `javascript_include_tag`, and all the other asset helper tags. These logical references are automatically converted into digest-aware paths in production when `assets:precompile` has been run (through a json mapping file found in `public/assets/.manifest.json`).
+These assets can be referenced through their logical path using the normal helpers like `asset_path`, `image_tag`, `javascript_include_tag`, and all the other asset helper tags. These logical references are automatically converted into digest-aware paths in production when `assets:precompile` has been run (through a JSON mapping file found in `public/assets/.manifest.json`).
 
 Additionally, Propshaft ships with a CSS function called `asset-path("image.svg")` that'll be compiled into `url("/assets/image-f2e1ec14d6856e1958083094170ca6119c529a73.svg")` when doing `assets:precompile`. This function is applied to all `.css` files.
 
 
 ## Migrating from Sprockets
 
-Propshaft does a lot less than Sprockets, by design, so it might well be a fair bit of work to migrate, if it's even desirable. This is particularly true if you rely on Sprockets to provide any form of transpiling, like CoffeeScript or Sass, or if you rely on any gems that do. You'll need to either stop transpiling or use a Node-based transpiler, like those in `jsbundling-rails` and `cssbundling-rails`.
+Propshaft does a lot less than Sprockets, by design, so it might well be a fair bit of work to migrate if it's even desirable. This is particularly true if you rely on Sprockets to provide any form of transpiling, like CoffeeScript or Sass, or if you rely on any gems that do. You'll need to either stop transpiling or use a Node-based transpiler, like those in `jsbundling-rails` and `cssbundling-rails`.
 
 On the other hand, if you're already bundling JavaScript and CSS through a Node-based setup, then Propshaft is going to slot in easily. Since you don't need another tool to bundle or transpile. Just to digest and serve.
 

data/lib/propshaft/version.rb

@@ -1,3 +1,3 @@
 module Propshaft
-  VERSION = "0.1.3"
+  VERSION = "0.1.4"
 end

data/lib/propshaft.rb

@@ -1,3 +1,6 @@
+module Propshaft
+end
+
 require "propshaft/assembly"
 require "propshaft/helper"
 require "propshaft/railtie"

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: propshaft
 version: !ruby/object:Gem::Version
-  version: 0.1.3
+  version: 0.1.4
 platform: ruby
 authors:
 - David Heinemeier Hansson
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2021-09-21 00:00:00.000000000 Z
+date: 2021-09-22 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rails