jekyll_asset_pipeline 0.6.2 → 0.7.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: b726f7a64a403c4829e7afe69470938ab04ad8bb1fa87cbc72dc6f7a0f5871cb
-  data.tar.gz: 6fb6c82c5fa9b50f3b834e7f303b140ef9758d17ea1aa9182aa0bdb36856dbc0
+  metadata.gz: 34f1235420f955670222b56e026baa37efe0c7f6525048918616a78aa102c400
+  data.tar.gz: 8a2e180e4db7c48d11baeaa8d5b9a6111f22892ac02c3b34f184f6ee4e903a1d
 SHA512:
-  metadata.gz: c2b0347febf55d91ec28060603e8b8056f86eda6f89df1a58574bb5ade32046ac8ee00b44f0c9a71c4b08a2b779ebd4dd2899448d19dbd427f9b09e4e90e706f
-  data.tar.gz: 05e7d25c1b1697570416e929c898e44f8ecec05856f8305d98ecc2baafb895c2f840c8e7883de0940e53c533eafefe9bc8dcf7f4ce793f169aba892f12eec7e6
+  metadata.gz: 95472dfc679a1e5bb7f557f2cb1f24c98211900f7e1a3e714d71abe4e29236a97f7fddba00f620ffcd37df9b64401aeb5bcf3995f9213624e58ba958c7a05042
+  data.tar.gz: 7c2fddcecf364532a04fb2f8988478cc2be94d0c6c05f0e7abde2744ff01f2ac26abb1616b72eec26431d55d284fd94687f783b0020c0f90a254cc8c8a291d88

data/CHANGELOG.md

@@ -1,5 +1,36 @@
 # Changelog
 
+## 0.7.0 (2026-05-17)
+
+Project adopted and moved to https://github.com/janosrusiczki/jekyll-asset-pipeline.
+
+**Breaking changes**
+
+* Bundle filenames now use an MD5 hash of the compiled output content instead of
+  the pipeline parameters. On first build after upgrading, all existing bundle
+  filenames will change (one-time). Previously, the hash was derived from file
+  mtimes, which meant every CI build produced new filenames — `git checkout`
+  resets mtimes to the current time regardless of whether content changed. Now
+  the hash reflects actual content, so filenames are stable across CI builds and
+  local rebuilds alike. Non-manifest dependencies such as Sass `@use` partials
+  that affect output are also correctly reflected in the hash. [#55]
+
+**Improvements**
+
+* Log output is now aligned with Jekyll's column formatting (`Asset Pipeline:`
+  right-justified to column 20, matching `Generating...`, `Jekyll Feed:`, etc.)
+* Raised minimum Ruby version to 2.7.0 (aligns with Jekyll's CI matrix)
+* Updated CI from Travis to GitHub Actions (Ruby 2.7, 3.3, 3.4 matrix)
+* Switched coverage reporting from Coveralls to Codecov
+* Replaced `rake` 12 with 13 in dev dependencies
+
+**Documentation**
+
+* Modernized README: updated converter examples to `sass-embedded` (Dart Sass)
+  and `Open3`/`lessc` for LESS; replaced YUI Compressor example with Terser;
+  removed CoffeeScript and Octopress sections (both effectively abandoned)
+* Fixed all dead links, HTTP → HTTPS, and stale repo references
+
 ## 0.6.2 (2019-10-16)
 
 * Support Jekyll 4.0 [#53]

data/README.md

@@ -1,10 +1,10 @@
 # Jekyll Asset Pipeline
 
 [![Gem Version](https://img.shields.io/gem/v/jekyll_asset_pipeline.svg)](https://rubygems.org/gems/jekyll_asset_pipeline)
-[![Build Status](https://img.shields.io/travis/matthodan/jekyll-asset-pipeline.svg)](https://travis-ci.org/matthodan/jekyll-asset-pipeline)
-[![Coveralls Status](https://img.shields.io/coveralls/github/matthodan/jekyll-asset-pipeline/master.svg)](https://coveralls.io/r/matthodan/jekyll-asset-pipeline?branch=master)
+[![CI](https://github.com/janosrusiczki/jekyll-asset-pipeline/actions/workflows/ci.yml/badge.svg)](https://github.com/janosrusiczki/jekyll-asset-pipeline/actions/workflows/ci.yml)
+[![codecov](https://codecov.io/gh/janosrusiczki/jekyll-asset-pipeline/branch/main/graph/badge.svg)](https://codecov.io/gh/janosrusiczki/jekyll-asset-pipeline)
 
-[Jekyll Asset Pipeline](http://www.matthodan.com/2012/11/22/jekyll-asset-pipeline.html) is a powerful asset pipeline that automatically collects, converts and compresses / minifies your site's JavaScript and CSS assets when you compile your [Jekyll](http://jekyllrb.com/) site.
+Jekyll Asset Pipeline is a powerful asset pipeline that automatically collects, converts and compresses / minifies your site's JavaScript and CSS assets when you compile your [Jekyll](https://jekyllrb.com/) site.
 
 ## Table of Contents
 
@@ -12,16 +12,14 @@
 - [How It Works](#how-it-works)
 - [Getting Started](#getting-started)
 - [Asset Preprocessing](#asset-preprocessing)
-  - [CoffeeScript](#coffeescript)
   - [SASS / SCSS](#sass--scss)
   - [LESS](#less)
   - [Successive Preprocessing](#successive-preprocessing)
 - [Asset Compression](#asset-compression)
-  - [Yahoo's YUI Compressor](#yahoos-yui-compressor)
+  - [Terser](#terser)
   - [Google's Closure Compiler](#googles-closure-compiler)
 - [Templates](#templates)
 - [Configuration](#configuration)
-- [Octopress](#octopress)
 - [Contribute](#contribute)
 - [Community](#community)
 - [Credits](#credits)
@@ -30,8 +28,8 @@
 ## Features
 
 - Declarative dependency management via asset manifests
-- Asset preprocessing/conversion (supports [CoffeeScript](http://coffeescript.org/), [Sass / Scss](http://sass-lang.com/), [Less](http://lesscss.org/), [Erb](http://ruby-doc.org/stdlib-2.2.0/libdoc/erb/rdoc/ERB.html), etc.)
-- Asset compression (supports [YUI Compressor](http://yui.github.io/yuicompressor/), [Closure Compiler](https://developers.google.com/closure/compiler/), etc.)
+- Asset preprocessing/conversion (supports [Sass / Scss](https://sass-lang.com/), [Less](https://lesscss.org/), Erb, etc.)
+- Asset compression (supports [Terser](https://rubygems.org/gems/terser), [Closure Compiler](https://developers.google.com/closure/compiler/), etc.)
 - Fingerprints bundled asset filenames with MD5 hashes for better browser caching
 - Automatic generation of HTML `link` and `script` tags that point to bundled assets
 - Integrates seamlessly into Jekyll's workflow, including auto site regeneration
@@ -49,13 +47,13 @@ Jekyll Asset Pipeline's workflow can be summarized as follows:
 
 Jekyll Asset Pipeline is extremely easy to add to your Jekyll project and has no incremental dependencies beyond those required by Jekyll. Once you have a basic Jekyll site up and running, follow the steps below to install and configure Jekyll Asset Pipeline.
 
-1. Install the `jekyll_asset_pipeline` gem via [Rubygems](http://rubygems.org/).
+1. Install the `jekyll_asset_pipeline` gem via [RubyGems](https://rubygems.org/).
 
   ``` bash
   $ gem install jekyll_asset_pipeline
   ```
 
-  If you are using [Bundler](http://gembundler.com/) to manage your project's gems, you can just add `jekyll_asset_pipeline` to your Gemfile and run `bundle install`.
+  If you are using [Bundler](https://bundler.io/) to manage your project's gems, you can just add `jekyll_asset_pipeline` to your Gemfile and run `bundle install`.
 
 2. Add a `_plugins` folder to your project if you do not already have one. Within the `_plugins` folder, add a file named `jekyll_asset_pipeline.rb` with the following require statement as its contents.
 
@@ -65,7 +63,7 @@ Jekyll Asset Pipeline is extremely easy to add to your Jekyll project and has no
 
 3. Move your assets into a Jekyll ignored folder (i.e. a folder that begins with an underscore `_`) so that Jekyll won't include these raw assets in the site output. It is recommended to use an `_assets` folder to hold your site's assets.
 
-4. Add the following [Liquid](http://liquidmarkup.org/) blocks to your site's HTML `head` section. These blocks will be converted into HTML `link` and `script` tags that point to bundled assets. Within each block is a manifest of assets to include in the bundle. Assets are included in the same order that they are listed in the manifest. Replace the `foo` and `bar` assets with your site's assets. At this point we are just using plain old javascript and css files (hence the `.js` and `.css` extensions). See the [Asset Preprocessing](#asset-preprocessing) section to learn how to include files that must be preprocessed (e.g. CoffeeScript, Sass, Less, Erb, etc.). Name the bundle by including a string after the opening tag. We've named our bundles "global" in the below example.
+4. Add the following [Liquid](https://shopify.github.io/liquid/) blocks to your site's HTML `head` section. These blocks will be converted into HTML `link` and `script` tags that point to bundled assets. Within each block is a manifest of assets to include in the bundle. Assets are included in the same order that they are listed in the manifest. Replace the `foo` and `bar` assets with your site's assets. At this point we are just using plain old javascript and css files (hence the `.js` and `.css` extensions). See the [Asset Preprocessing](#asset-preprocessing) section to learn how to include files that must be preprocessed (e.g. Sass, Less, Erb, etc.). Name the bundle by including a string after the opening tag. We've named our bundles "global" in the below example.
 
   ``` html
   {% css_asset_tag global %}
@@ -78,7 +76,7 @@ Jekyll Asset Pipeline is extremely easy to add to your Jekyll project and has no
   - /_assets/bar.js
   {% endjavascript_asset_tag %}
   ```
-  Asset manifests must be formatted as YAML arrays and include full paths to each asset from the root of the project. YAML [does not allow tabbed markup](http://www.yaml.org/faq.html), so you must use spaces when indenting your YAML manifest or you will get an error when you compile your site. If you are using assets that must be preprocessed, you should append the appropriate extension (e.g. '.js.coffee', '.css.less') as discussed in the [Asset Preprocessing](#asset-preprocessing) section.
+  Asset manifests must be formatted as YAML arrays and include full paths to each asset from the root of the project. YAML [does not allow tabbed markup](https://yaml.org/faq.html), so you must use spaces when indenting your YAML manifest or you will get an error when you compile your site. If you are using assets that must be preprocessed, you should append the appropriate extension (e.g. '.js.coffee', '.css.less') as discussed in the [Asset Preprocessing](#asset-preprocessing) section.
 
 5. Run the `jekyll build` command to compile your site. You should see an output that includes the following Jekyll Asset Pipeline status messages.
 
@@ -97,112 +95,57 @@ That is it! You should now have bundled assets. Look in the `_site` folder of yo
 
 ## Asset Preprocessing
 
-Asset preprocessing (i.e. conversion) allows us to write our assets in languages such as [CoffeeScript](http://coffeescript.org/), [Sass](http://sass-lang.com/), [Less](http://lesscss.org/), [Erb](http://ruby-doc.org/stdlib-1.9.3/libdoc/erb/rdoc/ERB.html) or any other language. One of Jekyll Asset Pipeline's key strengths is that it works with __any__ preprocessing library that has a ruby wrapper. Adding a preprocessor is straightforward, but requires a small amount of additional code.
-
-In the following example, we will add a preprocessor that converts CoffeeScript into JavaScript.
-
-### CoffeeScript
-
-1. In the `jekyll_asset_pipeline.rb` file that we created in the [Getting Started](#getting-started) section, add the following code to the end of the file (i.e. after the `require` statement).
-
-  ``` ruby
-  module JekyllAssetPipeline
-    class CoffeeScriptConverter < JekyllAssetPipeline::Converter
-      require 'coffee-script'
-
-      def self.filetype
-        '.coffee'
-      end
-
-      def convert
-        return CoffeeScript.compile(@content)
-      end
-    end
-  end
-  ```
-
-  The above code adds a CoffeeScript converter. You can name a converter anything as long as it inherits from `JekyllAssetPipeline::Converter`. The `self.filetype` method defines the type of asset a converter will process (e.g. `.coffee` for CoffeeScript) based on the extension of the raw asset file. A `@content` instance variable that contains the raw content of our asset is made available within the converter. The converter should process this content and return the processed content (as a string) via a `convert` method.
-
-2. If you haven't already, you should now install any dependancies that are required by your converter. In our case, we need to install the `coffee-script` gem.
-
-  ``` bash
-  $ gem install coffee-script
-  ```
-
-  If you are using [Bundler](http://gembundler.com/) to manage your project's gems, you can just add `coffee-script` to your Gemfile and run `bundle install`.
-
-3. Append a `.coffee` extension to the filename of any asset that should be converted with the `CoffeeScriptConverter`. For example, `foo.js` would become `foo.js.coffee`.
-
-4. Run the `jekyll build` command to compile your site.
-
-That is it! Your asset pipeline has converted any CoffeeScript assets into JavaScript before adding them to a bundle.
+Asset preprocessing (i.e. conversion) allows us to write our assets in languages such as [Sass](https://sass-lang.com/), [Less](https://lesscss.org/), Erb, or any other language. One of Jekyll Asset Pipeline's key strengths is that it works with __any__ preprocessing library that has a Ruby wrapper. Adding a preprocessor is straightforward, but requires a small amount of additional code.
 
 ### SASS / SCSS
 
-You probably get the gist of how converters work, but here's an example of a SASS converter for quick reference.
+Here's an example of a Sass converter using the actively-maintained [`sass-embedded`](https://rubygems.org/gems/sass-embedded) gem (the official Ruby binding for Dart Sass).
 
 ``` ruby
 module JekyllAssetPipeline
   class SassConverter < JekyllAssetPipeline::Converter
-    require 'sass'
+    require 'sass-embedded'
 
     def self.filetype
       '.scss'
     end
 
     def convert
-      return Sass::Engine.new(@content, syntax: :scss).render
+      Sass.compile_string(@content, syntax: :scss, load_paths: [@dirname]).css
     end
   end
 end
 ```
 
-Don't forget to install the `sass` gem or add it to your Gemfile and run `bundle install` before you run the `jekyll build` command since the above SASS converter requires the `sass` library as a dependency.
-
-If you're using `@import` statements in your SASS files, you'll probably need to specify a base load path to the SASS engine in your `convert` method.
-You can use the `@dirname` instance variable for this, which contains the path to the current asset's directory:
-
-``` ruby
-...
-def convert
-  return Sass::Engine.new(@content, syntax: :scss, load_paths: [@dirname]).render
-end
-...
-```
+Install the `sass-embedded` gem or add it to your Gemfile and run `bundle install`. The `load_paths: [@dirname]` option ensures that `@use` and `@import` rules resolve relative to the asset's directory.
 
 ### LESS
 
+No actively-maintained pure-Ruby gem exists for LESS, but you can shell out to the [Node `lessc` binary](https://lesscss.org/) (install with `npm install -g less`) using Ruby's standard `Open3` library:
+
 ``` ruby
 module JekyllAssetPipeline
   class LessConverter < JekyllAssetPipeline::Converter
-    require 'less'
+    require 'open3'
 
     def self.filetype
       '.less'
     end
 
     def convert
-      return Less::Parser.new.parse(@content).to_css
+      stdout, status = Open3.capture2("lessc --include-path=#{@dirname} -", stdin_data: @content)
+      raise "lessc failed" unless status.success?
+      stdout
     end
   end
 end
 ```
 
-Don't forget to install the `less` gem or add it to your Gemfile and run `bundle install` before you run the `jekyll build` command since the above LESS converter requires the `less` library as a dependency.
-
-As with the SASS convertor, you'll probably need to specify a base load path and pass that to the LESS Parser:
-
-``` ruby
-...
-def convert
-  return Less::Parser.new(paths: [@dirname]).parse(@content).to_css
-end
-...
-```
+This pattern — shelling out to any compiler that reads from stdin — works for any tool that has a command-line interface, not just LESS.
 
 ### Successive Preprocessing
 
-If you would like to run an asset through multiple preprocessors successively, you can do so by naming your assets with nested file extensions. Nest the extensions in the order (right to left) that the asset should be processed. For example, `.css.scss.erb` would first be processed by an `erb` preprocessor then by a `scss` preprocessor before being rendered. This convention is very similar to the convention used by the [Ruby on Rails asset pipeline](http://guides.rubyonrails.org/asset_pipeline.html#preprocessing).
+If you would like to run an asset through multiple preprocessors successively, you can do so by naming your assets with nested file extensions. Nest the extensions in the order (right to left) that the asset should be processed. For example, `.css.scss.erb` would first be processed by an `erb` preprocessor then by a `scss` preprocessor before being rendered. This convention is very similar to the convention used by the [Ruby on Rails asset pipeline](https://guides.rubyonrails.org/asset_pipeline.html#preprocessing).
 
 Don't forget to define preprocessors for the extensions you use in your filenames, otherwise Jekyll Asset Pipeline will not process your asset.
 
@@ -210,57 +153,45 @@ Don't forget to define preprocessors for the extensions you use in your filename
 
 Asset compression allows us to decrease the size of our assets and increase the speed of our site. One of Jekyll Asset Pipeline's key strengths is that it works with __any__ compression library that has a ruby wrapper. Adding asset compression is straightforward, but requires a small amount of additional code.
 
-In the following example, we will add a compressor that uses Yahoo's YUI Compressor to compress our CSS and JavaScript assets.
+In the following example, we will add a JavaScript compressor using the actively-maintained [`terser`](https://rubygems.org/gems/terser) gem. For CSS compression, the `sass-embedded` converter shown above supports compressed output natively via `style: :compressed`.
 
-### Yahoo's YUI Compressor
+### Terser
 
 1. In the `jekyll_asset_pipeline.rb` file that we created in the [Getting Started](#getting-started) section, add the following code to the end of the file (i.e. after the `require` statement).
 
   ``` ruby
   module JekyllAssetPipeline
-    class CssCompressor < JekyllAssetPipeline::Compressor
-      require 'yui/compressor'
-
-      def self.filetype
-        '.css'
-      end
-
-      def compress
-        return YUI::CssCompressor.new.compress(@content)
-      end
-    end
-
     class JavaScriptCompressor < JekyllAssetPipeline::Compressor
-      require 'yui/compressor'
+      require 'terser'
 
       def self.filetype
         '.js'
       end
 
       def compress
-        return YUI::JavaScriptCompressor.new(munge: true).compress(@content)
+        Terser.new.compile(@content)
       end
     end
   end
   ```
 
-  The above code adds a CSS and a JavaScript compressor. You can name a compressor anything as long as it inherits from `JekyllAssetPipeline::Compressor`. The `self.filetype` method defines the type of asset a compressor will process (either `'.js'` or `'.css'`). The `compress` method is where the magic happens. A `@content` instance variable that contains the raw content of our bundle is made available within the compressor. The compressor should process this content and return the processed content (as a string) via a `compress` method.
+  You can name a compressor anything as long as it inherits from `JekyllAssetPipeline::Compressor`. The `self.filetype` method defines the type of asset a compressor will process (either `'.js'` or `'.css'`). The `compress` method is where the magic happens. A `@content` instance variable that contains the raw content of our bundle is made available within the compressor. The compressor should process this content and return the processed content (as a string) via a `compress` method.
 
-2. If you haven't already, you should now install any dependencies that are required by your compressor. In our case, we need to install the `yui-compressor` gem.
+2. If you haven't already, install the `terser` gem.
 
   ``` bash
-  $ gem install yui-compressor
+  $ gem install terser
   ```
 
-  If you are using [Bundler](http://gembundler.com/) to manage your project's gems, you can just add `yui-compressor` to your Gemfile and run `bundle install`.
+  If you are using [Bundler](https://bundler.io/) to manage your project's gems, you can just add `terser` to your Gemfile and run `bundle install`.
 
 3. Run the `jekyll build` command to compile your site.
 
-That is it! Your asset pipeline has compressed your CSS and JavaScript assets. You can verify that this is the case by looking at the contents of the bundles generated in the `_site/assets` folder of your project.
+That is it! Your asset pipeline has compressed your JavaScript assets. You can verify that this is the case by looking at the contents of the bundles generated in the `_site/assets` folder of your project.
 
 ### Google's Closure Compiler
 
-You probably get the gist of how compressors work, but here's an example of a Google Closure Compiler compressor for quick reference.
+Here's an alternative example using the Google Closure Compiler.
 
 ``` ruby
 class JavaScriptCompressor < JekyllAssetPipeline::Compressor
@@ -271,7 +202,7 @@ class JavaScriptCompressor < JekyllAssetPipeline::Compressor
   end
 
   def compress
-    return Closure::Compiler.new.compile(@content)
+    Closure::Compiler.new.compile(@content)
   end
 end
 ```
@@ -311,7 +242,7 @@ That is it! Your asset pipeline used your template to generate an HTML `link` ta
 
 ## Configuration
 
-Jekyll Asset Pipeline provides the following configuration options that can be controlled by adding them to your project's `_config.yml` file. If you don't have a `_config.yml` file, consider reading the [configuration section](https://github.com/mojombo/jekyll/wiki/Configuration) of the Jekyll documentation.
+Jekyll Asset Pipeline provides the following configuration options that can be controlled by adding them to your project's `_config.yml` file. If you don't have a `_config.yml` file, consider reading the [configuration section](https://jekyllrb.com/docs/configuration/) of the Jekyll documentation.
 
 ``` yaml
 asset_pipeline:
@@ -331,31 +262,11 @@ Setting        | Default  | Description
 `gzip`         | `false`  | controls whether Jekyll Asset Pipeline saves gzipped versions of your assets alongside un-gzipped versions.
 
 
-## Octopress
-
-[Octopress](http://octopress.org/) is a popular framework for Jekyll that can help you get a blog up and running quickly. Jekyll Asset Pipeline can be added to an Octopress site using the [Getting Started](#getting-started) steps above with the following modifications:
-
-1. Octopress uses Bundler to manage your site's dependencies. You should add `gem jekyll_asset_pipeline` to your Gemfile and then run `bundle install` to install.
-
-2. Instead of adding a `_plugins` folder, you should put `jekyll_asset_pipeline.rb` in the `plugins` folder included by default in the root of your Octopress site.
-
-3. You should still store your assets in an Jekyll ignored folder (i.e. a folder that begins with an underscore `_`), but note that this folder should be located within the `source` folder of your Octopress site (e.g. `source/_assets`).
-
-4. No change to this step.
-
-5. Instead of running the `jekyll` command to compile your site, you should use Octopress' rake commands (e.g. `rake generate`) as outlined [here](http://octopress.org/docs/blogging/).
-
-If you have any difficulties using Jekyll Asset Pipeline with Octopress, please [open an issue](http://github.com/matthodan/jekyll-asset-pipeline/issues).
-
 ## Contribute
 
-You can contribute to the Jekyll Asset Pipeline by submitting a pull request [via GitHub](https://github.com/matthodan/jekyll-asset-pipeline). There are a few areas that need improvement:
-
-- __Tests, tests, tests.__ **This project is now fully tested.**
-- __Successive preprocessing.__ Currently you can only preprocess a file once. It would be better if you could run an asset through multiple preprocessors before it gets compressed and bundled. **As of v0.1.0, Jekyll Asset Pipeline now supports successive preprocessing.**
-- __Handle remote assets.__ Right now, Jekyll Asset Pipeline does not provide any way to include remote assets in bundles unless you save them locally before generating your site. Moshen's [Jekyll Asset Bundler](https://github.com/moshen/jekyll-asset_bundler) allows you to include remote assets, which is pretty interesting. That said, it is generally better to keep remote assets separate so that they load asynchronously.
+You can contribute to Jekyll Asset Pipeline by submitting a pull request [via GitHub](https://github.com/janosrusiczki/jekyll-asset-pipeline).
 
-If you have any ideas or you would like to see anything else improved please use the [issues section](https://github.com/matthodan/jekyll-asset-pipeline/issues).
+If you have any ideas or you would like to see anything else improved please use the [issues section](https://github.com/janosrusiczki/jekyll-asset-pipeline/issues).
 
 ## Changelog
 
@@ -363,14 +274,13 @@ See [the changelog](CHANGELOG.md).
 
 ## Community
 
-- Here is [GitHub's list of projects that use the gem](https://github.com/matthodan/jekyll-asset-pipeline/network/dependents).
-- Here is a currated list of [sites that use Jekyll Asset Pipeline](http://github.com/matthodan/jekyll-asset-pipeline/wiki/Sites-that-use-Jekyll-Asset-Pipeline). Feel free to add your site to the list if you want.
+- Here is [GitHub's list of projects that use the gem](https://github.com/janosrusiczki/jekyll-asset-pipeline/network/dependents).
 
 ## Credits
 
 * [Moshen](https://github.com/moshen/) for creating the [Jekyll Asset Bundler](https://github.com/moshen/jekyll-asset_bundler).
-* [Mojombo](https://github.com/mojombo) for creating [Jekyll](https://github.com/mojombo/jekyll) in the first place.
+* [Mojombo](https://github.com/mojombo) for creating [Jekyll](https://github.com/jekyll/jekyll) in the first place.
 
 ## License
 
-Jekyll Asset Pipeline is released under the [MIT License](http://opensource.org/licenses/MIT).
+Jekyll Asset Pipeline is released under the [MIT License](https://opensource.org/licenses/MIT).

data/lib/jekyll_asset_pipeline/extensions/ruby/subclass_tracking.rb

@@ -6,6 +6,7 @@ module JekyllAssetPipeline
     # Record subclasses of this class (this method is automatically called by
     # ruby)
     def inherited(base)
+      super
       subclasses << base
     end
 

data/lib/jekyll_asset_pipeline/pipeline.rb

@@ -62,9 +62,8 @@ module JekyllAssetPipeline
         FileUtils.rm_rf(staging_path)
       end
 
-      # Add prefix to output
       def puts(message)
-        $stdout.puts("Asset Pipeline: #{message}")
+        Jekyll.logger.info('Asset Pipeline:', message)
       end
 
       private
@@ -107,11 +106,16 @@ module JekyllAssetPipeline
       convert
       bundle if @options['bundle']
       compress if @options['compress']
+      finalize_bundle_filename if @options['bundle']
       gzip if @options['gzip']
       save
       markup
     end
 
+    def log_error(message)
+      Jekyll.logger.error('Asset Pipeline:', message)
+    end
+
     # Collect assets based on manifest
     def collect
       @assets = YAML.safe_load(@manifest).map! do |path|
@@ -122,8 +126,7 @@ module JekyllAssetPipeline
         end
       end
     rescue StandardError => e
-      puts 'Asset Pipeline: Failed to load assets from provided ' \
-           "manifest: #{e.message}"
+      log_error "Failed to load assets from provided manifest: #{e.message}"
       raise e
     end
 
@@ -156,23 +159,24 @@ module JekyllAssetPipeline
       asset.filename = File.basename(asset.filename, '.*')
 
       # Add back the output extension if no extension left
-      if File.extname(asset.filename) == ''
-        asset.filename = "#{asset.filename}#{@type}"
-      end
+      asset.filename = "#{asset.filename}#{@type}" if File.extname(asset.filename) == ''
     rescue StandardError => e
-      puts "Asset Pipeline: Failed to convert '#{asset.filename}' " \
-           "with '#{klass}': #{e.message}"
+      log_error "Failed to convert '#{asset.filename}' with '#{klass}': #{e.message}"
       raise e
     end
 
     # Bundle multiple assets into a single asset
     def bundle
       content = @assets.map(&:content).join("\n")
+      @assets = [::JekyllAssetPipeline::Asset.new(content, "#{@prefix}#{@type}")]
+    end
 
-      hash = ::JekyllAssetPipeline::Pipeline.hash(@source, @manifest, @options)
-      @assets = [
-        ::JekyllAssetPipeline::Asset.new(content, "#{@prefix}-#{hash}#{@type}")
-      ]
+    # Set final bundle filename from MD5 of post-compression content
+    def finalize_bundle_filename
+      @assets.each do |asset|
+        hash = Digest::MD5.hexdigest(asset.content)
+        asset.filename = "#{@prefix}-#{hash}#{@type}"
+      end
     end
 
     # Compress assets if compressor is defined
@@ -188,8 +192,7 @@ module JekyllAssetPipeline
         begin
           asset.content = klass.new(asset.content).compressed
         rescue StandardError => e
-          puts "Asset Pipeline: Failed to compress '#{asset.filename}' " \
-               "with '#{klass}': #{e.message}"
+          log_error "Failed to compress '#{asset.filename}' with '#{klass}': #{e.message}"
           raise e
         end
       end
@@ -230,8 +233,7 @@ module JekyllAssetPipeline
           file.write(asset.content)
         end
       rescue StandardError => e
-        puts "Asset Pipeline: Failed to save '#{asset.filename}' to " \
-             "disk: #{e.message}"
+        log_error "Failed to save '#{asset.filename}' to disk: #{e.message}"
         raise e
       end
     end

data/lib/jekyll_asset_pipeline/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module JekyllAssetPipeline
-  VERSION = '0.6.2'
+  VERSION = '0.7.0'
 end

data/lib/jekyll_asset_pipeline.rb

@@ -19,10 +19,7 @@ require 'jekyll_asset_pipeline/extensions/jekyll/site'
 require 'jekyll_asset_pipeline/extensions/liquid/liquid_block_extensions'
 require 'jekyll_asset_pipeline/extensions/liquid/asset_tag'
 require 'jekyll_asset_pipeline/extensions/liquid/asset_tags/css_asset_tag'
-# rubocop:disable Metrics/LineLength
 require 'jekyll_asset_pipeline/extensions/liquid/asset_tags/javascript_asset_tag'
-# rubocop:enable Metrics/LineLength
-
 # Ruby extensions
 require 'jekyll_asset_pipeline/extensions/ruby/subclass_tracking'
 

metadata

@@ -1,15 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: jekyll_asset_pipeline
 version: !ruby/object:Gem::Version
-  version: 0.6.2
+  version: 0.7.0
 platform: ruby
 authors:
 - Matt Hodan
 - Janos Rusiczki
-autorequire: 
 bindir: bin
 cert_chain: []
-date: 2019-10-16 00:00:00.000000000 Z
+date: 2026-05-17 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: jekyll
@@ -65,14 +64,14 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '12.0'
+        version: '13.0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '12.0'
+        version: '13.0'
 description: |2
       Jekyll Asset Pipeline adds asset preprocessing (CoffeeScript, Sass,
       Less, ERB, etc.) and asset compression / minification / gzip (Yahoo YUI
@@ -104,11 +103,10 @@ files:
 - lib/jekyll_asset_pipeline/templates/javascript_tag_template.rb
 - lib/jekyll_asset_pipeline/templates/template_helper.rb
 - lib/jekyll_asset_pipeline/version.rb
-homepage: https://github.com/matthodan/jekyll-asset-pipeline
+homepage: https://github.com/janosrusiczki/jekyll-asset-pipeline
 licenses:
 - MIT
 metadata: {}
-post_install_message: 
 rdoc_options: []
 require_paths:
 - lib
@@ -116,16 +114,14 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
-      version: 2.3.0
+      version: 2.7.0
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubyforge_project: 
-rubygems_version: 2.7.8
-signing_key: 
+rubygems_version: 3.6.9
 specification_version: 4
 summary: A powerful asset pipeline for Jekyll that bundles, converts, and minifies
   CSS and JavaScript assets.