Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

compatibility note #30

Open
wants to merge 1 commit into
base: gh-pages
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -112,6 +112,12 @@ <h2 id="ii-components">II. Components</h2>
<pre><code class="lang-js">var thing = require(&#39;your/duo-component&#39;);
</code></pre>
<p>If you’re coming from the Component community, you’ll notice that we no longer need to add <code>scripts</code>, <code>styles</code> or <code>templates</code>. Duo handles all of this for you, walking the dependency tree like Browserify and including everything you need automatically, for both Javascript and CSS!</p>
<p>Note: even if a package is lacking a <code>component.json</code>, it might still be used as a dependency if two conditions are met:</p>
<ol>
<li>its main file is named <code>index.js</code></li>
<li>it doesn't have any dependency</li>
</ol>

<h2 id="iii-web-applications">III. Web Applications</h2>
<p>In order for a package manager to be truly useful, it needs to scale to accommodate building entire web applications. Once again, Duo makes this process seamless.</p>
<p>Duo allows for building multiple pages at once, so that you can split up your application into different bundles and keep your page assets slim. To build from multiple entry files, just pass more than one entry into <code>duo</code>:</p>
Expand Down