requirejs_optimizer 0.0.5

data/spec/lib/requirejs_optimizer/step/digestify_spec.rb

@@ -0,0 +1,70 @@
+require 'spec_helper'
+
+module RequirejsOptimizer
+
+  module Step
+
+    describe Digestify do
+
+      before do
+        # Disconnect fileutils
+        FileUtils.stub(:cp)
+        Rails.application.assets.stub(:file_digest).and_return(stub(hexdigest: 'abcdefg'))
+      end
+
+      describe "#initialize" do
+
+        subject { Digestify }
+
+        context "when assets have already been initialized" do
+          before { Rails.application.stub(:assets).and_return("present") }
+
+          it "doesn't re-initialize assets" do
+            Rails.application.should_not_receive(:initialize!)
+            subject.new
+          end
+        end
+
+        context "when assets haven't yet been initialized" do
+          before { Rails.application.stub(:assets).and_return(nil) }
+
+          it "initializes assets" do
+            Rails.application.should_receive(:initialize!).with(:assets)
+            subject.new
+          end
+        end
+
+      end
+
+      describe '#perform' do
+
+        it "makes digestified versions of all js and css files" do
+          Dir.should_receive(:glob).with(target_path_for("**", "*.*")).and_return(%w(file.css file.js file.png))
+          subject.should_receive(:digestify_file).once.with("file.css")
+          subject.should_receive(:digestify_file).once.with("file.js")
+          subject.should_receive(:digestify_file).once.with("file.png")
+          subject.perform
+        end
+
+      end
+
+      describe '#digestify_file' do
+
+        it "copies a digested file into place" do
+          FileUtils.should_receive(:cp).with("foo.css", "foo-abcdefg.css")
+          subject.digestify_file("foo.css")
+
+          FileUtils.should_receive(:cp).with("foo.js", "foo-abcdefg.js")
+          subject.digestify_file("foo.js")
+
+          FileUtils.should_receive(:cp).with("foo.png", "foo-abcdefg.png")
+          subject.digestify_file("foo.png")
+        end
+
+      end
+
+    end
+
+  end
+
+end

data/spec/lib/requirejs_optimizer/step/finalize_spec.rb

@@ -0,0 +1,33 @@
+require 'spec_helper'
+
+module RequirejsOptimizer
+
+  module Step
+
+    describe Finalize do
+
+      before do
+        # disconnect file system modifications
+        FileUtils.stub(:rm_r)
+        FileUtils.stub(:cp_r)
+      end
+
+      describe '#perform' do
+
+        it "removes the current public/assets directory" do
+          FileUtils.should_receive(:rm_r).with(Rails.root.join("public/assets"))
+          subject.perform
+        end
+
+        it "copies the build target to public/assets" do
+          FileUtils.should_receive(:cp_r).with(RequirejsOptimizer.target_dir.to_s, Rails.root.join("public", "assets"))
+          subject.perform
+        end
+
+      end
+
+    end
+
+  end
+
+end

data/spec/lib/requirejs_optimizer/step/manifest_spec.rb

@@ -0,0 +1,37 @@
+require 'spec_helper'
+
+module RequirejsOptimizer
+
+  module Step
+
+    describe Manifest do
+
+      before do
+        # disconnect IO
+        subject.stub(:write_manifest)
+      end
+
+      describe '#perform' do
+
+        before do
+          Dir.should_receive(:glob).with(target_path_for("**", "*.*")).and_return(%w(file.css file-0123456789abcdef0123456789abcdef.css other/file.js other/file-0123456789abcdef0123456789abcdef.js))
+        end
+
+        it "properly generates manifest entries" do
+          subject.should_receive(:manifest_entry_for).once.with('file-0123456789abcdef0123456789abcdef.css')
+          subject.should_receive(:manifest_entry_for).once.with('other/file-0123456789abcdef0123456789abcdef.js')
+          subject.perform
+        end
+
+        it "writes the manifest file to the appropriate place" do
+          subject.should_receive(:write_manifest).with("file.css: file-0123456789abcdef0123456789abcdef.css\nother/file.js: other/file-0123456789abcdef0123456789abcdef.js")
+          subject.perform
+        end
+
+      end
+
+    end
+
+  end
+
+end

data/spec/lib/requirejs_optimizer/step/optimize_spec.rb

@@ -0,0 +1,42 @@
+require 'spec_helper'
+
+module RequirejsOptimizer
+
+  module Step
+
+    describe Optimize do
+
+      describe "#perform" do
+
+        before { subject.stub(:node_exists).and_return(true) }
+
+        it "raises an error if node is missing" do
+          subject.stub(:node_exists?).and_return(false)
+          expect {
+            subject.perform
+          }.to raise_error RequirejsOptimizer::Errors::NodeUnavailable
+        end
+
+        describe "optimization" do
+
+          context "when unsuccessful" do
+
+            before { subject.stub(:optimize).and_return(false) }
+
+            it "raises an error" do
+              expect {
+                subject.perform
+              }.to raise_error RequirejsOptimizer::Errors::RjsOptimizationFailed
+            end
+
+          end
+
+        end
+
+      end
+
+    end
+
+  end
+
+end

data/spec/lib/requirejs_optimizer/step/prepare_spec.rb

@@ -0,0 +1,53 @@
+require 'spec_helper'
+
+module RequirejsOptimizer
+
+  module Step
+
+    describe Prepare do
+
+      describe '#perform' do
+
+        before do
+          # Disconnect all the fileutils stuff
+          FileUtils.stub(:cp_r)
+          FileUtils.stub(:rm)
+        end
+
+        describe "build directory preparation" do
+
+          before do
+            RequirejsOptimizer.stub(:build_dir).and_return(Pathname.new("foo"))
+            Rails.stub(:root).and_return Pathname.new("root")
+          end
+
+          it "copies public/assets to the build dir" do
+            FileUtils.should_receive(:cp_r).with("root/public/assets", "foo")
+            subject.perform
+          end
+
+        end
+
+        it "removes digestified js and css files" do
+          subject.stub(:remove_gzipped_files)
+
+          Dir.should_receive(:glob).with(build_path_for("**", "*.*")).and_return(%w(file.css file-0123456789abcdef0123456789abcdef.css))
+          FileUtils.should_receive(:rm).with "file-0123456789abcdef0123456789abcdef.css"
+          subject.perform
+        end
+
+        it "removes gzipped files" do
+          subject.stub(:remove_digestified_files)
+
+          Dir.stub(:glob).with(build_path_for("**", "*.gz")).and_return ["thing"]
+          FileUtils.should_receive(:rm).with ["thing"]
+          subject.perform
+        end
+
+      end
+
+    end
+
+  end
+
+end

data/spec/lib/requirejs_optimizer_spec.rb

@@ -0,0 +1,24 @@
+require 'spec_helper'
+
+describe RequirejsOptimizer do
+
+  describe 'module attributes' do
+
+    before do
+      RequirejsOptimizer.build_dir = "tmp/foo"
+    end
+
+    its(:build_dir) { should == Rails.root.join("tmp/foo") }
+
+    describe "build_dir" do
+
+      it "should be `tmp/assets` by default" do
+        RequirejsOptimizer.build_dir = nil
+        RequirejsOptimizer.build_dir.should == Rails.root.join("tmp/assets")
+      end
+
+    end
+
+  end
+
+end

data/spec/rails_app/.gitignore

@@ -0,0 +1,15 @@
+# See http://help.github.com/ignore-files/ for more about ignoring files.
+#
+# If you find yourself ignoring temporary files generated by your text editor
+# or operating system, you probably want to add a global ignore instead:
+#   git config --global core.excludesfile ~/.gitignore_global
+
+# Ignore bundler config
+/.bundle
+
+# Ignore the default SQLite database.
+/db/*.sqlite3
+
+# Ignore all logfiles and tempfiles.
+/log/*.log
+/tmp

data/spec/rails_app/README.rdoc

@@ -0,0 +1,261 @@
+== Welcome to Rails
+
+Rails is a web-application framework that includes everything needed to create
+database-backed web applications according to the Model-View-Control pattern.
+
+This pattern splits the view (also called the presentation) into "dumb"
+templates that are primarily responsible for inserting pre-built data in between
+HTML tags. The model contains the "smart" domain objects (such as Account,
+Product, Person, Post) that holds all the business logic and knows how to
+persist themselves to a database. The controller handles the incoming requests
+(such as Save New Account, Update Product, Show Post) by manipulating the model
+and directing data to the view.
+
+In Rails, the model is handled by what's called an object-relational mapping
+layer entitled Active Record. This layer allows you to present the data from
+database rows as objects and embellish these data objects with business logic
+methods. You can read more about Active Record in
+link:files/vendor/rails/activerecord/README.html.
+
+The controller and view are handled by the Action Pack, which handles both
+layers by its two parts: Action View and Action Controller. These two layers
+are bundled in a single package due to their heavy interdependence. This is
+unlike the relationship between the Active Record and Action Pack that is much
+more separate. Each of these packages can be used independently outside of
+Rails. You can read more about Action Pack in
+link:files/vendor/rails/actionpack/README.html.
+
+
+== Getting Started
+
+1. At the command prompt, create a new Rails application:
+       <tt>rails new myapp</tt> (where <tt>myapp</tt> is the application name)
+
+2. Change directory to <tt>myapp</tt> and start the web server:
+       <tt>cd myapp; rails server</tt> (run with --help for options)
+
+3. Go to http://localhost:3000/ and you'll see:
+       "Welcome aboard: You're riding Ruby on Rails!"
+
+4. Follow the guidelines to start developing your application. You can find
+the following resources handy:
+
+* The Getting Started Guide: http://guides.rubyonrails.org/getting_started.html
+* Ruby on Rails Tutorial Book: http://www.railstutorial.org/
+
+
+== Debugging Rails
+
+Sometimes your application goes wrong. Fortunately there are a lot of tools that
+will help you debug it and get it back on the rails.
+
+First area to check is the application log files. Have "tail -f" commands
+running on the server.log and development.log. Rails will automatically display
+debugging and runtime information to these files. Debugging info will also be
+shown in the browser on requests from 127.0.0.1.
+
+You can also log your own messages directly into the log file from your code
+using the Ruby logger class from inside your controllers. Example:
+
+  class WeblogController < ActionController::Base
+    def destroy
+      @weblog = Weblog.find(params[:id])
+      @weblog.destroy
+      logger.info("#{Time.now} Destroyed Weblog ID ##{@weblog.id}!")
+    end
+  end
+
+The result will be a message in your log file along the lines of:
+
+  Mon Oct 08 14:22:29 +1000 2007 Destroyed Weblog ID #1!
+
+More information on how to use the logger is at http://www.ruby-doc.org/core/
+
+Also, Ruby documentation can be found at http://www.ruby-lang.org/. There are
+several books available online as well:
+
+* Programming Ruby: http://www.ruby-doc.org/docs/ProgrammingRuby/ (Pickaxe)
+* Learn to Program: http://pine.fm/LearnToProgram/ (a beginners guide)
+
+These two books will bring you up to speed on the Ruby language and also on
+programming in general.
+
+
+== Debugger
+
+Debugger support is available through the debugger command when you start your
+Mongrel or WEBrick server with --debugger. This means that you can break out of
+execution at any point in the code, investigate and change the model, and then,
+resume execution! You need to install ruby-debug to run the server in debugging
+mode. With gems, use <tt>sudo gem install ruby-debug</tt>. Example:
+
+  class WeblogController < ActionController::Base
+    def index
+      @posts = Post.all
+      debugger
+    end
+  end
+
+So the controller will accept the action, run the first line, then present you
+with a IRB prompt in the server window. Here you can do things like:
+
+  >> @posts.inspect
+  => "[#<Post:0x14a6be8
+          @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>,
+       #<Post:0x14a6620
+          @attributes={"title"=>"Rails", "body"=>"Only ten..", "id"=>"2"}>]"
+  >> @posts.first.title = "hello from a debugger"
+  => "hello from a debugger"
+
+...and even better, you can examine how your runtime objects actually work:
+
+  >> f = @posts.first
+  => #<Post:0x13630c4 @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>
+  >> f.
+  Display all 152 possibilities? (y or n)
+
+Finally, when you're ready to resume execution, you can enter "cont".
+
+
+== Console
+
+The console is a Ruby shell, which allows you to interact with your
+application's domain model. Here you'll have all parts of the application
+configured, just like it is when the application is running. You can inspect
+domain models, change values, and save to the database. Starting the script
+without arguments will launch it in the development environment.
+
+To start the console, run <tt>rails console</tt> from the application
+directory.
+
+Options:
+
+* Passing the <tt>-s, --sandbox</tt> argument will rollback any modifications
+  made to the database.
+* Passing an environment name as an argument will load the corresponding
+  environment. Example: <tt>rails console production</tt>.
+
+To reload your controllers and models after launching the console run
+<tt>reload!</tt>
+
+More information about irb can be found at:
+link:http://www.rubycentral.org/pickaxe/irb.html
+
+
+== dbconsole
+
+You can go to the command line of your database directly through <tt>rails
+dbconsole</tt>. You would be connected to the database with the credentials
+defined in database.yml. Starting the script without arguments will connect you
+to the development database. Passing an argument will connect you to a different
+database, like <tt>rails dbconsole production</tt>. Currently works for MySQL,
+PostgreSQL and SQLite 3.
+
+== Description of Contents
+
+The default directory structure of a generated Ruby on Rails application:
+
+  |-- app
+  |   |-- assets
+  |       |-- images
+  |       |-- javascripts
+  |       `-- stylesheets
+  |   |-- controllers
+  |   |-- helpers
+  |   |-- mailers
+  |   |-- models
+  |   `-- views
+  |       `-- layouts
+  |-- config
+  |   |-- environments
+  |   |-- initializers
+  |   `-- locales
+  |-- db
+  |-- doc
+  |-- lib
+  |   `-- tasks
+  |-- log
+  |-- public
+  |-- script
+  |-- test
+  |   |-- fixtures
+  |   |-- functional
+  |   |-- integration
+  |   |-- performance
+  |   `-- unit
+  |-- tmp
+  |   |-- cache
+  |   |-- pids
+  |   |-- sessions
+  |   `-- sockets
+  `-- vendor
+      |-- assets
+          `-- stylesheets
+      `-- plugins
+
+app
+  Holds all the code that's specific to this particular application.
+
+app/assets
+  Contains subdirectories for images, stylesheets, and JavaScript files.
+
+app/controllers
+  Holds controllers that should be named like weblogs_controller.rb for
+  automated URL mapping. All controllers should descend from
+  ApplicationController which itself descends from ActionController::Base.
+
+app/models
+  Holds models that should be named like post.rb. Models descend from
+  ActiveRecord::Base by default.
+
+app/views
+  Holds the template files for the view that should be named like
+  weblogs/index.html.erb for the WeblogsController#index action. All views use
+  eRuby syntax by default.
+
+app/views/layouts
+  Holds the template files for layouts to be used with views. This models the
+  common header/footer method of wrapping views. In your views, define a layout
+  using the <tt>layout :default</tt> and create a file named default.html.erb.
+  Inside default.html.erb, call <% yield %> to render the view using this
+  layout.
+
+app/helpers
+  Holds view helpers that should be named like weblogs_helper.rb. These are
+  generated for you automatically when using generators for controllers.
+  Helpers can be used to wrap functionality for your views into methods.
+
+config
+  Configuration files for the Rails environment, the routing map, the database,
+  and other dependencies.
+
+db
+  Contains the database schema in schema.rb. db/migrate contains all the
+  sequence of Migrations for your schema.
+
+doc
+  This directory is where your application documentation will be stored when
+  generated using <tt>rake doc:app</tt>
+
+lib
+  Application specific libraries. Basically, any kind of custom code that
+  doesn't belong under controllers, models, or helpers. This directory is in
+  the load path.
+
+public
+  The directory available for the web server. Also contains the dispatchers and the
+  default HTML files. This should be set as the DOCUMENT_ROOT of your web
+  server.
+
+script
+  Helper scripts for automation and generation.
+
+test
+  Unit and functional tests along with fixtures. When using the rails generate
+  command, template test files will be generated for you and placed in this
+  directory.
+
+vendor
+  External libraries that the application depends on. Also includes the plugins
+  subdirectory. If the app has frozen rails, those gems also go here, under
+  vendor/rails/. This directory is in the load path.

data/spec/rails_app/Rakefile

@@ -0,0 +1,7 @@
+#!/usr/bin/env rake
+# Add your own tasks in files placed in lib/tasks ending in .rake,
+# for example lib/tasks/capistrano.rake, and they will automatically be available to Rake.
+
+require File.expand_path('../config/application', __FILE__)
+
+RailsApp::Application.load_tasks

data/spec/rails_app/app/assets/javascripts/application.js

@@ -0,0 +1,15 @@
+// This is a manifest file that'll be compiled into application.js, which will include all the files
+// listed below.
+//
+// Any JavaScript/Coffee file within this directory, lib/assets/javascripts, vendor/assets/javascripts,
+// or vendor/assets/javascripts of plugins, if any, can be referenced here using a relative path.
+//
+// It's not advisable to add code directly here, but if you do, it'll appear at the bottom of the
+// the compiled file.
+//
+// WARNING: THE FIRST BLANK LINE MARKS THE END OF WHAT'S TO BE PROCESSED, ANY BLANK LINE SHOULD
+// GO AFTER THE REQUIRES BELOW.
+//
+//= require jquery
+//= require jquery_ujs
+//= require_tree .

data/spec/rails_app/app/assets/javascripts/modules/bar/two.coffee

@@ -0,0 +1,2 @@
+define ->
+  {foo: "one"}

data/spec/rails_app/app/assets/javascripts/modules/baz/three.coffee

@@ -0,0 +1,2 @@
+define ->
+  {baz: "three"}

data/spec/rails_app/app/assets/javascripts/modules/foo/one.coffee

@@ -0,0 +1,2 @@
+define ->
+  {bar: "two"}

data/spec/rails_app/app/assets/javascripts/modules/main.coffee

@@ -0,0 +1 @@
+require ["foo/one", "bar/two", "baz/three"]

data/spec/rails_app/app/assets/javascripts/modules/require.build.js

@@ -0,0 +1,6 @@
+({
+    appDir:    "../../../../tmp/assets"
+    , baseUrl: "./modules"
+    , dir:     "../../../../tmp/assets/build"
+    , name:    "main"
+})

data/spec/rails_app/app/assets/stylesheets/application.css

@@ -0,0 +1,13 @@
+/*
+ * This is a manifest file that'll be compiled into application.css, which will include all the files
+ * listed below.
+ *
+ * Any CSS and SCSS file within this directory, lib/assets/stylesheets, vendor/assets/stylesheets,
+ * or vendor/assets/stylesheets of plugins, if any, can be referenced here using a relative path.
+ *
+ * You're free to add application-wide styles to this file and they'll appear at the top of the
+ * compiled file, but it's generally better to create a new file per style scope.
+ *
+ *= require_self
+ *= require_tree .
+*/

data/spec/rails_app/app/controllers/application_controller.rb

@@ -0,0 +1,3 @@
+class ApplicationController < ActionController::Base
+  protect_from_forgery
+end

data/spec/rails_app/app/helpers/application_helper.rb

@@ -0,0 +1,2 @@
+module ApplicationHelper
+end

data/spec/rails_app/app/views/layouts/application.html.erb

@@ -0,0 +1,14 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <title>RailsApp</title>
+  <%= stylesheet_link_tag    "application", :media => "all" %>
+  <%= javascript_include_tag "application" %>
+  <%= csrf_meta_tags %>
+</head>
+<body>
+
+<%= yield %>
+
+</body>
+</html>