sprockets-browserify 0.2.0 → 0.3.0

data/node_modules/browserify/node_modules/url/node_modules/punycode/vendor/requirejs/docs/errors.html

@@ -0,0 +1,155 @@
+<div id="directory" class="section">
+<h1>Common Errors</h1>
+
+<ul class="index mono">
+<li class="hbox"><a href="#mismatch">Mismatched anonymous define() modules ...</a><span class="spacer boxFlex"></span><span class="sect">&sect; 1</span></li>
+<li class="hbox"><a href="#timeout">Load timeout for modules: ...</a><span class="spacer boxFlex"></span><span class="sect">&sect; 2</span></li>
+<li class="hbox"><a href="#defineerror">Error evaluating module ...</a><span class="spacer boxFlex"></span><span class="sect">&sect; 3</span></li>
+<li class="hbox"><a href="#notloaded">Module name ... has not been loaded yet for context: ...</a><span class="spacer boxFlex"></span><span class="sect">&sect; 4</span></li>
+<li class="hbox"><a href="#requireargs">Invalid require call</a><span class="spacer boxFlex"></span><span class="sect">&sect; 5</span></li>
+<li class="hbox"><a href="#interactive">No matching script interactive for ...</a><span class="spacer boxFlex"></span><span class="sect">&sect; 6</span></li>
+<li class="hbox"><a href="#pathnotsupported">Path is not supported: ...</a><span class="spacer boxFlex"></span><span class="sect">&sect; 7</span></li>
+</ul>
+
+<p>This page lists errors that are generated by RequireJS. If the following information does not fix the problem, you can ask on the <a href="https://groups.google.com/group/requirejs">RequireJS list</a> or <a href="https://github.com/jrburke/requirejs/issues">open an issue</a>. In either case it is best to have an example or detailed explanation of the problem, hopefully with steps to reproduce.</p>
+
+</div>
+
+<div class="section">
+<h2><a name="mismatch">Mismatched anonymous define() modules ...</a><span class="sectionMark">&sect; 1</span></h2>
+
+<p>If you manually code a script tag in HTML to load a script with an anonymous define() call, this error can occur.</p>
+
+<p>Also seen if you manually code a script tag in HTML to load a script that has a few named modules, but then try to load an anonymous module that ends up having the same name as one of the named modules in the script loaded by the manually coded script tag.</p>
+
+<p>Finally, if you use the loader plugins or anonymous modules (modules that call define() with no string ID) but do not use the RequireJS optimizer to combine files together, this error can occur. The optimizer knows how to name anonymous modules correctly so that they can be combined with other modules in an optimized file.</p>
+
+<p>To avoid the error:</p>
+
+<ul>
+    <li>Be sure to load all scripts that call define() via the RequireJS API. Do not manually code script tags in HTML to load scripts that have define() calls in them.</li>
+    <li>If you manually code an HTML script tag, be sure it only includes named modules, and that an anonymous module that will have the same name as one of the modules in that file is not loaded.</li>
+    <li>If the problem is the use of loader plugins or anonymous modules but the RequireJS optimizer is not used for file bundling, use the RequireJS optimizer.</li>
+</ul>
+
+</div>
+
+
+<div class="section">
+<h2><a name="timeout">Load timeout for modules: ...</a><span class="sectionMark">&sect; 2</span></h2>
+
+<p>Likely causes and fixes:</p>
+
+<ul>
+    <li>There was a script error in one of the listed modules. If there is no script error in the browser's error console, and if you are using Firebug, try loading the page in another browser like Chrome or Safari. Sometimes script errors do not show up in Firebug.</li>
+    <li>The path configuration for a module is incorrect. Check the "Net" or "Network" tab in the browser's developer tools to see if there was a 404 for an URL that would map to the module name. Make sure the script file is in the right place. In some cases you may need to use the <a href="api.html#config">paths configuration</a> to fix the URL resolution for the script.</li>
+</ul>
+
+</div>
+
+
+<div class="section">
+<h2><a name="defineerror">Error evaluating module ...</a><span class="sectionMark">&sect; 3</span></h2>
+
+<p>An error occured when the define() function was called for the module given in the error message. It is an error with the code logic inside the define function. The error could happen inside a require callback.</p>
+
+<p>In Firefox and WebKit browsers, a line number and file name will be indicated in the error. It can be used to locate
+the source of the problem. Better isolation of the error can be done by using a debugger to place a
+breakpoint in the file that contains the error.</p>
+
+</div>
+
+<div class="section">
+<h2><a name="notloaded">Module name ... has not been loaded yet for context: ...</a><span class="sectionMark">&sect; 4</span></h2>
+
+<p>This occurs when there is is a require('name') call, but the 'name' module has not been loaded yet.</p>
+
+<p>If you are using the simplified define wrapper, make sure you have <strong>require</strong> as the first argument to the definition function:</p>
+
+<pre><code>define(function (require) {
+    var namedModule = require('name');
+});
+</code></pre>
+
+<p>If you are listing dependencies in the dependency array, make sure that <strong>require</strong> and <strong>name</strong> are in the dependency array:</p>
+
+<pre><code>define(['require', 'name'], function (require) {
+    var namedModule = require('name');
+});
+</code></pre>
+
+<p>Or, if part of a require() callback:</p>
+
+<pre><code>require(['require', 'name'], function (require) {
+    var namedModule = require('name');
+});
+</code></pre>
+
+<p>Be sure that <strong>require('name')</strong> only occurs inside a define() definition function or a require() callback function, never in the global space by its own.</p>
+
+</div>
+
+
+<div class="section">
+<h2><a name="requireargs">Invalid require call</a><span class="sectionMark">&sect; 4</span></h2>
+
+<p>This occurs when there is is a call like:</p>
+
+<pre><code>require('dependency', function (dependency) {});
+</code></pre>
+
+<p>Asynchronously loading dependencies should use an array to list the dependencies:</p>
+
+<pre><code>require(['dependency'], function (dependency) {});
+</code></pre>
+
+</div>
+
+<div class="section">
+<h2><a name="interactive">No matching script interactive for ...</a><span class="sectionMark">&sect; 6</span></h2>
+
+<p>This error only shows up in some IE browsers. Most likely caused by loading a script that calls define() but was loaded in a plain script tag or via some other call, like an eval() of a JavaScript string.</p>
+
+<p>To avoid the error, be sure to load all scripts that call define via the RequireJS API.</p>
+
+</div>
+
+<div class="section">
+<h2><a name="pathnotsupported">Path is not supported: ...</a><span class="sectionMark">&sect; 7</span></h2>
+
+<p>This error occurs when the optimizer encounters a path to a module or script which is a network path. The optimizer only allows
+building with local resources. To fix it:</p>
+
+<p>Make sure you reference the network dependency as a module name, not as a full URL, so that it can be mapped to a different
+during the build:</p>
+
+
+<pre><code>//DO NOT DO THIS
+require(['http://some.domain.dom/path/to/dependency.js'],
+function (dependency) {});
+
+//Rather, do this:
+require.config({
+    paths: {
+        'dependency': 'http://some.domain.dom/path/to/dependency'
+    }
+});
+
+require(['dependency'], function (dependency) {});
+</code></pre>
+
+<p>If you want to include this dependency in the built/optimized file, download the JS file and in the
+build profile for the optimizer, put in a paths config that points to that local file.</p>
+
+<p>If you want to <b>exclude</b> that file from being included, and just need to map "dependency"
+for the build (otherwise it will not build), then use the special "empty:" paths config:</p>
+
+<pre><code>//Inside the build profile
+{
+    paths: {
+        'dependency': 'empty:'
+    }
+}
+</code></pre>
+
+</div>

data/node_modules/browserify/node_modules/url/node_modules/punycode/vendor/requirejs/docs/faq-advanced.html

@@ -0,0 +1,136 @@
+<div id="directory" class="section">
+<h1>FAQ: RequireJS Advanced Usage</h1>
+
+<ul class="index mono">
+<li class="hbox"><a href="#rename">How can I rename require?</a><span class="spacer boxFlex"></span><span class="sect">&sect; 1</span></li>
+<li class="hbox"><a href="#css">What about loading CSS?</a><span class="spacer boxFlex"></span><span class="sect">&sect; 2</span></li>
+</ul>
+</div>
+
+<div class="section">
+<h2><a name="rename">How can I rename require/define/requirejs?</a><span class="sectionMark">&sect; 1</span></h2>
+
+<p>RequireJS and its optimization tool need to be version 0.26.0 or higher for this to work.</p>
+
+<p>Why would you want to do this? You may have very strict global namespace requirements
+or you may be using code that already defines require/define and you want to avoid interference.</p>
+
+<p>Some notes on this capability:</p>
+
+<ul>
+    <li>Make sure to use a source version of require.js, not a minified version.</li>
+    <li>Make sure that version of require.js is included in the optimization because the require.js
+    file contents are altered for the namespacing to work.</li>
+    <li>Code your modules using require/define as normal, then do a build to namespace the values.
+    Do not code your modules using the namespaced require/define. It will make your code less
+    portable and usable by others.</li>
+    <li>This transformation/optimization only works once. Do not use the output of this optimization as
+    input to another optimization/build stage.</li>
+</ul>
+
+<p>The following example optimization config is based on the directory structure
+used in the example on the <a href="optimization.html"> optimization page</a>. This config combines
+require.js with main.js into a new <strong>foo.js</strong>. file. define() is renamed to <strong>foo.define()</strong>
+and require() is renamed to <strong>foo.require()</strong>:</p>
+
+<pre><code>
+{
+    appDir: "../",
+    baseUrl: "scripts",
+    dir: "../../appdirectory-build",
+
+    //Put in a mapping so that 'requireLib' in the
+    //modules section below will refer to the require.js
+    //contents.
+    paths: {
+        requireLib: 'require'
+    },
+
+    //Indicates the namespace to use for require/requirejs/define.
+    namespace: "foo",
+
+    modules: [
+        {
+            name: "foo",
+            include: ["requireLib", "main"],
+            //True tells the optimizer it is OK to create
+            //a new file foo.js. Normally the optimizer
+            //wants foo.js to exist in the source directory.
+            create: true
+        }
+    ]
+}
+</code></pre>
+
+
+<p>Once this optimization is done, the HTML that used to refer to require.js would
+need to be modified to refer to foo.js.</p>
+
+<p>Thanks to <a href="http://ryanflorence.com">Ryan Florence</a> for help on the namespace design.</p>
+
+<hr>
+
+<p>Another approach to renaming, if you prefer to have more direct control of the content, and
+want to commit source code with the modifications. This approach <strong>should not be used</strong>
+with the "namespace" optimization demonstrated above.</p>
+
+<div class="subSection">
+<h4>1) Modify the source of require.js</h4>
+
+<p>There needs to be a wrapper around the require.js code so you can set the require function to the name of your choosing:</p>
+
+<pre><code>var myGlobalRequire = (function () {
+    //Define a require object here that has any
+    //default configuration you want for RequireJS. If
+    //you do not have any config options you want to set,
+    //just use an simple object literal, {}. You may need
+    //to at least set baseUrl.
+    var require = {
+        baseUrl: '..'
+    };
+
+    //INSERT require.js CONTENTS HERE
+
+    return require;
+}());
+</code></pre>
+</div>
+
+<div class="subSection">
+<h4>2) Modify loaded files</h4>
+
+<p>For any files you load with this new function, if those files reference require in any way, you will want to wrap them in an anonymous function to set the value of require to be your new function name that you set up in step 1:</p>
+
+<pre><code>(function (require) {
+
+    //Regular require references now work correctly in here.
+
+}(myGlobalRequire));
+</code></pre>
+
+<p>Following the steps above should allow you to use the optimization tool to combine scripts together effectively. If you want your renamed require definition in the optimized script, reference your modified require.js directly in the <strong>include</strong> optimization option, or as the <strong>name</strong> option if you want to optimize that file directly.</p>
+
+<p>Thanks to <a href="http://alexsexton.com/">Alex Sexton</a> and <a href="http://tobielangel.com/">Tobie Langel</a> for suggesting parts of this solution.</p>
+</div>
+</div>
+
+<div class="section">
+<h2><a name="css">What about loading CSS?</a><span class="sectionMark">&sect; 2</span></h2>
+
+<p>Ideally RequireJS could load CSS files as dependencies. However, there are issues knowing when a CSS file has been loaded, particularly in Gecko/Firefox when the file is loaded from another domain. Some history can be found in <a href="http://bugs.dojotoolkit.org/ticket/5402">this Dojo ticket</a>.</p>
+
+<p>Knowing when the file is loaded  is important because you may only want to grab the dimensions of a DOM element once the style sheet has loaded.</p>
+
+<p>Some people have implemented an approach where they look for a well known style to be applied to a specific HTML element to know if a style sheet is loaded. Due to the specificity of that solution, it is not something that would fit will with RequireJS. Knowing when the link element has loaded the referenced file would be the most robust solution.</p>
+
+<p>Since knowing when the file has loaded is not reliable, it does not make sense to explicitly support CSS files in RequireJS loading, since it will lead to bug reports due to browser behavior. If you do not care when the file is loaded, you can easily write your own function to load CSS on demand by doing the following:</p>
+
+<pre><code>function loadCss(url) {
+    var link = document.createElement("link");
+    link.type = "text/css";
+    link.rel = "stylesheet";
+    link.href = url;
+    document.getElementsByTagName("head")[0].appendChild(link);
+}
+</code></pre>
+</div>

data/node_modules/browserify/node_modules/url/node_modules/punycode/vendor/requirejs/docs/faq-optimization.html

@@ -0,0 +1,179 @@
+<div id="directory" class="section">
+<h1>FAQ: RequireJS Optimizations</h1>
+<ul class="index mono">
+<li class="hbox"><a href="#usage">How do I use the Optimization Tool?</a><span class="spacer boxFlex"></span><span class="sect">&sect; 1</span></li>
+<li class="hbox"><a href="#wrap">How can I provide a library to others that does not depend on RequireJS?</a><span class="spacer boxFlex"></span><span class="sect">&sect; 2</span></li>
+<li class="hbox"><a href="#namespace">How can I namespace my code to play well in other people's pages?</a><span class="spacer boxFlex"></span><span class="sect">&sect; 3</span></li>
+<li class="hbox"><a href="#priority">How can I download all script dependencies in parallel?</a><span class="spacer boxFlex"></span><span class="sect">&sect; 4</span></li>
+</ul>
+</div>
+
+<div class="section">
+<h2><a name="usage">How do I use the Optimization Tool?</a><span class="sectionMark">&sect; 1</span></h2>
+
+<p>See the <a href="optimization.html">general optimization page</a> for basic set-up. Also see the <a href="jquery.html">jQuery doc page</a> for a good way to set up your project, even if you are not using jQuery.</p>
+</div>
+
+
+<div class="section">
+<h2><a name="wrap">How can I provide a library to others that does not depend on RequireJS?</a><span class="sectionMark">&sect; 2</span></h2>
+
+<p>If you are building a library for use on web pages that may not use RequireJS or an AMD loader, you can use the optimizer to combine
+all your modules into one file, then wrap them in a function and use an AMD API shim. This allows you to ship code that does not ship with all
+of RequireJS, and allows you to export any kind of API that works on a plain web page without an AMD loader.</p>
+
+<p><a href="https://github.com/jrburke/almond">almond</a> is an AMD API shim that is very small, so it can be used in place of require.js
+when all of your modules are built into one file using the RequireJS optimizer. The
+<a href="https://github.com/jrburke/r.js/blob/master/build/example.build.js#L244">wrap</a> build config option will put a function
+wrapper around the code, or you can provide your own wrapper if you need to do extra logic.</p>
+
+<p>See the almond project for details on how to build with the API shim and with wrap.</p>
+
+<p>If you need to dynamically load code after a build, then using almond+wrap will not be sufficient as almond cannot dynamically
+load code. Instead, you may want to namespace your use of require/define. See next section.</p>
+</div>
+
+<div class="section">
+<h2><a name="namespace">How can I namespace my code to play well in other people's pages?</a><span class="sectionMark">&sect; 3</span></h2>
+
+<p>If you want to provide your code to web sites that may not use an AMD loader, and you need to dynamically load code,
+doing a simple <a href="#wrap">one file build with a wrapper</a> is not enough. You also may want isolate your loading needs from
+the page's AMD loader.</p>
+
+<p>There is a <a href="https://github.com/jrburke/r.js/blob/master/build/example.build.js#L159">namespace</a> build option that
+does the following:</p>
+
+<ul>
+    <li>Renames requirejs, require and define uses to have "namespace." in front of them.</li>
+    <li>If the file does an existence check for define, in the following form <code>typeof define === 'function' && define.amd</code>,
+    then it will prefix the define references with "namespace.".</li>
+    <li>If require.js is included in the built file, it will make sure it exposes the "namespace." versions of the API.</li>
+</ul>
+
+<p>Do not code your source with namespace.require()/namespace.define() calls, but rather use require()/define() as you
+normally would, then use the optimizer to do the renaming.</p>
+
+</div>
+
+<div class="section">
+<h2><a name="priority">How can I download all script dependencies in parallel?</a><span class="sectionMark">&sect; 4</span></h2>
+
+<p>Using <a href="">require()</a> and <a href="api.html#define">define()</a> to define script modules and dependencies is an efficient syntax for indicating related code. However, for deploying code in the browser, it may not lead to the best overall performance. To find nested dependencies, a script has to be fetched, then a require() or define() call in that script might trigger other script downloads.</p>
+
+<p>The <a href="optimization.html">Optimization Tool</a> allows a quick way to <a href="optimization.html#onejs">build all your scripts into one file</a>, so only one script download is needed for your page.</p>
+
+<p>However, if you have many pages in your web app, it may make more sense to optimize your scripts into a set of two or three optimized layers:</p>
+
+<ul>
+<li>One layer for common toolkit code, like jQuery, Dojo, Prototype or MooTools (toolkit.js). It may make sense to roll this layer in with the appcommon.js layer.</li>
+<li>One layer for common web app code (appcommon.js)</li>
+<li>One layer for page-specific code  (page.js)</li>
+</ul>
+
+<p>Ideally you could do that layering after you finish development, and tune those layers for optimal, parallel download of the files, without having to change all your scripts.</p>
+
+<p>This is possible with RequireJS:</p>
+
+<ul>
+<li><a href="optimization.html#wholeproject">Optimize your project</a> to create the three script layers.</li>
+<li>Use the <a href="api.html#config"><strong>priority</strong> config value</a> to pass the list of layers to priority download to the top-level require() call in the HTML file(s).</li>
+</ul>
+
+<p>Script modules/files specified in the config's priority array will be downloaded in parallel before any other script dependencies are traced. <b>Note:</b> resources loaded by loader plugins (like 'text!template.html') <b>cannot</b> be specified in the priority array: the priority mechanism only works with regular JavaScript resources.</p>
+
+<p>This example builds on the <a href="download.html#samplejquery">sample jQuery project</a> to demonstrate the approach:</p>
+
+<p>Assume the project has the following structure:</p>
+
+<ul>
+<li>app.build.js (the build profile used by optimization tool)</li>
+<li>webapp
+<ul>
+<li>page1.html</li>
+<li>page2.html</li>
+<li>scripts
+<ul>
+<li>require.js (the loader)</li>
+<li>appcommon.js (used on both pages, "appcommon")</li>
+<li>jquery.js (used on both pages, "appcommon")</li>
+<li>page1.js (lists the dependencies for page 1)</li>
+<li>page2.js (lists the dependencies for page 2)</li>
+<li>object.js (used on both pages, "appcommon")</li>
+<li>event.js (used on both pages, "appcommon")</li>
+<li>widget.js (used on both pages, "appcommon")</li>
+<li>Dialog.js (used on both pages, "appcommon")</li>
+<li>Slider.js (used only on page 2)</li>
+<li>Tabs.js (used only on page 1)</li>
+</ul></li>
+</ul></li>
+<li>webapp-build
+<ul>
+<li>this directory will hold the optimized files</li>
+</ul></li>
+</ul>
+
+<p>page1.html might look like this:</p>
+
+<pre><code>&lt;!DOCTYPE html&gt;
+&lt;html&gt;
+    &lt;head&gt;
+        &lt;title&gt;Page 1&lt;/title&gt;
+        &lt;script src="scripts/require.js"&gt;&lt;/script&gt;
+        &lt;script&gt;
+            require.config({
+                priority: ["appcommon", "page1"]
+            });
+        &lt;/script&gt;
+    &lt;/head&gt;
+    &lt;body&gt;
+    &lt;/body&gt;
+&lt;/html&gt;
+</code></pre>
+
+<p>with appcommon.js looking like this:</p>
+
+<pre><code>define(["jquery", "object", "event", "widget", "Dialog"],
+function () {
+    //Just an empty function, this is a place holder
+    //module that will be optimized to include the
+    //common depenendencies listed in this module's dependency array.
+});
+</code></pre>
+
+<p>and page1.js looking like this:</p>
+
+<pre><code>define([ "jquery", "object", "event", "widget", "Dialog", "Tabs"],
+function ($,        object,   event,   widget,   Dialog,   Tabs) {
+    ...
+});
+</code></pre>
+
+<p>page2.html and page2.js would look similar, except referencing "page2" instead of "page1" and using "Slider" instead of "Tabs" in page2.js.</p>
+
+<p>The build profile, <strong>app.build.js</strong> would look like this:</p>
+
+<pre><code>({
+    appDir: "webapp",
+    baseUrl: "scripts",
+    dir: "webapp-build",
+    optimize: "none",
+    modules: [
+        {
+            name: "appcommon"
+        },
+        {
+            name: "page1",
+            exclude: ["appcommon"]
+        },
+        {
+            name: "page2",
+            exclude: ["appcommon"]
+        }
+    ]
+})
+</code></pre>
+
+<p>Once the build is run, it will generate the contents of <strong>webapp-build</strong> that look similar to <strong>webapp</strong>, except that the contents are optimized. appcommon.js will contain the common modules, and page1.js will have all the modules page1 needs, excluding appcommon's modules and their nested dependencies.</p>
+
+<p>The <strong>priority</strong> config value tells RequireJS to load appcommon.js and page1.js in parallel and wait before both are loaded before tracing dependencies. With those two files, along with require.js, all the dependencies in the page will be loaded with three requests, with the appcommon.js and page1.js scripts being loaded asynchronously and in parallel.</p>
+</div>