Kinda support manifest.compile with simple path by josh · Pull Request #12 · rails/sprockets
Theres been a few issues around Manifest#compile targeting assets using transformers. https://github.com/josh/sprockets-es6/issues/9 Sprockets 3.0.0.rc QA #10 (comment) The issue has to do with how 2.x and 3.x implement manifest.compile. To support arbitrary procs and fnmatch syntax, sprockets has to iterate over every darn file in the load path to check it against these filters. Its terribly slow
Gulpfile for Rails application with replaced Sprockets with Gulp
Gulpfile.js �G ��U 0�D��U 'use strict' var gulp, sass, babelify, browserify, watchify, source, util; gulp = require('gulp'); sass = require('gulp-sass'); babelify = require('babelify') browserify = require('browserify'); watchify = require('watchify'); source = require('vinyl-source-stream'); util = require('gulp-util'); var sassPath, sassSource, jsSource; sassPath = './app/assets/stylesheets/**/*
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Loading sprockets is too slow · Issue #17 · rails/sprockets
Sprockets 3.0.0 release · Issue #16 · rails/sprockets
Inability to compile nondigest and digest assets breaks compatibility with bad gems · Issue #49 · rails/sprockets-rails
sprockets/lib/sprockets/manifest.rb at main · rails/sprockets
GitHub - sstephenson/sprockets: Rack-based asset packaging system
