jekyll-postcss 0.4.0 → 0.4.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: b814559fcadf25906a68dbb7e40926a72fa75aa92e293e3d39454dd9bcf784cd
-  data.tar.gz: 779270e4ff58d9b35a4c46dbfbab8be77998edd9c2307208a7654b27ab2841f2
+  metadata.gz: cba7273f4532e27ab92106857418dc0263b353e5bf82de0f6b01ab7a9f0672c3
+  data.tar.gz: d4f38cf3b58e9d5a5f84425b19795a99c586eb5a7a65e3f17c24edad9bda81af
 SHA512:
-  metadata.gz: 65fb6ab42952f39ae49851e0600539fcac18ad4505fb817db67690c518984f73e09672d6dd6a00a2d989c05a054d13c15d2a88a0fc4fa0043fb654d48b3d43c4
-  data.tar.gz: 72ff0a8ad7f284634faafd8adf4b33baf77532af7ea680ce0e05a89c1107d9e64643934477917d63106dfa0abb42b75f985cb6a6de60acb7fc3ef091384a9571
+  metadata.gz: 4c33fa3a5cbaa238644fe013dbe4f8c0dc7773c4c77993b193c08f130b00b2fd2917997ab83416e88eb169b9464a621ef1011567c60b7b33a8913f63723d20bc
+  data.tar.gz: 30238af1504ce3ec730a22bd9dd02a0e01ef2550467d4b4d78a21e10663b9b9f61cc1cc1f528819586cad62a11d999cbae244a08d71115aca1c70808584f50b6

data/.tool-versions

@@ -1 +1 @@
-ruby 2.5.3
+ruby 2.7.2

data/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Changelog
 
+## 0.4.1
+
+- Fix a weird issue where the jekyll server never booted up because the converter class got in an infinite loop trying to make a socket connection to the postcss server.
+
 ## 0.4.0
 
 ### Process SCSS/Sass files
@@ -24,7 +28,8 @@ jekyll-postcss has a higher priority, so it will hand off the the postcss output
 
 ## 0.3.1
 
-- Only run development server in development
+- Only run development server in development.
+    - This was discovered when attempting to deploy to Netlify. You can read more about it here [#8](https://github.com/mhanberg/jekyll-postcss/issues/8), [#15](https://github.com/mhanberg/jekyll-postcss/issues/15), and [here](https://community.netlify.com/t/deploy-is-hanging-postcss-problem/14822).
 
 ## 0.3.0
 

data/README.md

@@ -13,6 +13,7 @@ Add this line to your application's Gemfile:
 ```ruby
 gem 'jekyll-postcss'
 ```
+
 And then add this line to your application's `_config.yml`:
 
 ```yml
@@ -33,7 +34,7 @@ Add your PostCSS plugins to a `postcss.config.js` file in the root of your repos
 
 module.exports = {
   plugins: [
-    require("autoprefixer") // example of plugin you might use
+    require("autoprefixer"), // example of plugin you might use
     ...(process.env.JEKYLL_ENV == "production" // example of only using a plugin in production
       ? [require("cssnano")({ preset: "default" })]
       : [])
@@ -56,11 +57,34 @@ module.exports = {
 };
 ```
 
-### Notes
+### Deployment
+
+When deploying, make sure to set your `JEKYLL_ENV` to something like `production` or `staging`. This is necessary to make sure that jekyll-postcss will not use internal development conveniences when building on your host's servers.
+
+This can be done so by setting your build command like so
+
+```shell
+JEKYLL_ENV=production bundle exec jekyll build
+```
+
+or using your hosts proprietary configuration. Here is an example using Netlify.
+
+```toml
+# netlify.toml
+
+[context.production.environment]
+  JEKYLL_ENV = "production"
+
+[context.branch-deploy.environment]
+  JEKYLL_ENV = "staging"
+
+[context.deploy-preview.environment]
+  JEKYLL_ENV = "staging"
+```
 
-jekyll-postcss will run a development server when `JEKYLL_ENV` is set to `development`. This is the default value if you don't set it elsewhere. When building your site for production or staging, make sure to set the `JEKYLL_ENV` appropriately, or else your deploy may fail, e.g., `JEKYLL_ENV=production bundle exec jekyll build`.
+### Front Matter Reminder
 
-Also note that your `.css` files still need to have a [front matter](https://jekyllrb.com/docs/step-by-step/03-front-matter/) for them to be processed by Jekyll.
+Your stylesheets still need to have [front matter](https://jekyllrb.com/docs/step-by-step/03-front-matter/) for them to be processed by Jekyll.
 
 ```
 ---

data/bin/release

@@ -0,0 +1,3 @@
+#!/usr/bin/env bash
+
+bundle exec rake release

data/bin/spec

@@ -0,0 +1,3 @@
+#!/usr/bin/env bash
+
+bundle exec rspec "$@"

data/lib/jekyll-postcss/socket.rb

@@ -49,19 +49,27 @@ module PostCss
       @env == "development"
     end
 
+    MAX_ATTEMPTS = 100
+
     def start_dev_server
       Thread.new do
         system "#{START_SCRIPT} #{POSTCSS_SCRIPT} --development"
       end
 
-      @postcss = nil
-      while @postcss.nil?
+      attempts = 0
+      @postcss =
         begin
-          @postcss = TCPSocket.open("localhost", 8124)
-        rescue StandardError
-          nil # Suppressing exceptions
+          TCPSocket.open("localhost", 8124) 
+        rescue StandardError => e
+          attempts = attempts + 1
+
+          if attempts < MAX_ATTEMPTS
+            sleep 0.1
+            retry 
+          else
+            raise "Could not connect to the PostCSS server"
+          end
         end
-      end
     end
   end
 end

data/lib/jekyll-postcss/version.rb

@@ -2,6 +2,6 @@
 
 module Jekyll
   module PostCss
-    VERSION = "0.4.0"
+    VERSION = "0.4.1"
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: jekyll-postcss
 version: !ruby/object:Gem::Version
-  version: 0.4.0
+  version: 0.4.1
 platform: ruby
 authors:
 - Mitchell Hanberg
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2020-05-20 00:00:00.000000000 Z
+date: 2021-05-26 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -102,7 +102,9 @@ files:
 - bin/command
 - bin/console
 - bin/postcss
+- bin/release
 - bin/setup
+- bin/spec
 - jekyll-postcss.gemspec
 - lib/jekyll-postcss.rb
 - lib/jekyll-postcss/socket.rb
@@ -131,8 +133,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubyforge_project: 
-rubygems_version: 2.7.6
+rubygems_version: 3.1.4
 signing_key: 
 specification_version: 4
 summary: A PostCSS plugin for Jekyll.