assets-packager - Assets pipeline for ultra fast CSS and JavaScript packaging.

  •        7

Assets-packager is a tool for compiling, minifying, and packaging CSS and JavaScript assets into production-ready packages.It is used as a part of build process for GoalSmashers.com and it takes around 10 seconds to buld 40 CSS and 20 JavaScript bundles from hundreds of assets.

https://github.com/jakubpawlowicz/assets-packager

Dependencies:

assets-expander : 1.0.x
async : 0.9.x
clean-css : 2.2.x
commander : 2.3.x
enhance-css : 1.1.x
less : 1.7.x
uglify-js : 2.4.x

Tags
Implementation
License
Platform

   




Related Projects

connect-assets - A Rails-style asset pipeline for Node.js

  •    Javascript

Transparent file compilation and dependency management for Node’s connect framework in the spirit of the Rails asset pipeline. Finally, create an assets directory in your project and throw all assets compiled into JavaScript into /assets/js and all assets compiled into CSS into /assets/css.

connect-assets - A Rails-style asset pipeline for Node.js

  •    Javascript

Transparent file compilation and dependency management for Node’s connect framework in the spirit of the Rails asset pipeline. Finally, create an assets directory in your project and throw all assets compiled into JavaScript into /assets/js and all assets compiled into CSS into /assets/css.

sinatra-asset-pipeline - An asset pipeline for Sinatra based on Sprockets.

  •    Ruby

An asset pipeline implementation for Sinatra based on Sprockets. sinatra-asset-pipeline supports both compiling assets on the fly for development as well as precompiling assets for production. The design goal for sinatra-asset-pipeline is to provide good defaults for integrating your Sinatra application with Sprockets. This makes your application serve assets inside assets folder under the public /assets path. You can use the helpers provided by sprocket-helpers inside your assets to ease locating your assets.

jekyll-assets - :art: Asset pipelines for Jekyll.

  •    Ruby

Jekyll Assets is a drop in asset pipeline that uses Sprockets to build specifically for Jekyll. It utilizes Sprockets, and Jekyll to try and achieve a clean, and extensible assets platform that supports plugins, caching, converting your assets. It even supports proxying of said assets in a way that does not interfere with either Sprockets, or Jekyll, or your own source. By default you can add Jekyll Assets to your Gemfile, as a plugin, and have it act as a drop-in replacement for Jekyll's basic SASS processors, with you only having to add it to your Gemfile, and updating your <img>, and <link>. The configuration file is the same as Jekyll's, which is _config.yml. Except we use the special key called assets inside of that file. All values listed below are default, you need not copy these into your configuration file unless you plan to change a value. Setting a value makes it explicit, and shared across both production, and development.

webpacker - Use Webpack to manage app-like JavaScript modules in Rails

  •    Ruby

Webpacker makes it easy to use the JavaScript pre-processor and bundler webpack 3.x.x+ to manage application-like JavaScript in Rails. It coexists with the asset pipeline, as the primary purpose for webpack is app-like JavaScript, not images, CSS, or even JavaScript Sprinkles (that all continues to live in app/assets).However, it is possible to use Webpacker for CSS, images and fonts assets as well, in which case you may not even need the asset pipeline. This is mostly relevant when exclusively using component-based JavaScript frameworks.


serviceworker-rails - Use Service Worker with the Rails asset pipeline

  •    Ruby

The Rails asset pipeline makes a number of assumptions about what's best for deploying JavaScript, including asset digest fingerprints and long-lived cache headers - mostly to increase "cacheability". Rails also assumes a single parent directory, /public/assets, to make it easier to look up the file path for a given asset. Service workers may only be active from within the scope from which they are served. So if you try to register a service worker from a Rails asset pipeline path, like /assets/serviceworker-abcd1234.js, it will only be able to interact with requests and responses within /assets/**. This is not what we want.

sprockets - Rack-based asset packaging system

  •    Ruby

Sprockets is a Ruby library for compiling and serving web assets. It features declarative dependency management for JavaScript and CSS assets, as well as a powerful preprocessor pipeline that allows you to write assets in languages like CoffeeScript, Sass and SCSS.For most people interested in using Sprockets, you will want to see End User Asset Generation guide. This contains information about Sprockets' directive syntax and default processing behavior.

sbt-native-packager - sbt Native Packager

  •    Scala

SBT native packager lets you build application packages in native formats. It offers different archetypes for common configurations, such as simple Java apps or server applications. Discussion/Questions: If you wish to ask questions about the native packager, we have a mailinglist and we're very active on Stack Overflow. You can either use the sbt tag or the sbt-native-packager tag. They also have far better search support for working around issues.

harp - Static Site Server/Generator with built-in preprocessing

  •    Javascript

Harp is a static web server that also serves Jade, Markdown, EJS, Less, Stylus, Sass, and CoffeeScript as HTML, CSS, and JavaScript without any configuration. It supports the beloved layout/partial paradigm and it has flexible metadata and global objects for traversing the file system and injecting custom data into templates. Optionally, Harp can also compile your project down to static assets for hosting behind any valid HTTP server. Pre-compilers are becoming extremely powerful and shipping front-ends as static assets has many upsides. It's simple, it's easy to maintain, it's low risk, easy to scale, and requires low cognitive overhead. I wanted a lightweight web server that was powerful enough for me to abandon web frameworks for dead simple front-end publishing.

Assets - An ultra-simple-to-use assets management library for PHP

  •    PHP

An ultra-simple-to-use assets management PHP library. The library is framework agnostic and it should work well with any framework or naked PHP application. Nevertheless, since the library is most popular between Laravel users the following instructions have been tailored for Laravel 5 framework (still on Laravel 4?). If you want to use the library in any other scenario please read the non static interface instructions.

non-stupid-digest-assets - Fix the Rails 4 asset pipeline to generate non-digest along with digest assets

  •    Ruby

In Rails 4, there is no way to by default compile both digest and non-digest assets. This is a pain in the arse for almost everyone developing a Rails 4 app. This gem solves the problem with the minimum possible effort. Be sure to give either a regex that will match the right assets or the logical path of the asset in question.

postcss-assets - An asset manager for PostCSS

  •    Javascript

PostCSS Assets is an asset manager for CSS. It isolates stylesheets from environmental changes, gets image sizes and inlines files. Note: all of the listed options below are parameters for the assets object, not the top level postcss options object.

webpack-encore - A simple but powerful API for processing & compiling assets built around Webpack

  •    Javascript

Webpack Encore is a simpler way to integrate Webpack into your application. It wraps Webpack, giving you a clean & powerful API for bundling JavaScript modules, pre-processing CSS & JS and compiling and minifying assets. Encore gives you professional asset system that's a delight to use. Encore is inspired by Webpacker and Mix, but stays in the spirit of Webpack: using its features, concepts and naming conventions for a familiar feel. It aims to solve the most common Webpack use cases.

shaka-packager - A media packaging SDK intended for C++ programmers writing MPEG-DASH packaging applications with Widevine DRM and Common Encryption support

  •    C++

Media packaging SDK intended for C++ programmers writing DASH/HLS packager applications with common encryption support, Widevine DRM support, Live, and Video-On-Demand.This document provides the information needed to create a DASH/HLS packager that is able to remux and encrypt a video into fragmented ISO BMFF format with common encryption (CENC) support. The DASH/HLS packaging API is also designed in such a way for easy extension to more source and destination formats.

electron-packager - Customize and package your Electron app with OS-specific bundles (

  •    Javascript

Package your Electron app into OS-specific bundles (.app, .exe, etc.) via JavaScript or the command line. Electron Packager is a command line tool and Node.js library that bundles Electron-based application source code with a renamed Electron executable and supporting files into folders ready for distribution.

asset_sync - Synchronises Assets between Rails and S3

  •    Ruby

Synchronises Assets between Rails and S3. Asset Sync is built to run with the new Rails Asset Pipeline feature introduced in Rails 3.1. After you run bundle exec rake assets:precompile your assets will be synchronised to your S3 bucket, optionally deleting unused files and only uploading the files it needs to.

jquery-mobile-rails - JQuery Mobile for Rails 3.1 assets pipeline

  •    Ruby

JQuery Mobile for Rails 3.1 assets pipeline

bootstrap-datepicker-rails - A Datepicker for Twitter Bootstrap, integrated with Rails assets pipeline

  •    Ruby

bootstrap-datepicker-rails project integrates a datepicker with Rails 3 assets pipeline. and run bundle install.

jekyll-asset-pipeline

  •    Ruby

Powerful asset pipeline for Jekyll that collects, converts and compresses JavaScript and CSS assets

connect-assetmanager - Middleware for Connect (node.js) for handling your static assets.

  •    Javascript

Middleware for Connect (node.js) for handling your static assets. The path to the folder containing the files.





We have large collection of open source products. Follow the tags from Tag Cloud >>


Open source products are scattered around the web. Please provide information about the open source projects you own / you use. Add Projects.