I"»<p>Compiling Lego component is built-in with no extra installation; pretty straighforward.</p>

<div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code>npx lego <span class="o">[</span><span class="nt">-w</span><span class="o">]</span> <span class="o">[</span>source_path] <span class="o">[</span>target_path]
</code></pre></div></div>

<ul>
  <li><strong>-w</strong>: watching for changes in components and recreating</li>
  <li><strong>source_path</strong>: (default: ./bricks) either a file or a directory (relative or absolute) where you write your HTML components. If it’s a directory, it will recursively read all the <em>.html</em> files and compile them into the <em>target_file</em>.</li>
  <li><strong>target_path</strong>: (default: ./dist) the path (relative or absolute) where your JS components will be generated. That folder will be created and contain all the components.</li>
</ul>

<p>Therefore <code class="language-plaintext highlighter-rouge">npx lego</code> would compile the <em>source_path</em> files or folder (recursively) into <em>target_file_path</em> js file using lego.min.js (from ./bricks to ./dist by default).</p>

<p>As mentioned before, when developing you probably want to watch for changes with the <code class="language-plaintext highlighter-rouge">-w</code>
option: <code class="language-plaintext highlighter-rouge">npx lego -w &lt;source_path&gt; &lt;target_file_path&gt;</code></p>

:ET