Lugo Labs
  • Products
    Iconly Tracker
  • Open Source
    Circles Loda button Datepicker skins Icofont Iconly Rails Skins
  • Tools
    Caret Flat Slider Charicons
  • Blog
    Blog Reading List
  • Contact

Production edge case with using a SCSS manifest file with the Asset Pipeline etc.

5 May 2016

Ruby on Rails JavaScript HTML CSS UX Processes


New Netguru Gem Will Help You Integrate React And Redux With Rails

New Netguru Gem Will Help You Integrate React And Redux With Rails

netguru - 04 May 2016

I’ve been involved in the development of the react_webpack_rails gem, which provides simple and lightweight integration of Rails, React and Weback. This gem allows one to build rich user interfaces with a modern JavaScript stack on top of Rails applications. You can find more info about react_webpack_rails in this github repo.

ImageMagick vulnerability does not affect Paperclip

ImageMagick vulnerability does not affect Paperclip

Giant Robots Smashing into Other Giant Robots - 04 May 2016

There is no need to upgrade Paperclip in light of CVE-2016–3714. You may choose to upgrade ImageMagick regardless.

Testing Your Style With ESLint and Mocha

Testing Your Style With ESLint and Mocha

Giant Robots Smashing into Other Giant Robots - 04 May 2016

Use ESLint and Mocha to generate tests for the style of your codebase.

Production edge case with using a SCSS manifest file with the Asset Pipeline

Production edge case with using a SCSS manifest file with the Asset Pipeline

Reinteractive - 03 May 2016

Today I found an interesting edge case in using SASS or SCSS in Rails with the asset pipeline. The manifest file in this Rails application was an application.scss file and was using @import statements instead of require statements. However, two of the lines were: @import "chosen/chosen.css"; @import "flowplayer/flowplayer.css"; These look innocent enough. But when the application was deployed to production, the application.css file started with @import url(chosen/chosen.css); @import url...

Rails 5 adds a way to get information about types of failed validations

Rails 5 adds a way to get information about types of failed validations

Bigbinary - 03 May 2016
This works out well for normal apps. But in case of API only applications, sometimes we want to allow the client consuming the API to generate customized error message as per their needs. We don’t want to send the final translated messages in such cases. Instead if we could just send details that presence validation failed for :name attribute, the client app would be able to customize the error message based on that information.
Container-Ready Rails 5

Container-Ready Rails 5

Heroku - 02 May 2016

Rails 5 will be the easiest release ever to get running on Heroku. You can get it going in just five lines:

Comparing Rails: Exploring WebSockets in Phoenix

Comparing Rails: Exploring WebSockets in Phoenix

SitePoint - 02 May 2016

One of the biggest features in Rails 5 is WebSockets. Seems like this feature has been inspired in part by Phoenix, the Elixir web framework. In this article, we take a look at creating a real-time Twitter stream heatmap using Elixir and Phoenix. The idea is to hook into the Twitter sample stream and plot […]

Gem Dependency Issues with Rails 5 Beta

Gem Dependency Issues with Rails 5 Beta

End Point - 02 May 2016

Posted by Patrick Lewis |May 2, 2016 Tags: dependencies, dependency management, gem, rails, ruby, Ruby on Rails, rubygems

Introducing Empties – Unstyled Components

Introducing Empties – Unstyled Components

Giant Robots Smashing into Other Giant Robots - 02 May 2016

Announcing the latest addition to the Bourbon suite! Meet Refills less fashionable sibling, Empties, a new library of components that are completely – or for the most part – unstyled.

5 Ways to Write Sass That Plays Well With Others

5 Ways to Write Sass That Plays Well With Others

Gaslight - 29 April 2016

Sass is an excellent tool for front-end designers and developers. It can improve the CSS authoring experience and help you quickly build out your design system. Like any tool, however, it can be misused. When working with teams or working on projects that will be handed off to a client, it is important to maintain your Sass in a clear, easy to understand way so that others can quickly learn how to implement and iterate on the design system.

Have a project to develop? Get in touch

Lugo Labs

Open Source

  • Iconly
  • Icofont
  • Tabular
  • Rails skins
  • Gambas
  • Blue csv
  • Circles
  • Loda button
  • jQuery datepicker skins
  • Colonne
  • jQuery UI pic

Tools

  • caret
  • flat slider
  • charicons

Products

  • Tracker
  • Iconly

© 2006-2025 Lugo Labs - Contact
Lugo Labs