sprockets

Long time Rails[1] user. Have discovered Npm[2], Bower[3], Grunt[4], Yeoman[5] recently. How do I get these excellent tools to play nicely with the Rails ecosystem[6]? Notably Sprockets[7] and Grunt do not seem to see eye to eye? What strategies have you used? Would love to know. [1] http://rubyonrails.org/ [2] https://www.npmjs.org/ [3] http://bower.io/ [4] http://gruntjs.com/ [5] http://yeoman.io/ [6] http://guides.rubyonrails.org/asset_pipeline.html [7] https://github.com/sstephenson/sprockets

I was really curious to see the pull request, so I hunted it down: https://github.com/sstephenson/sprockets/issues/506 Edit: if you just want to install a gem and skip the why, the parent has this blog post: https://www.coffeepowered.net/2014/02/09/faster-pathname/

This looks like a solid project. I want to mention mincer[1], which I have used in the past for compiling assets, and it has been an entirely painless process. Definitely take a look at it as an alternative, which has been around longer and has seen assistance from the folks behind sprockets[2] (according to the README) for creating a similar API. 1. https://github.com/nodeca/mincer 2. https://github.com/sstephenson/sprockets

Broccoli is a new build tool. It’s comparable to the Rails asset pipeline in scope, though it runs on Node and is backend-agnostic. This first line is a little disingenuous. Technically, it's not backend-agnostic, since it depends on Node being installed on the backend (in the same way that Sprockets [1] depends on Ruby). The Rails asset pipeline is a framework-specific integration of Sprockets. In much the same way, you could more closely integrate Broccoli with Rails if you wanted and call it a new Rails asset pipeline. The project itself looks great, just the first line was confusing since they started the docs off by comparing apples to oranges. A better comparison would probably be, "It's comparable to Sprockets (which powers the Rails asset pipeline), but runs on Node instead of Ruby." [1] https://github.com/sstephenson/sprockets

I've done a bit of work to flesh out the jQuery integration in our fork of the airbrake notifier, to automatically wrap all event handlers and AJAX callbacks. Which is great, because it means our entire Backbone app gets a full stack trace with line and column numbers. I should really submit a pull request. Also very excited about the proposals about having the error object passed to window.onerror... well, I used to be. I've had a little bit of involvement in the W3C mailing lists over the last few years, but it seems like nothing ever gets done. And source maps support would be awesome! Just as soon as we can get source maps from sprockets, which seems like it's on the way [1]. [1] https://github.com/sstephenson/sprockets/pull/311

As other commenters have mentioned, Source Maps are the solution to this problem in general. The main reason we don't yet allow signup to RescueJS is that "create a source map" is currently beyond the state of the art for web frameworks. You can't "just" do it. Over the weekend we spent a few hours trying to hook source maps into the asset pipeline for Rails based on https://github.com/sstephenson/sprockets/pull/311 and upgrading the 'uglifier' rubygem to work with UglifyJS2. We didn't manage to get it quite working within the time limit, but we'll try and push our work-in-progress upstream to get this ball moving again.

Happens already. Two examples: 1. Internet Explorer has conditional comments - http://msdn.microsoft.com/en-us/library/ms537512%28v=vs.85%2... 2. Sprockets' directive processor uses directives in comments. https://github.com/sstephenson/sprockets

Similarly, we concatenate our JS with sprockets[0] -- so what's on line 50 of module.js in the pre-compiled code base may be on line 1350 of app.js in the browser. 0 : https://github.com/sstephenson/sprockets

There have been several issues with Sass (sass-rails) and the Asset Pipeline. Some of them involving Compass (https://github.com/chriseppstein/compass/issues/516#issuecom...), some of them due to Sprockets (https://github.com/sstephenson/sprockets/pull/268#issuecomme...). They have indeed been crippling for front-end development, and majorly under-reported since this summer. So if you're facing any of these issues, please participate in the GitHub Issues threads I linked above and help the relevant teams diagnose/improve the problems.

I prefer Sprockets (rails asset pipeline, https://github.com/sstephenson/sprockets), which is Rack based..

Sprockets includes Jammit-inspired JST support. You can use it with either EJS or Eco templates. See the "JavaScript Templating" section of the readme: https://github.com/sstephenson/sprockets#readme You can even write your own JST template class. Here's an example that adds Mustache template support: https://github.com/josh/mustache-trimmer/blob/master/lib/til...

The coffee-script gem (https://github.com/josh/ruby-coffee-script) uses ExecJS (https://github.com/sstephenson/execjs) to invoke the CS compiler. Rails 3.1's asset pipelining system will use these gems by way of Sprockets 2 (https://github.com/sstephenson/sprockets) to compile and serve CoffeeScript to the browser. If you're on Windows or Mac OS, ExecJS will use the JS runtime already installed on your system (Windows Script Host or Apple JavaScriptCore). You can also install a gem like therubyracer (V8 for MRI, available on Heroku) or therubyrhino (Rhino for JRuby) for faster compilation. And ExecJS can use Node.js or Spidermonkey if they're installed too.

Sprockets looks promising if you're using Ruby. Haven't had a chance to use it in a project yet. http://github.com/sstephenson/sprockets